oltu-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antonio Sanso (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OLTU-96) Improve client API in order to support known Provider
Date Fri, 19 Apr 2013 08:09:15 GMT

    [ https://issues.apache.org/jira/browse/OLTU-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13636174#comment-13636174

Antonio Sanso commented on OLTU-96:

Thanks a lot Sam!! 
I have applied your patch in rev. 1469732.

As a side node we might use the just added OAuthProviderType to include also the info about
the TokenResponse format as for OLTU-98. WDYT?
> Improve client API in order to support known Provider
> -----------------------------------------------------
>                 Key: OLTU-96
>                 URL: https://issues.apache.org/jira/browse/OLTU-96
>             Project: Apache Oltu
>          Issue Type: Task
>          Components: oauth2-client
>            Reporter: Antonio Sanso
>            Assignee: Antonio Sanso
>         Attachments: OLTU-96.patch
> According to the Oltu documentation [0] when using Oltu library client side is always
needed to specify the authorization and token location e.g. 
>          OAuthClientRequest request = OAuthClientRequest
>             .authorizationLocation("https://graph.facebook.com/oauth/authorize")
>             .setClientId("your-facebook-application-client-id")
>             .setRedirectURI("http://www.example.com/redirect")
>             .buildQueryMessage();
> even for well known Provider e.g. Facebook, Google etc.
> Given that they should not change really often it would be nice to have preconfigured
> [0] https://cwiki.apache.org/confluence/display/OLTU/OAuth+2.0+Client+Quickstart

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message