PingOne SSO

Before you begin

You need your socure_public_account_id, available in the RiskOS™ Dashboard on the Developer Workbench > API Keys page under the Customer ID section.

• Access Sandbox socure_public_account_id.

• Access Production socure_public_account_id.

Set Up Single Sign-On (SSO) with PingOne

1. Configure SAML in PingOne

Follow these steps to create a SAML 2.0 integration in PingOne:

1. Log into your PingOne account.
2. From the navigation sidebar, expand the Applications section and select Applications.
3. Click + (plus) to begin creating a new application.
4. On the Add Application page:
   • Enter the app name as Socure SSO Integration.
   • (Optional) Add a description.
   • (Optional) Upload a PNG or GIF file as an app icon.
   • Select SAML Application as the application type.
5. Complete the SAML Configuration as follows:
   • Select Manually Enter.
   • ACS URLs: Enter https://api-dashboardv2.socure.com/saml2/SSO.
   • Entity ID: Enter one of the following:
     • Sandbox environment: https://riskos.sandbox.socure.com/saml2/socure_public_account_id
     • Production environment: https://riskos.socure.com/saml2/socure_public_account_id
6. Complete the Attribute Mappings as follows:

7. Click Save and Close.

To manage what role(s) a user should have when they access RiskOS™, you must add a new custom attribute. Fill out the details of the new custom attribute as follows:

• Data type: string array
• Display Name: https://dashboard.socure.com/attributes/role
• Variable Name: RoleName
• Enum: Checked
• Attribute Members:
• Display name is flexible, and you can define it as you prefer; however, the value must match a valid RiskOS™ role name.

The following table lists the valid role names available in RiskOS™:

2. Send the SAML metadata to Socure

After creating the SAML application integration, go to the Configuration tab and click Download Metadata to obtain the SAML metadata file. Securely send this file to Socure.

Don't copy and paste just the X.509 certificate from the SAML Setup Instructions page. Socure requires the full SAML metadata file (XML format), which includes your entity ID, endpoints, and certificates.

After receiving your SAML metadata file, your Technical Account Manager will confirm when SAML is enabled for your account.

3. Test the integration

To test the SAML integration, go to the IdP Admin Console, create a user, assign Socure's RiskOS™ app to the user and assign role(s) via the custom RoleName SAML attribute. When the user launches the RiskOS™ app from the IdP dashboard, the following occurs:

The Users tab on the Users page in RiskOS™ is populated with the user's name, email address, and phone number.
The system assigns the user the role(s) specified in the RoleName custom SAML attribute. If no role is assigned, the system defaults to assigning the Analyst role to the user.

4. Assign users to RiskOS™

If you plan to manage role assignment to users and you have configured the custom SAML attribute for RoleName, you can assign role(s) to the user when assigning the application. If a role is not assigned, the system defaults to assigning Analyst role to the user.