On 28/08/12 07:33, mayankeagle wrote:
I also tried with a Javascript client now that I made work with CXF 2.6.1
earlier. It gives an error on the server side saying "No message body writer
has been found for response class OOBAuthorizationResponse".
Sergey, I remember you'd mentioned that in 2.6.1 the OOB support was removed
but was added again in 2.6.2. I'm not sure why I'm getting this error in the
Javascript client though. In the Java client, for a similar
/authorize/decision URL, I'm getting another value of the session
authenticity token.
Not sure why the server side is behaving differently for 2 clients with the
same value of consumer key/ secret/ call-back URL. In the Java client, I get
a response similar to the one that I got for the /authorize call which
includes an authenticity token, and in the Javascript client I get this
error about the OOBAuthorizationResponse class.
I do not know how you made 2.6.1 recognize OOB so I can not comment on
that. Please check again my earlier response on how to make
OOBAuthorizationResponse handled.
OOBAuthorizationResponse can be returned as a simple form payload too,
but that is not supported right now, my understanding is that it is not
the way one would offer an OOB data to the end user
Cheers, Sergey
--
View this message in context:
http://cxf.547215.n5.nabble.com/OAuth-1-0-in-CXF-2-6-2-tp5713150p5713190.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
