Thursday, August 2, 2012

Introduces Mobile SSO, Access Management Service for Tablets, Smartphones



https://developers.facebook.com/blog/post/640/
https://github.com/facebook/facebook-android-sdk/tree/master/examples
http://stackoverflow.com/questions/4327611/single-sign-on-for-android-facebook
https://developers.facebook.com/docs/mobile/android/sso/#sso
http://cloudnewsdaily.com/2011/05/symplified-introduces-mobile-sso-access-management-service-for-tablets-smartphones/
https://www.pingidentity.com/blogs/pingtalk/index.cfm/2011/5/12/OAuth-20-close-to-solved-SSO-for-mobile-apps-a-different-story


Eran Hammer-Lahav has done an excellent job in explaining the majority of the differences in his articleIntroducing OAuth 2.0. To summarize, here are the key differences:
More OAuth Flows to allow better support for non-browser based applications. This is a main criticisim against OAuth from client applications that were not browser based. For example, in OAuth 1.0, desktop applications or mobile phone applications had to direct the user to open their browser to the desired service, authenticate with the service, and copy the token from the service back to the application. The main criticism here is against the user experience. With OAuth 2.0, there are now new ways for an application to get authorization for a user.
OAuth 2.0 no longer requires client applications to have cryptography. This hearkens back to the old Twitter Auth API, which didn't require the application to HMAC hash tokens and request strings. With OAuth 2.0, the application can make a request using only the issued token over HTTPS.
OAuth 2.0 signatures are much less complicated. No more special parsing, sorting, or encoding.
OAuth 2.0 Access tokens are "short-lived". Typically, OAuth 1.0 Access tokens could be stored for a year or more (Twitter never let them expire). OAuth 2.0 has the notion of refresh tokens. While I'm not entirely sure what these are, my guess is that your access tokens can be short lived (i.e. session based) while your refresh tokens can be "life time". You'd use a refresh token to acquire a new access token rather than have the user re-authorize your application.
Finally, OAuth 2.0 is meant to have a clean separation of roles between the server responsible for handling OAuth requests and the server handling user authorization. More information about that is detailed in the aforementioned article.

No comments: