Argh! Not so great. The security token seems to be null even though I see the st param on the makeRequest call.
I don¹t see any way inside of my ClientAuthenticationHandler to get at the original request object or the security token. This presents a bit of a problem for me, since we need to pass along a bit of information from the token onto the authorization code request. Ideas? doug On 12/6/11 10:02 AM, "daviesd" <davi...@oclc.org> wrote: > I didn¹t notice that the request coming into addOAuth2Authentication wasn¹t a > HttpServletRequest but instead a org.apache.shindig.gadgets.http.HttpRequest > with a securityToken accessor. Great!
