Steps to configure OAuth/OpenID-Connect-based SSO for PingOne

About PingOne

PingOne is a cloud-based Identity as a Service platform that provides identity management capabilities for workforces.

The following steps will help you enable OAuth/OpenID-Connect-based single sign-on (SSO) for PingOne from ManageEngine Identity360.

Prerequisites

  1. The MFA and SSO license for Identity360 is required to enable SSO for enterprise applications. For more information, refer to the pricing details.
  2. Log in to Identity360 as an Admin or Super Admin, or as a Technician with a role that has Application Integration and Single Sign-on permissions.
  3. Navigate to Applications > Application Integration > Create New Application, and select PingOne from the applications displayed.
    Note: You can also find PingOne from the search bar located at the top.
  4. Under the General Settings tab, enter the Application Name and Description.
  5. Under the Choose Capabilities tab, choose SSO and click Continue.
     Identity360 application configuration General SettingsGeneral Settings of SSO configuration for PingOne.
  6. Under Integration Settings, navigate to the Single Sign On tab, and select OAuth/OpenID Connect from the Method radio button. Click IdP Details and copy the highlighted field values in the screenshot below.
     Identity360 application configuration Integration SettingsIntegration Settings of SSO configuration for PingOne.

PingOne (service provider) configuration steps

  1. Log in to PingOne as an administrator.
  2. Go to Environments > End User Sandbox environment > Manage Environment.
    PingOne admin portal viewPingOne admin portal view.
  3. Click Integrations > External IdPs > + Add Provider.
    Add identity provider from PingOneAdding an identity provider from PingOne.
  4. Select OPENID CONNECT.
    Select OIDC IdP from PingOneSelect OIDC IdP from PingOne.
  5. Under Create Profile, enter a suitable name for Identity360. You can also give a description and customize the icon and login button in this section. Click Continue.
    Create IdP profile in PingOneCreating an IdP profile in PingOne.
  6. On the Configure OpenID Connect Connection page, copy the CALLBACK URL, as it will be required during Identity360 configuration.
  7. Fill in the required fields with details copied in step 6 of the prerequisites:
    • CLIENT ID: Client ID
    • CLIENT SECRET: Client Secret
    • AUTHORIZATION ENDPOINT: Authorization Endpoint URL
    • TOKEN ENDPOINT: Token Endpoint URL
    • JWKS ENDPOINT: Keys Endpoint URL
    • ISSUER: Issuer
    • USER INFORMATION ENDPOINT: User Endpoint URL
  8. Under the REQUESTED SCOPES field, enter openid, email, profile.
  9. Under the TOKEN ENDPOINT AUTHENTICATION METHOD field, choose the Client Secret Basic radio button.
  10. Click Save and Continue.
    Configuring OIDC connection in PingOneConfiguring the OIDC connection in PingOne.
    Configuring OIDC connection in PingOneConfiguring the OIDC connection in PingOne.
  11. On the Map Attributes page, keep the default settings, and click Save & Finish.
    Map attributes in PingOneMapping attributes in PingOne.

Identity360 (identity provider) configuration steps

  1. Switch to Identity360's application configuration page.
  2. In the Login Redirect URL field, paste the Redirect URI copied from step 6 of PingOne configuration.
  3. Choose the required Scope from the drop-down.

    Note: Relay State is an optional parameter used with a SAML message to remember where you were or to direct you to a specific page after logging in.

    • openid: Establishes that this is an OpenID Connect request.
    • email: Requests the user's email attribute.
    • profile: Requests the user's profile claims (FirstName and LastName).
  4. Click Save.
    Identity360 application configurationIntegration Settings of SSO configuration for PingOne.
  5. To learn how to assign users and groups to one or more applications, refer to this page.

Your users should now be able to sign in to PingOne through the Identity360 portal.

Note: For PingOne, SP-initiated flow is supported when SSO is enabled through OAuth.

Don't see what you're looking for?

  •  

    Visit our community  

    Post your questions in the forum.

     
  •  

    Request additional resources  

    Send us your requirements.