Why update IdP details
To enable SSO for your inSync setup, you must have created a corporate database with an IdP that contains the credentials of users and administrators for whom you want to enable SSO access. To enable communication between inSync and your IdP, there must be a mechanism that allows the IdP to recognize requests that inSync Master sends. That is why you must update your IdP configuration to provide inSync configuration details.
Before you begin
Before updating IdP details, ensure that:
- You have the SAML_Identifier parameter handy. To obtain the value of this parameter, submit a request to Druva Support.
Note: This parameter functions as the entity ID.
- You have access to the documentation for the Identity Provider that you are using. This article contains instructions that serve as a guide, and not as exact tasks that you must perform.
Note: Unless otherwise noted, use this procedure as a guide. Use the documentation provided by your IdP for exact configuration steps.
To update your IdP details
- Log on to the IdP administrator console with elevated rights.
Note: For example, the Global Administrator role supported by PingOne allows for full access to manage and control all aspects of the administrator console.
- Create a new SAML application.
- Provide the Assertion Consumer Service URL.
Note: The Assertion Consumer Service is a SAML-compliant URL that is hosted on your IdP. It acts as a receptor for form submissions and page redirects. An example URL might look like this: https://cloud.druva.com/wrsaml/consume
- Provide the SAML_Identifier value as the "entity ID".
- Provide the application URL, for example, https://cloud.druva.com/admin
- Provide the Name ID Format, SSO token, and other details that your IdP mandates.
- Save your changes.