I just need the value of the verifier so that I can use it to retrieve the access token.
I wrote a custom authorization handler which uses Response.ok ( new StringBuilder ( "oauth_token=" ).append ( token ).append ( "&&oauth_verifier=" ).append ( verifier ).toString () ).build () ; I don't need to do any redirects in this case because its a stand-alone Java client which wants to invoke the REST service that is OAuth protected. With this change, I'm able to make it work with Signpost on the client side. I'll try a custom JAX-RS Message Body writer and see if I can get it to work. After you've made this code-change in the framework to support Java clients out of the box, then will it be provided as a patch that I can download from the Apache site and use, or will I have to wait until the next release of CXF? -- View this message in context: http://cxf.547215.n5.nabble.com/OAuth-1-0-in-CXF-2-6-2-tp5713150p5713216.html Sent from the cxf-user mailing list archive at Nabble.com.
