Hi
On 23/07/13 11:13, mayankeagle wrote:
Hi Sergey,
We don't bind it to an HTML as this is being invoked from a background
service without a user-interface. I understand that this is happening one
step before the OOBResponse comes, but do I need to write a custom HTML
provider/ formatter to render this? Earlier I wasn't doing anything - I used
to get the ns2 XML as a response to the authorize call and then I parsed it
to get the session authenticity token.
Can you please make sure that this background service sets HTTP Accept:
application/xml ? In CXF 2.7.5 the way the final response type is
calculated has changed, what may be happening is that the client sets no
Accept type, which becomes a wildcard after the intersection and as per
JAX-RS rules this is defaulted to application/octet-stream - if your
custom writer has @Produces(application/xml) then it won;t be chosen
FYI, I have just validated that a command-line client works OK in our
OAuth1 demo (where it parses the authorization challenge manually)
Cheers, Sergey
--
View this message in context:
http://cxf.547215.n5.nabble.com/OAuth-1-0-with-CXF-2-7-5-tp5731305p5731314.html
Sent from the cxf-user mailing list archive at Nabble.com.
