1-hop: External vendor – PingFederate interaction

Last update:

Aug 21, 2026

For 1-hop case, external vendor will directly send the equivalent information described in 2 hop/2-key: Portal – PingFederate Interaction section, through SAML. SAML should include:

RelayState: HSID Inbound SSO URL where PingFederate redirects the user after SAML processing. This is equivalent to TARGET parameter in 2 hop/2-key: Portal – PingFederate Interaction section.
SAMLResponse - Assertion
- AuthnStatement
  - Should contain AuthnContextClassRef (ACR) to inform which level of authentication is done on External Vendor site.
  - The value would be decided during Inbound SSO onboarding process.

1-hop: PingFederate – HSID Interaction

Was this helpful?

We are sorry the content didn't meet your needs.

Share additional feedback to help us improve.

0/255 | Character limit exceeded.

Thank you so much for sharing your feedback!