RSS

OAuth 2.0 Authorization Protocol

17 Jan

Oauth 2.0 having four types of scenarios as follows

1. Authorization code – A resource owner is able to authenticate directly with an authorization server, and passes on an “authorization code” to the client app.

Oauth-2.0-Authorization-code

2. Implicit – For client apps which are implemented in a browser using a scripting language (such as JavaScript). here client is not validating

Oauth-2.0-Implicit

3. Resource owner credentials – Where there is a high degree of trust between the resource owner and the client app (e.g. a trusted client app on a resource owner’s mobile device). we are using this scenario in mobile applications because redirection is not possible with mobile apps.

Oauth-2.0-Resource owner credentials

4. Client credentials – For access to protected resources that are under the control of the client app (and not any specific/individual resource owner). This is using for public resource as well as this scenario represented 2-legged OAuth

Oauth-2.0-Client credentials

About these ads
 
Leave a comment

Posted by on January 17, 2013 in java, wso2

 

Tags: , ,

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
Follow

Get every new post delivered to your Inbox.

%d bloggers like this: