SAML Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 27: | Line 27: | ||
There is a ''trust relationship'' between the Identity Provider and and the Service Provider. | There is a ''trust relationship'' between the Identity Provider and and the Service Provider. | ||
=Web Browser Single Sign-On= | =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. | 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== | |||
=To Deplete= | =To Deplete= | ||
Revision as of 01:21, 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.
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
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