SAML Concepts - Profile: Difference between revisions
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
A ''profile'' is essentially a use case for SAML. A profile combines [[SAML Concepts#SAML_Assertion|assertions]], [[SAML Concepts#SAML_Protocol|protocols]] and [[SAML Concepts#SAML_Binding|bindings]] to support specific use cases. For example, the Web Browser SSO Profile specifies how SAML authentication assertions are communicated between an [[SAML Concepts#Identity_Provider|Identity Provider]] and [[SAML Concepts#Service_Provider|Service Provider]] to enable single sign-on for a browser user. | A ''profile'' is essentially a use case for SAML. A profile combines [[SAML Concepts#SAML_Assertion|assertions]], [[SAML Concepts#SAML_Protocol|protocols]] and [[SAML Concepts#SAML_Binding|bindings]] to support specific use cases. For example, the Web Browser SSO Profile specifies how SAML authentication assertions are communicated between an [[SAML Concepts#Identity_Provider|Identity Provider]] and [[SAML Concepts#Service_Provider|Service Provider]] to enable single sign-on for a browser user. | ||
=SAML Profiles= | =SAML Profiles= | ||
Revision as of 02:39, 21 February 2017
Internal
Overview
A profile is essentially a use case for SAML. A profile combines assertions, protocols and bindings to support specific use cases. For example, the Web Browser SSO Profile specifies how SAML authentication assertions are communicated between an Identity Provider and Service Provider to enable single sign-on for a browser user.
SAML Profiles
- Web Browser Single Sign-On Profile
- Enhanced Client and Proxy (ECP) Profile
- Identity Provider Discovery Profile
- Single Logout Profile
- Assertion Query/Request Profile
- Artifact Resolution Profile
- Name Identifier Management Profile
- Name Identifier Mapping Profile