Last update:
2-hop/2-key: HSID- Portal interaction
Aug 21, 2026
After completing the necessary steps HSID will redirect to the “redirect_uri” provided by the portal (see the section above). HSID will send back the complete URL along with any information passed in the form of query parameters when TARGET parameter value is set by Portal in “Portal - PingFederate interaction”.
In the example above, Portal “automatic-oidc-start” will now automatically initiate an HSID OIDC authorization request for HSID.
Note: OIDC redirect_uri provided by Portal should be static, due to OIDC redirect_uri exact match validation (simple string comparison) requirement and RFC 9700 OAuth 2.0 best security practice. Therefore, dynamic parameters provided to “automatic-oidc-start” function (deeplink, twokey, etc) should be associated with state OIDC query parameter, then retrieved once redirect_uri is called with state parameter (see below).
HSID will perform the regular OIDC flow (however, the user is already SSO-authenticated, therefore there is no password authentication) and redirect to the redirect_uri along with the auth code and state.
Then Portal processes:
- Verification of state
- Retrieval of dynamic parameters (optional, see above)
- Retrieval of OIDC Tokens using auth code.
Share additional feedback to help us improve.
0/255
|
Powered by Aikyam @2025 All rights reserved
+1 866 451 2735
+1 866 451 2735
+1 855 819 5909