Okta SAML is Okta's SAML 2.0-based solution for single sign-on, federated authentication and authorization, providing centralized session management. It enables integration with service providers and attribute mapping for fine-grained access control. Administrators configure applications, certificates and assertion settings centrally in Okta, including signa…
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Technical building block: can be automated, integrated, or operated.
Concrete cog in the system that works inside larger relationships.
Okta SAML connects Okta as an identity provider to an application and enables single sign-on through the SAML 2.0 protocol.
OASIS standardized SAML 2.0 as an XML-based standard for federated identity. Okta integrated the standard into its identity cloud so that Okta can issue SAML assertions as an identity provider to connected service providers.
During sign-in, the application requests a SAML assertion from Okta. Okta authenticates the person and returns a signed assertion with identity attributes; the application checks its signature, audience, destination, and validity before creating a session. Metadata, certificates, entity IDs, ACS URL, and attribute mappings must agree.
Okta authenticates the person and issues a SAML assertion for the application.
The target application validates the assertion and uses it to sign the person in.
Metadata, certificates, and endpoints establish the technical trust relationship.
Okta SAML fits centralized sign-in to SAML-capable applications. Integration effort, certificate rotation, attribute design, and dependency on Okta need explicit operational decisions.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.