Federated Identity and Trust
Key Takeaways
In federation, an identity provider supplies identity and authentication evidence to a relying party.
Check the issuing party, verification key, audience, timing and transaction protections before accepting an assertion.
Security Assertion Markup Language and OpenID Connect can convey authentication evidence. OAuth 2.0 access tokens serve resource authorization.
Confirm subject mapping and application permissions separately from assertion validation.
Identify the trust relationship
A federation arrangement allows a service to accept information about a user’s authentication from another trusted party. In a common browser sign-in flow, the identity provider (IdP) authenticates a user and issues an assertion. The relying party (RP) validates the assertion and uses it to establish its own session. In Security Assertion Markup Language (SAML), the application receiving the assertion is often called the service provider (SP). The trust relationship governs which issuer, endpoints, keys and attributes are accepted.
Consider a company’s approved IdP and two applications, Expense and Benefits. Expense directs a user to the IdP with the necessary transaction context. If the existing IdP session can be reused under the applicable policy, the user may get single sign-on (SSO) without entering a password again. The IdP provides the proof for Expense. Expense still validates the assertion that applies to its own application and establishes its own session. A shared IdP’s assertion for Benefits is addressed to Benefits, even if the same employee exists in both systems.
| Check at the receiving application | What it addresses |
|---|---|
| Issuer and trusted verification key | Confirms the expected IdP issued and protected the assertion |
| Audience and applicable recipient endpoint | Limits acceptance to the intended relying party and destination |
| Validity window | Rejects evidence outside its permitted time |
| Transaction state, nonce or assertion identifier as applicable | Correlates a response and helps prevent injection or replay |
| Subject and identity mapping | Resolves the authenticated subject to the intended application account |
Match the protocol to the artifact
SAML 2.0 uses assertions to carry the subject and authentication or attribute information. In browser SSO, the service provider consumes the response at its configured assertion consumer service endpoint. SAML assertions use Extensible Markup Language (XML). OpenID Connect (OIDC) adds authentication to OAuth 2.0 and supplies an ID token in JSON Web Token format for the client to validate under its protocol rules. An OAuth access token is presented to a resource server to authorize a call. In an OIDC flow, the two token types can appear together and have different recipients and purposes. Verify the expected token type as well as its integrity. OAuth 2.0 is the authorization framework underlying that use of access tokens.
Do not use a subject string alone to link users from multiple identity providers. The same string can identify different subscribers in separate issuer namespaces. Confirm the expected issuer, then use the subject and configured mapping within that issuer’s context. Validate attributes that are used to link local accounts, especially when multiple people have similar names. A valid assertion establishes information about an identity. The receiving system still decides what that identity may do.
Work an audience failure
A support engineer receives evidence that sign-in at the IdP succeeded and that the returned SAML assertion verifies against its trusted signing key. Its audience identifies the Benefits service, but the callback was presented to Expense. Expense should reject it. Investigate the IdP application mapping, configured entity identifiers, and intended callback. Allowing Expense to accept every assertion signed by the corporate IdP would remove the intended audience boundary. In the opposite case, matching the audience text alone while accepting an untrusted issuer would leave the issuer boundary open. Audience and signature validation protect different parts of the transaction. If the audience is correct and the signature fails after a certificate change, check approved metadata and key rollover separately. The two defects produce similar user symptoms and require different checks.
Trace a successful federation test end to end. Confirm the expected subscriber was authenticated, the service accepted the assertion for its own session, the subject mapped to the intended account, and an allowed action succeeded while a protected action remained unavailable. For tenant integrations, use the service provider’s product-specific federation setup. SailPoint documents configuring its hosted service provider with the IdP metadata and signing certificate for its SAML sign-in path. Do not infer from that tenant setup how other applications provision entitlements.
See NIST’s general-purpose federation requirements, the OASIS SAML technical overview, OpenID Connect Core, and SailPoint’s SAML service provider setup.
Expense receives an otherwise valid assertion from its trusted identity provider. The assertion’s audience is Benefits. What should Expense do?
Accept it because the issuer is trusted by both applications
Reject it and verify the application-specific audience and routing
Convert the assertion to a product role automatically
Trust it as long as the user can read a Benefits report
An OpenID Connect client gets an ID token and an OAuth access token. Which artifact is ordinarily intended for authenticating the user to that client?
The access token issued for the separate resource API
The client’s own name in its deployment configuration
The user’s application role label
The ID token, validated by that client under OpenID Connect
Sections you finish are checked off in the contents.