Do you need to use Oauth for projects that are separated from each other and request each other?

the front end needs to access the resources that can only be viewed by partial login. Design flow:
the front end encrypts the user name and password entered by the user, then sends the post request to the server
the server compares the authentication information with the database, and then returns an Oauth token
. After that, each front end accesses the authenticated resources and sends the token to the server as a request parameter

.

this is a bit of a reference to weibo"s API, to achieve this goal of the same project, will there be a better design?

Apr.07,2021

JSON Web Token (abbreviation JWT) is the most popular cross-domain authentication solution at present. As you said, after the front end submits the information, the back end will return the encoded authriztion value, and the front end is stored in localstorage. The request header for setting token, in the request interceptor carries this token, to complete authentication


.

I wonder if LZ is saying that OAuth2.0
is generally used as a third-party login

.

but I have also used the "password mode" to log in to the system and return access_token. Realize the requirements mentioned by LZ

Menu