Docs » About SSO integrations for Splunk Observability Cloud » Configure a PingOne SSO integration

Configure a PingOne SSO integration 🔗

The PingOne SSO integration allows you to log into Observability Cloud using PingOne.

Before you begin configuring the OneLogin SSO integration, ensure you have completed the steps in Configure SSO integrations for Splunk Observability Cloud, including the section Name an SSO integration to learn about naming your integrations.

Note

To use this procedure, you must be an administrator of your PingOne organization and your Observability Cloud organization.

To set up your PingOne SSO integration, follow these steps:

Open a browser tab or window for Observability Cloud, and another for PingOne.

In Observability Cloud, do the following:
  1. Log in to Splunk Observability Cloud.

  2. Open the PingOne guided setup. Optionally, you can navigate to the guided setup on your own:

    1. In the left navigation menu, select Data Management.

    2. Select Add Integration.

    3. In the integration filter menu, select All.

    4. In the Search field, search for PingOne, and select it.

  3. In the Name text box, enter a name for your PingOne SSO integration.

  4. Copy the value next to Integration ID so you can use it in a later step.

In PingOne, do the following:
  1. Select Applications. A list of your installed applications appears.

  2. Select Add Application, and then select Search Application Catalog.

  3. In the search field, enter SignalFx. Select the SignalFx application.

  4. If the Setup is active, select it. A setup screen appears.

    If the Setup button is inactive, and you see the tooltip “You need to setup a connection first”, then you might need to connect to an Identity Repository. To connect to an Identity Repository:
    1. At the top of the PingOne page, select Setup.

    2. Select Connect to an Identity Repository.

    3. Select the Identity Repository you want to use, select Next twice, then select Finished.

  5. Select SignalFx, then select Setup.

  6. Optional: Copy the configuration parameters to keep as a reference.

  7. Select Continue to Next Step.

Still in PingOne, continue the configuration:
  1. In the ACS URL field, a URL similar to https://api.signalfx.com/v1/saml/acs/<INTEGRATION_ID> appears.

  2. Replace <INTEGRATION_ID> with the integration ID you copied in a previous step.

  3. Confirm that the ACS URL and Entity ID URLs refer to your Observability Cloud realm.

    If your Observability Cloud organization uses the us0 realm, enter the following:
    • ACS URL: https://api.signalfx.com/v1/saml/acs/<INTEGRATION_ID>

    • Entity ID: https://api.signalfx.com/v1/saml/metadata

    If your Observability Cloud organization uses another realm, enter the following:
    • ACS URL: https://api.<YOUR_REALM>.signalfx.com/v1/saml/acs/<INTEGRATION_ID>

    • Entity ID: https://api.<YOUR_REALM>.signalfx.com/v1/saml/metadata

In PingOne, select Continue to Next Step. The Attribute Mapping screen appears.
  1. For SAML_SUBJECT:
    1. Select Advanced.

    2. In the Name ID Format to send to SP dropdown list, select urn:oasis:names:tc:SAML:2.0:nameid-format:persistent, then Save.

  2. Select other attributes as needed.

Select Continue to Next Step. The Group Access screen appears.
  1. Select the users who should have access to Observability Cloud. Select Continue to Next Step. The customization screen appears.

  2. Configure the SignalFx application, then select Continue to Next Step. The review screen appears.

  3. In the review screen that appears, do the following:
    1. Locate the Certificate field, then select Download to download the pingone-signing.crt file to your computer.

    2. Locate the SAML Metadata field, and then select the Download link to download the saml2-metadata-idp.xml file to your computer.

    3. Finish. The PingOne Applications list appears. In the list, SignalFx appears as an active application.

In Observability Cloud, do the following:
  1. Locate the Certificate text box.

  2. Select Upload File. A file system dialog box opens.

  3. To upload the certificate file, select the pingone-signing.crt file you downloaded in a previous step.

  4. After the upload, the text for Certificate changes to match the uploaded file.

  5. Locate the Metadata text box:

  6. Upload File. A file system dialog box opens.

  7. To upload the metadata file, select saml2-metadata-idp.xml file you downloaded in a previous step.

  8. After the upload, the text in the Metadata text box changes to match the uploaded file.

  9. Save. Observability Cloud displays a Validated! message.

The PingOne SSO integration is now available to users in your PingOne application. When users use the integration for the first time, they receive an email containing a link that they must open in order to authenticate. This only occurs the first time the user signs in. Subsequent login attempts don’t require validation.

If you want to turn off email authentication, contact Splunk Observability Cloud support.

Once you have a custom URL configured, your users can continue to log in using their existing username/password pair, or they can use their Okta credentials instead. PingOne SSO authentication and Observability Cloud username/password authentication are independent.

Observability Cloud generates a password for users you create in PingOne SSO. If the PingOne login portal is unavailable, Observability Cloud users can use the reset password link on the Observability Cloud login page to get native Observability Cloud credentials.

Report an issue 🔗

Before you create an issue or open a support request, try gathering the following information:

  • What happened and the impact of the issue.

  • All the steps you’ve followed until the issue appeared.

  • What was the expected outcome.

  • Your attempts to solve the issue, including workarounds.

  • The operating system, runtime or compiler version, libraries, frameworks, and application servers of your environment, including your instrumentation settings.

  • Debug logs and other logs that might help troubleshoot the issue.

To get help, see Splunk Observability Cloud support.