[
https://issues.apache.org/jira/browse/SHINDIG-897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673767#action_12673767
]
Paul Lindner commented on SHINDIG-897:
--------------------------------------
I modified Cassie's patch a bit and committed that code. I was able to get the
PHP client talking to the URL endpoints defined in the service.
I took out the consumer secret generator hack and moved that to
canonicaldb.json. I also added a number of methods to the OAuthDataStore which
abstract the state changes required for the OAuth dance.
With a little work we can make the OAuthServlet work for any conditions, we
just need to delineate a pass off to the native authentication/authorization UI
flow and provide a callback handler for return from that.
This change also seems to break the samples project, I'm going to commit this
and start clean and see if that fixes it.
> 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: Java
> Reporter: Jacky Wang
> Priority: Minor
> Attachments: alternativeOAuth.patch,
> supports-3-legged-oauth-validation.patch,
> supports-3-legged-oauth-validation.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.
