PingID Single Sign-On

To set up a single sign-on (SSO) with the PingID provider, you must create two applications in your PingID environment:

• OAuth2 Worker application for authentication and group synchronization
• SAML application for users’ SSO

Overview of steps

Make sure to perform the following actions in the correct order, otherwise you might disable your existing authentication to your {ProductName} tenant. These steps are: 

1. Set up the authentication provider in {ProductName} using a PingID Worker application.
2. Perform group synchronization for your PingID authentication provider.
3. Create Access Control records for the imported groups. Make sure that you will retain an administrative role in {ProductName} when you log in using your PingID identity. You must create access control records with the Administrator role for the group where you are a member.
4. Set up SAML SSO for your {ProductName} tenant.

Setting up the OAuth2 Worker application

For steps 1-3 from the above overview, see Add a custom app in the Ping identity platform.

SAML Configuration

The redirect URL for the PingID SAML application is https://<your {ProductName} domain>:8443/assertion/saml. For example, https://acme.eu.{ProductWeb}:8443/assertion/saml. The port is 8443. In environments with reverse proxy infrastructure, do not specify the port number in the URL (https://<your {ProductName} domain>/assertion/saml), meaning the default HTTPS port 443 will be used.

1. To create a SAML application, log into your PingID environment and go to  Applications. Click +  to create a new application. 
2. Enter the Application Name , and an optional  Description. Select SAML Application as the Application Type.
   

   

   
   
3. Click Configure .
4. In Provide Metadata Configuration, select Manually Enter, and add the following:
   1. In ACS URL, enter https://<your {ProductName} domain>:8443/assertion/saml. The port is 8443. In environments with reverse proxy infrastructure, do not specify the port number in the URL (https://<your {ProductName} domain>/assertion/saml), meaning the default HTTPS port 443 will be used. 
   2. In Entity ID, enter a unique identifier for this application. We recommend you to use your {ProductName} tenant address.
      

      

5. Next, click the  Attribute Mappings  tab and create attribute mappings as per the following table. Be aware that it is likely PingID will default the attribute saml_subject to User ID . You must change it to Username.
   

   Attributes	PingOne Mappings
   saml_subject	Username
   fname	Given Name
   group_membership	Groups IDs
   group_membership_names	Group Names
   lname	Family Name

   
   

   

   
   
6. Once the attribute mappings are complete, enable the application using the slider in the top right of the page.
7. Click the Configuration tab of your SAML application and copy the IDP Metadata URL . 
   

   

   
   
8. Log in to {ProductName} Web UI and go to Users page and to Single sign-on tab.
9. Paste the IDP Metadata URL into the SSO XML metadata URL field.
   

   

    
   
10. The SSO issuer ID must be the same string that you entered as the Entity ID in your PingID application configuration.
11. Set SSO method to SAMLv2.
12. Click Save.
13. Test your SSO by opening the {ProductName} Web UI login page. This will redirect you to the PingID authentication page. Log in with any user account from your PingID environment.  

Every time a user logs into {ProductName} using SAML SSO, their given/family names and group membership will be synchronized from PingID.