How the concept is used

An identity provider can send the result to a relying service using an agreed protocol. The recipient needs to check the issuer, the intended audience and whether the result remains valid. This is different from copying the user’s password between applications. The shared login experience depends on agreements and technical checks that each connected service must follow.

A practical example

Imagine employees opening both an order system and a customer support tool with the same work identity. The support application can recognise an employee without another password, while the company manages authentication centrally. When the employee leaves, relevant access still needs to be removed. Existing sessions may require separate treatment even after the central account has been disabled.

Important distinctions

SSO does not mean that every system grants identical permissions, shares all customer information or supports coordinated logout. Those behaviours need to be specified. Nor does it necessarily mean that a person’s real-world identity has been thoroughly checked; an ordinary internal account can also support SSO. Assess trust in the identity provider, session lifetimes and the division of responsibilities. Authentication elsewhere does not remove the relying service’s duty to validate the result and grant appropriate access.

Sources

  1. NIST: NIST SP 800-63C-4: Federation and Assertions Checked

These explanations were prepared with AI assistance and draw on the sources listed.