Learning oauth2.0 notes (1)

1.1.  Roles

       RoleOauth defines four roles: oauth sets four roles

   resource owner

Resource owner

      An entity capable of granting access to a protected resource.      When the resource owner is a person, it is referred to as an      end-user.

A resource owner is an entity that allows authorized access to protected resources. When the resource owner is a person, it is called an end user.

      resource server

Resource Server

      The server hosting the protected resources, capable of accepting      and responding to protected resource requests using access tokens.

The resource server is used to host protected resources and has the ability to receive access token requests and respond to protected resources. (Keyword: access tokens) Client

Client
An application making protected resource requests on behalf of the resource owner and with its authorization. the term "client" does not imply any particle implementation characteristics (e.g ., whether the application executes on a server, a desktop, or other devices ).

A client is an app that can use the authorization information of the resource owner to request protected resources. "Client" does not represent any specific reality. (The app can be running on the server, desktop, or other devices) Authorization Server

Authorization Server
The server issuing access tokens to the client after successfully authenticating the resource owner and obtaining authorization.

Authorize the server to verify the identity of the resource owner. After the previous two steps are successful, access and tokens are issued. the interaction between the authorization server and resource server is beyond the scope of this specification. the authorization server may be the same server as the resource server or a separate entity. A single authorization server may issue access tokens accepted by multiple resource servers.

The interaction between the authorized server and the resource server exceeds the scope of this provision.

The authorization server and the resource server can be the same server or a separate entity.

A single authorized server can issue access tokens services to multiple resource servers.