Your Ariba representative will provide you with connection parameters for the ACS URL and Entity ID fields.

All other fields are optional.

  1. Import the metadata for Ariba:
    • Click Select File to upload the metadata file.
    • Click Or use URL to enter the URL of the metadata.
  2. In the ACS URL and Entity ID fields, replace the ${parameter} variables with the information provided by your Ariba representative.
  3. In the Target Resource field, enter a URL to redirect the user to after IdP-initiated single sign-on (SSO).
  4. In the Single Logout Endpoint field, enter a URL for PingOne to send single logout (SLO) requests to.
  5. In the Single Logout Response Endpoint field, enter a URL for PingOne to send SLO responses to.
  6. On the Primary Verification Certificate line, click Browse to locate and upload a local certificate file used to verify SLO requests and responses.
  7. On the Secondary Verification Certificate line, click Browse to locate and upload a local certificate used to verify SLO requests and responses if the primary certificate fails.
  8. Select the Force Re-authentication check box to require your identity bridge to re-authenticate users with an active SSO session.
  9. Select the Encrypt Assertion check box to encrypt outgoing SAML assertions.
  10. On the Signing line:
    • Click Sign Assertion to have PingOne sign outgoing SAML assertions. This is the default option.
    • Click Sign Response to have PingOne sign responses to incoming SAML assertions.
  11. From the Signing Algorithm list, select an algorithm with which to sign SAML assertions.
  12. Select the Use Custom URL check box to enter a customer URL to launch Ariba from the dock.
Click Continue to Next Step.