In my previous article we met oPRO - a Rails engine to build full-fledged OAuth 2 providers. We've already created a server (the actual provider) and a client app. For now, the server has a basic authentication system powered by Devise. Users are able to create applications to receive client and secret keys, authenticate via OAuth 2 and perform sample API requests. However, currently there is no storage mechanism for the user's data on the client side. Moreover, we don't get any information about a user apart from their tokens. This article will address these issues, as well as introducing some more API actions and refactoring the code.
Continue reading %OAuth 2 All the Things with oPRO: Users and API%
by Ilya Bodrov-Krukowski via SitePoint
No comments:
Post a Comment