Some Thoughts on authentication and authorization

  Recently the need to integrate the two systems together, such as A reception request can do something Platform A personal account of the background after a successful login A, B foreground background login request B can be operated personal accounts of some of the B platform is successful, and now two platforms may only use a login and registration page.

 

B platform will return after a successful login token, each individual service request will bring the token.

 

I understand the authentication and authorization process is as follows.

After the user submits the login form as verification is successful, sends the user name stored in the session object in the background, the background interceptor to intercept a particular request, such as request under admin path, and then queries whether the stored user session, decided to jump to the release or log in page.

 

Guess you like

Origin www.cnblogs.com/zplogo/p/11082959.html