Use the Identity Federation feature with your Identity Provider to enable your TD account users to use one ID to sign into more than one Treasure Data account.
You configure your Identity Provider (IdP) to authenticate your Treasure Data users and thereby control the sign in policy for your users.
Identity Federation provides heightened security and tighter authentication for both on-premise and cloud applications. You can centrally manage all users and their respective permissions through your corporate directory service.
For example, your company might have three Arm Treasure Data accounts, such as developer account, test account and production account.
Identity Federation supports IdPs using SAML 2.0 protocol, such as Azure Active Directory.
Contact your Customer Success representative if you are interested in enabling the Identity Federation feature on your account.
Identify Federation with Other Sign-in Methods
Identity Federation cannot be used in conjunction with Google SSO in Treasure Data.
You can configure users to sign into Treasure Data either with their email and password sign on or with Identity Federation.