This article applies to:
- Product edition: Druva Cloud Platform (DCP)
SSO token uniquely identifies the DCP login requests. For every login attempt, DCP sends a request to the IdP (typically HTTP POST). The IdP attaches the SSO token in response indicating the veracity of the authentication requests. When DCP receives this response, it uses the SSO token ID to validate the authenticity of the IdP response. Hence to allow IdP to recognize authentication requests from DCP, the SSO token must be generated first before updating the IdP configuration with this token.
- Only a Druva Cloud administrator can set up Single Sign-on.
- Configure Single Sign-on based on the applicable scenarios:
- New Druva customers that is; Phoenix customers on-boarded after 02 July 2018 and inSync customers on-boarded after 14 July 2018 must refer to the instructions given in this article.
- Existing Phoenix and inSync customers who already have configured Single Sign-on, must continue to use the existing Single Sign-on settings of Phoenix and the Single Sign-on settings of inSync as applicable.
- Druva recommends generating the SSO token only once. If the token is generated again, the older SSO token registered with the IdP becomes invalid. Hence, if a new SSO token is generated, update the IdP details accordingly.
- Log in to the DCP Console and on its menu bar click the account icon > Settings.
- Click Generate SSO Token.
- Click Copy. The token gets copied to the clipboard.
- Click OK and update the IdP configuration with the new SSO token.