Loading ...

Oauth 2 Parts

Hello everybody,

today  I want to describe for main components of OAuth 2, which should be implemented by any framework which claims to be programmer friendsly implementation of OAuth 2.

OAuth2 compoments.png

We will start from left botton box, or from user. So, user as usually is something or more precise somebody who initiate actions on UI. Something can also be selenium web driver implementation or something similar. 

Next goes client. Or if to add another key word client application. There are plenty of them: angularjs app, iOs app, iPhone app, Android app, Xamarin app, etc.

Authorization server is intended to be somebody, who generates tokes for each separate user. Token will consist information about user credentials and quite often user permissions for resources.

Resource server receives incoming information from client and makes a decision, to give to client and then to user requested resources or send him back to Authorization server for new portion of credentials.