ASP. NET MVC SSO Single Sign-on design and implementation

Single Sign-on:

Single Sign-on (SSO) means that multiple systems are processed through one user authorization center and can be authorized in all other systems without having to log in again; there are many ways to do this, and the following example is an SSO implemented by means of a cookie.

SSO requires a separate authentication center relative to single-system logins, and only the authentication center can accept security information such as user names and passwords, and other systems do not provide a login entry.

If multiple systems are now integrated and managed via single sign-on, the process is as follows:

A) The user accesses System 1, System 1 discovers that the user is not logged in to the SSO Authentication Center and transmits its own address as a parameter.

b) The SSO Authentication Center discovers that the user is logged in and directs the user to the login page.

c) The user enters the user name and password to submit the login request.

d) SSO verifies user information, such as authentication by saving the user information cookie and jumping to the original request address.

e) When system 2 goes to login, the system will jump to the authentication center, verify the login, log in, and jump to the original requested address.

Every time you log in in the blog park, you can see

Https://passport.cnblogs.com/user/signin?ReturnUrl=http://i.cnblogs.com/EditPosts.aspx?opt=1

Then the URL to jump after login is ReturnUrl

Later in the major web site when you can log on a little attention, a lot of places will use this feature.

The following is the SSO usage process:

Source code Download Path: Https://github.com/zhaochengshen/SSO

ASP. NET MVC SSO Single Sign-on design and implementation