This integration guide shows how to set up PingIndentity as a SAML single sign-on provider for your Redis Cloud account.
| Redis Cloud |
|---|
Specific identity provider details may be different than shown in this guide. Always consult your identity provider's docs for the latest information.
This guide shows how to configure PingIdentity as a SAML single sign-on identity provider (IdP) for your Redis Cloud account.
To learn more about Redis Cloud support for SAML, see SAML single sign-on.
Before completing this guide, you must verify ownership of any domains you want to associate with your SAML setup.
redisAccountMapping attribute
Log in into your Ping Identity account. Open Administrators > Identities > User Attributes and select Add Attribute.
Select the DECLARED attribute type.
Fill in the fields with the following values:
redisAccountMappingredisAccountMappingredisAccountMappingSelect Save and Close. Then, verify that the attribute was created successfully.
Go to Administrators > Identities > Users and select Add User.
Fill in the following information:
{accountID}={role}accountID is the account ID from account settings and role represents the role that the user will be assigned in Redis Cloud console (owner, member, manager, billing_admin, or viewer):
Save and check that the user was added successfully.
Go to Administrators > Connections > Applications and select + to add a new application.
Choose a name for the application, select SAML Application Type and select Configure.
In the ACS URLs and Entity ID field add for now some dummy data, like https://example.com
Select Save.
Go to the Configuration tab and save the following information:
This information will be needed once we configure SAML in the Redis Cloud console.
Go to the Attribute Mappings tab. Add the following attributes:
Now that we have our Ping Identity IdP server ready, we need to configure support for SAML in Redis Cloud.
Sign in to your account on the Redis Cloud console.
To activate SAML, you must have a local user (or social sign-on user) with the owner role. If you have the correct permissions, you will see the Single Sign-On tab.
Fill in the information you copied previously, including:
Issuer IDSingle Signon ServiceSingle Logout ServiceAlso add:
Select Enable and wait a few seconds for the status to change.
You will then be able to Download the service provider (SP) metadata. Save the file to your local hard disk.
Open the file in any text editor. Save the following text from the metadata:
In Ping Identity, go to Administrators > Connections > Applications and select your application name. Select the Configuration tab and select Edit.
This is where we had entered mock data. We will now enter the correct data for this step:
Paste EntityID information in the Entity ID field.
Paste Location link in the ACS URLS field.
For the Sign on URL field, add URL https://cloud.redis.io/#/login/?idpId=, where you need to add the ID from the Reply URL ID, for example, https://cloud.redis.io/#/login/?idpId=0oa5pwatz2JfpfCb91d7.
Select Save.
Select the slider to enable the app.
Return to the Redis Cloud console and select Activate.
A popup appears, explaining that to test the SAML connection, you need to log in with credentials of a user defined in Ping Federate. Select Continue to go to the Ping Federate login screen.
The Ping Federate login screen will appear. Enter the credentials and select Sign In.
If everything is configured correctly, you will see the the Redis Cloud console screen. Your local account is now considered a SAML account.
To log in to the Redis Cloud console from now on, click on Sign in with SSO.
Sign in with SSO buttonhttps://cloud.redis.io/#/login/?idpId=
In Ping Identity, go to Administrators > Connections > Applications and select your application name. Select the Configuration tab and select Edit.
Go to Target Application URL and enter: https://{enviroment}/#/login/?idpId={idpId}, where idpId is the ID found in the Location field, after the last '/'
Select Save.
Go to https://apps.pingone.com/{environment}/myapps/# , where environment is the environment ID, found in Administrators -> Environment for your app.
You are redirected to the Redis Cloud console.