SAML Concepts: Difference between revisions
Line 60: | Line 60: | ||
<font color=red>Requests and responses for obtaining assertions and doing identity management.</font> | <font color=red>Requests and responses for obtaining assertions and doing identity management.</font> | ||
{{Internal|SAML | {{Internal|SAML Concepts - Protocol|SAML Protocol}} | ||
=SAML Assertion= | =SAML Assertion= |
Revision as of 02:15, 21 February 2017
Internal
Security Assertion
Subject
Subjects are entities that have identity related information specific to a security domain.
Security Domain
Identity Provider
The Identity Provider (IdP) is.
The Identity Provider is also known as the asserting party.
Service Provider
The Service Provider (SP) is ....
The Service Provider is also known as the relying party.
Trust Relationship
There is a trust relationship between the Identity Provider and and the Service Provider.
Token
A SAML token is a type of token issued by a STS/IdP that can be used to enable SSO. A relying resource secured by SAML will redirect users to SAML identity provider to obtain a valid SAML token before authenticating and authorizing the user.
Single Sign-On (SSO)
Single sign-on (SSO) is not strictly a SAML concept. However, because SAML provides a trusted way to share security information, applications using SAML can participate in single sign-on scenario where the identity of a subject is verified by a party and other party uses it because it trusts the first party and the communication mechanisms between them. SAML requires the user to enroll with at least one SAML-enabled security provider. The identity of the user will be verified (authenticated) by that security provider. Web browser single sign-on is a SAML profile.
SAML Use Cases
Web Browser Single Sign-On
Web browser single sign-on (SSO) among independent but cooperating parties is the most important SAML use case. Another more recent approach to addressing browser SSO is the OpenID Connect protocol.
Attribute-based Authorization
Identity Federation
WS-Security
SAML Profile
A profile is essentially a use case for SAML. A profile combines assertions, protocols and bindings to support a specific use case.
SAML Binding
Mapping of SAML protocols onto standard messaging and communication protocols.
SAML Protocol
Requests and responses for obtaining assertions and doing identity management.
SAML Assertion
Authentication, attribute and entitlement information.
Authentication Context
Detailed data on types and strengths of Authentication.
Metadata
Configuration data for identity and service providers.
To Deplete
- https://home.feodorov.com:9443/wiki/Wiki.jsp?page=SingleSignOn
- https://home.feodorov.com:9443/wiki/Wiki.jsp?page=PicketLinkSAMLSSO#section-PicketLinkSAMLSSO-Concepts