2-hop/2-key: PingFederate – HSID interaction

Last update:
Aug 21, 2026
PingFederate will do the necessary validations and create a new opentoken and redirect to HSID Inbound SSO URL. HSID will get all the information passed by Portal in the form of query parameters.
  • Query Parameters (all values should be query-parameter-value encoded)
    • sso_identifier
      • This identifier should be provided at the time of HSID onboarding.
    • redirect_uri
      • This is a URL of Portal, that will automatically starts HSID OIDC, and also guides the user to the desired landing page after SSO completion. Please see the next section 2-hop/2-key: HSID – Portal Interaction.
    • opentoken
      • This parameter and value are automatically added by PingFederate. opentoken carries the user’s identity attributes that are required by HSID Inbound SSO process.
Note: This entire URL without “opentoken” parameter should be provided as “TARGET” query parameter value in the previous section, 2-hop/2-key: Portal – PingFederate Interaction.

On this page

Powered by Aikyam @2025 All rights reserved