JWT vs OAuth 2.0 vs SAML vs SSO
JWT vs OAuth 2.0 vs SAML vs SSO
The main differences between JSON web tokens (JWT) and OAuth 2.0 and Security Assertions Markup Language (SAML) tokens are:
JWTs could be used internally in SPAs, stateless situations, or authorizations for APIs. JWTs are JSON of course.
OAuth is always external and authorization server is the server that grants it. OAuth is based on HTTP request parameters and JSON response message.
SAML is always external and identity provider is the server that grants it. SAML is thought of as more enterprise. SAML has challenges of coding XML parsing, encryption, signing, and validation on the client. SAML 2.0 introduced many new protocols, including the assertion query and
request, authentication request, artifact resolution, name identifier
management, name identifier mapping, and single logout protocols. SAML 2.0 separated bindings from underlying profiles such as reverse SOAP, SAML URI, and HTTP redirect (GET) bindings.
Single SignOn (SSO) is the overall approach of authentication. OAuth and SAML are just ways to implement SSO. SSO is more expansive than OAuth and SAML. SSO could be done internally at a company that has 3 customer applications and one might want a single signon rather than having to sign in on each application. SAML 2 added more browser flow options such as SSO, artifact resolution, name identifier mapping, and SAML attribute profiles.
The disadvantage to SSO is once one website is hacked then any websites linked via SSO are essentially hacked.
Comments
Post a Comment