[
https://issues.apache.org/jira/browse/SHINDIG-897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669670#action_12669670
]
Paul Lindner commented on SHINDIG-897:
--------------------------------------
Hi Jacky,
3-legs, nice! very exciting.
Can you write up what you changed? Also, since this is a new interface we'll
expect people to implement I think we should have some better documentation
(and yes, I know the old interface didn't have any either..)
Let's see if I understand what you've done.
* Replace OAuthLookupService with GadgetDirService
* Replace SampleContainerOAuthLookupService with SampleGadgetDirOAuthService
* GadgetDirService adds: userHasAppInstalled(), getAppId(), getDomain(),
getContainer(), removes thirdPartyHasAccesstoUser() and
* Add new Interface OAuthService with methods getConsumer() and getAccessor();
* Add samplecontainer version of OAuthService
Initial thoughts:
* Many containers will have more granular permissions than 'hasAppInstalled()',
which this change seems to favor explicitly.
* My OAuth-fu is weak, how do you implement the UI for login/authorization?
> Add 3-legged OAuth validation support for RESTful api
> -----------------------------------------------------
>
> Key: SHINDIG-897
> URL: https://issues.apache.org/jira/browse/SHINDIG-897
> Project: Shindig
> Issue Type: Improvement
> Components: RESTful API (Java)
> Reporter: Jacky Wang
> Priority: Minor
> Attachments: add-3-legged-oauth.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> RESTful API now supports 2-legged OAuth, and we'd like to see it supports
> validation for requests issued by 3-legged OAuth client.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
