<div dir="ltr">Hi guys,<div><br></div><div>I am trying to use OAuth (as a client) to a OAuth server in which the callbacks are a bit messy. So for the moment, assume I cannot specify a callback. So the only option I have right now (this is a prototype anyway) is to copy and paste the "verifier" so that I can later get the access token. I am basing my code in Sven's great Seaside demo. However, and here is the problem, he does this to go to the authentication page:</div>
<div><br></div><div><div><span class="" style="white-space:pre"> </span></div><div><span class="" style="white-space:pre"> </span>self requestContext</div><div><span class="" style="white-space:pre"> </span>redirectTo: (self oauthService loginUrlFor: requestToken) ; </div>
<div><span class="" style="white-space:pre"> </span>respond.</div><div><br></div><div>What happens here in my app, is that the browser redirects of course to the OAuth authorization server where I finally can see the verifier code. But...say I have to enter this code in my app...there is no way (as far as I understand) to map it to the (previously stored somewhere) request token. So I don't know which request token to use.</div>
<div><br></div><div>So I think the only option is that the above redirect in fact opens another tab in the browser and that my seaside apps holds into the current request token. Somehow, I would like seaside to then ask for a verification code or something...</div>
<div><br></div><div>Is that possible? Any idea how can achieve that?</div><div><br></div><div>Thanks in advance, </div><div><br></div>-- <br>Mariano<br><a href="http://marianopeck.wordpress.com" target="_blank" class="vt-p">http://marianopeck.wordpress.com</a><br>
</div></div>