SAML Web Browser Single Sign-On Profile: Difference between revisions
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
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. The SSO implies standard browsers, and multiple service providers. With SAML-based SSO is that a user password never crosses a firewall. | 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. The SSO implies standard browsers, and multiple service providers. With SAML-based SSO is that a user password never crosses a firewall. | ||
Web browser SSO uses the [[SAML Authentication Request Protocol|Authentication Request protocol]], in conjunction with the HTTP Redirect, HTTP POST, and HTTP Artifact | Web browser SSO uses the [[SAML Authentication Request Protocol|Authentication Request protocol]], in conjunction with the HTTP Redirect, HTTP POST, and [[SAML HTTP Artifact Binding|HTTP Artifact binding]]. | ||
Revision as of 05:01, 21 February 2017
Internal
Overview
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. The SSO implies standard browsers, and multiple service providers. With SAML-based SSO is that a user password never crosses a firewall.
Web browser SSO uses the Authentication Request protocol, in conjunction with the HTTP Redirect, HTTP POST, and HTTP Artifact binding.