Still under construction ... more details coming soon ...

OAuth 2.0 Consumer for Apache Shindig

...

The OAuth 2.0 specification is here: http://tools.ietf.org/html/draft-ietf-oauth-v2-21

Other helpful OAuth 1.0 and OAuth 2.0 information here: http://oauth.net/2/

For more information on the related service provider (but still separate) click here: OAuth 2.0 Service Provider Implementation in Apache Shindig click here

Also being tracked at https://issues.apache.org/jira/browse/SHINDIG-1624

The consumer implementation is v2-21 compliant and was tested against Google, Facebook and the internal shindig provider documented in this Wiki and linked to above.

Overview

• The OAuth 2.0 Consumer proposal is the combination of a small number of changes to the gadget spec and gadgets.io.makeRequest() API to allow gadgets running in an OpenSocial container to make proxied HttpRequests to service providers protected by OAuth 2.0.
• The Shindig 3.0.0. Java Reference Implementation is an OAuth 2.0-v21 spec compliant server side implementation that supports Authorization Code (3-leggedparty) and Client Credentials (2-leggedparty) flows.  
• It has been tested against Google API, Facebook API and the Shindig Provider developed by Matt and Eric with the "Bearer" Token Type.
• The reference implementation can be extended (via Guice binding injections) to support additional Client Authentication requirements, Grant Types, Token Types, Authorization Responses and Token Responses.
• The default OAuth2Request and OAuth2Store implementations offer other plugin points required for production-ready OAuth 2.0 deployments.  Persistence, Caching and Secret Encryptpion.

Spec Considerations

Currently a gadget declares it's intent to use gadgets.io.makeRequest() to access external resources protected by OAuth 1.with an <OAuth> Service declaration

See spec definition here

<!-- Existing OAuth 1.0 definition -->
<ModulePrefs title="Demo 3-legged OAuth to Shindig">   
  <OAuth>     
    <Service name="shindig">       
      <Request url="http://localhost:8080/oauth/requestToken" />       
      <Authorization url="http://localhost:8080/oauth/authorize?oauth_callback=http://localhost:8080/gadgets/oauthcallback" />       
      <Access url="http://localhost:8080/oauth/accessToken" />     
    </Service>
  </OAuth>
  <Require feature="oauthpopup" />
</ModulePrefs>

Because OAuth 1 and 2 are incompatible  and some of the terminology has changed a new OAuth 2 Service declaration has been proposed here and is the basis of the implementation in Shindig.

See Proposed Changes Here

<!-- Proposed new OAuth 2.0 definition -->
<ModulePrefs title="OAuth2 Demo Gadget -- Authorization Code">
    <OAuth2>
     <!-- name and scope are optional -->
     <Service name="shindig" scope="defaultGadgetScope" >
       <!-- authorization and token endpoint urls are optional -->
       <Authorization url="http://localhost:8080/oauth2/authorize" />
       <Token url="http://localhost:8080/oauth2/token"  />
    </OAuth2>
   <Require feature="oauthpopup" />
</ModulePrefs>

<Authorization> and <Token> urls are optional in the gadget spec.  If they are not explicitly defined in the gadget spec they must be bound on the server.  OAuth 2.0 gadget-to-endpoint binding is left up to the server implementation.

