The primary protocol used for communication between the Identity Provider (IdP) and the enterprise application in IdP-initiated SSO is Security Assertion Markup Language (SAML).
Here's how SAML works in IdP-initiated SSO:
User Authentication: The user initiates the login process at the IdP.
Assertion Generation: After successful authentication, the IdP generates a SAML assertion containing information about the user's identity and attributes. Â
Assertion Sending: The IdP sends the SAML assertion to the enterprise application (ServiceNow in this case).
Assertion Validation and Access: ServiceNow validates the assertion and grants access to the user based on the information in the assertion.
Why not the other options?
A. JSON Web Token (JWT) authentication: JWT is a token format, often used with OAuth or OpenID Connect, but not the primary protocol for IdP-initiated SSO.
B. OAuth 2.0 authorization framework: OAuth is primarily used for authorization, granting access to resources, rather than authentication.
C. OpenID Connect (OIDC) protocol: OIDC is an authentication layer built on top of OAuth 2.0, but SAML is more commonly used for IdP-initiated SSO.