Hi
On 27/08/12 12:38, mayankeagle wrote:
Hi,
I have a stand-alone Java client developed using Signpost, which I'm trying
to use to invoke a REST web-service that is protected via OAuth 1.0 on CXF
2.6.2.
I'm able to obtain the request token and the session authenticity token, but
after that when I send the authorization decision as allow, then I get an
error on the server side saying that the oauth_token parameter is missing.
However, I have checked that the oauth_token parameter is present in the
HttpParameters of the DefaultOAuthConsumer object of Signpost.
What could be the reason for this issue? My URL looks something like:
/services/authorize/decision?session_authenticity_token=ef07b9e5-24a1-4b71-b492-5794e8e80895&oauthDecision=allow
I wonder why 'oauth_token' does not make it into the actual URI ?
Perhaps it's passed in the request body ?
Example,
POST
/services/authorize/decision?session_authenticity_token=ef07b9e5-24a1-4b71-b492-5794e8e80895&oauthDecision=allow
oauth_token=12345678
?
Can you confirm Signpost actually passes 'oauth_token' to the service ?
You can add a logging feature to the service endpoint
Cheers, Sergey
Any help would be appreciated.
Thanks.
--
View this message in context:
http://cxf.547215.n5.nabble.com/OAuth-1-0-in-CXF-2-6-2-tp5713150.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
