{"id":258,"date":"2023-03-23T00:14:12","date_gmt":"2023-03-23T00:14:12","guid":{"rendered":"https:\/\/vasanthselvaraj.com\/?p=258"},"modified":"2023-03-23T00:14:17","modified_gmt":"2023-03-23T00:14:17","slug":"single-sign-on-sso-terminologies","status":"publish","type":"post","link":"https:\/\/vasanthselvaraj.com\/?p=258","title":{"rendered":"Single Sign-On (SSO) terminologies"},"content":{"rendered":"\n

Introduction<\/h2>\n\n\n\n

In this post, we will look at different terminologies in SSO. Single Sign-On means use the same credentials everywhere whereas web SSO login once in browser and access multiple websites without authenticating again. When comes to SSO there are multiple names thrown around so lets look one by one<\/p>\n\n\n\n

SAML<\/td>OIDC<\/td><\/tr>
OAUTH<\/td>JWT<\/td><\/tr>
Federated identities<\/td>Federated Access<\/td><\/tr>
Identity provider<\/td>Service provider<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Problem Statement<\/h3>\n\n\n\n

Before we deep dive into topics – understand why SSO ? SSO primarily aim to solve Password Fatigue, Too many disjointed Apps and developer simplicity.<\/p>\n\n\n\n

SAML<\/h4>\n\n\n\n

SAML – Security Assertion Markup Language. Its based on XML to exchange identities between two parties for web single sign on. Most of the corporate applications uses SAML SSO to provide web SSO however current trends modern applications moving towards OAUTH2.0 framework to achieve the same by issuing OIDC or JWT tokens<\/p>\n\n\n\n

OAUTH<\/h4>\n\n\n\n

OAUTH – open authorisation. Its a standard designed to allow website to access resources hosted on other website on behalf of users. OAUTH2 is authorisation protocol not authentication<\/code> protocol. It uses access token to access other application. There are some additional terminologies to learn in OAUTH2<\/p>\n\n\n\n