After a gadget has declared it's intent to access OAuth 2.0 protected resources with the <OAuth2> service declaration it can use gadgets.io.makeRequest() in a manner almost identical to OAuth 1.0.  This assumes that the Authorization and Token endpoints have been bound correctly on the server and correct OAuth 2.0 clients are registered.

 function fetchData() {
        url = "http://localhost:8080/social/rest/people/@me/@friends/";
        var params = {};
        params[gadgets.io.RequestParameters.CONTENT_TYPE] =
          gadgets.io.ContentType.TEXT;
        params[gadgets.io.RequestParameters.AUTHORIZATION] =
          gadgets.io.AuthorizationType.OAUTH2;
        params[gadgets.io.RequestParameters.METHOD] =
          gadgets.io.MethodType.GET;
        params[gadgets.io.RequestParameters.OAUTH_SERVICE_NAME] = "shindig";
        params[gadgets.io.RequestParameters.OAUTH_SCOPE] = "requestScopeOverridesGadgetDefault";
        params[gadgets.io.RequestParameters.REFRESH_INTERVAL] = "0";

        gadgets.io.makeRequest(url, function (response) {
          if (response.oauthApprovalUrl) {
            var onOpen = function() {
              showOneSection('waiting');
            };
            var onClose = function() {
              fetchData();
            };
            var popup = new gadgets.oauth.Popup(response.oauthApprovalUrl,
                null, onOpen, onClose);
            $('personalize').onclick = popup.createOpenerOnClick();
            $('approvaldone').onclick = popup.createApprovedOnClick();
            showOneSection('approval');
          } else if (response.data) {
            $('main').appendChild(document.createTextNode(response.data));
            showOneSection('main');
          } else {
            var whoops = document.createTextNode(
                'OAuth error: ' + response.oauthError + ': ' +
                response.oauthErrorText);
            $('main').appendChild(whoops);
            showOneSection('main');
          }
        }, params);
      }

The AuthorizationType.OAUTH2 and RequestParameters.OAUTH_SCOPE are additions for OAuth 2.0 support and need to be proposed.

Running the Demo Gadgets

You will need Google and Facebook accounts and registered applications for these steps....

http://code.google.com/apis/accounts/docs/OAuth2.html

http://developers.facebook.com/docs/authentication/

The redirect_uris for your applications must match the oauth2callback servlet in your shindig environment.

For instance : http://localhost:8080/gadgets/oauth2callback

1. Extract the Shindig trunk from https://svn.apache.org/repos/asf/shindig/
2. Apply the patch from https://reviews.apache.org/r/1947/diff/raw
3. Edit config/oauth2.json - replace the client_id and client_secret placeholders in the "googleApi_client1" and "facebook_client1" clients with the applications you created.  Make sure to keep your OAuth 2.0 secrets secret.
4. Build and deploy the shindig WAR.
5. Run the common container and add the "OAuth2 Demo with Google Provider" or "OAuth2 Demo with Facebook Provider".
6. Click the "Personalize this gadget" link to initiate the OAuth 2.0 Authorization Code (3-legged) flow which will redirect you to the service provider (Google or Fa.cebook) for authorization
7. Enter your credentials for the service provider, don't worry they are safe and never leave Googe/Facebook.
8. The service provider will return an authorization code and subsequently access_token to shindig and the gadget's makeRequest() call will pull your Contacts/Friends.
9. When you are done you can disable your access_token on the service provider site.

Using Google and Facebook and having Google/Facebook accounts and applications is not necessary.  The OAuth 2.0 Consumer should work against any v20 or v21 spec compliant service provider.  It will require writing your gadget and registering it's client in config/oauth2.json

You can also use the Shindig OAuth 2.0 Provider (currently under review) that has been submitted to shindig.  The Consumer contains two sample gadgets that demonstrate the integrated capabilities.

1. Extract the Shindig trunk from https://svn.apache.org/repos/asf/shindig/
2. Apply the patch from https://reviews.apache.org/r/1947/diff/raw
3. Apply the patch from https://reviews.apache.org/r/1940/diff/raw
4. Run the common container and add the "OAuth2 Demo with Shindig Provider (Authorization Code)" or "OAuth2 Demo with Shindig Provider (Client Credentials)
5. Client Credentials does not cause a redirect

   OpenSocial Specification Considerations

6. Running the Demo Gadgets

7. OAuth 2.0 Flow Support

8. High Level Design Overview (NOT DONE)

9. Client Authentication

10. Authorization Response Handling

11. OAuth2CallbackServlet

12. Token Response Handling

13. Grant Types (NOT DONE)

14. Token Types (NOT DONE)

15. Accessing Protected Resources (NOT DONE)

16. Access Token Refresh Flow (NOT DONE)

17. Default Persistence (oauth2.json), Caching and Secret Encryption (NOT DONE)

18. shindig.properties impacts

19. web.xml impacts

20. HOW TO ( NOT DONE)

21. Future Considerations and TODOs