Today, I was asked by my superior to log in at one place and access multiple stations.
Single sign-on (SSO) SSO allows users to log in once to access all trusted applications in multiple applications. It includes a mechanism to map this primary login to another login for the same user in another application. It is one of the more popular enterprise business integration solutions.
SSO in simple terms is a unified login in one place to manage the common login status of multiple sites.
The “station” we say here is the meaning of the website. Don’t think that mobile access to everything SSO can only solve the website’s problems, but not the multi-sign-on problem
The SSO implementation is also similar to the way you get user information using JWT. Except Oauth2 still requires a login, whereas SSO does not. Let’s just think about it that way
The rough SSO process looks like this.
Take a simple example www.test1.com login in test1 site program, using crawler principle, send user information to request SSO program to verify user information. Then the SSO system returns a Token to the user after successful verification. In fact, the Token principle here is the same as that used by our general small factories. SSO just does a simple redirection here and saves the Token in the Cookie on site 1, and then redirects the Token to site 2 on site 302 as shown below www.test2.com? User_token = XXXXX after saving the Token, Redirects it back to site 1, creating the illusion that the user is just logged in to site 1.