[Seaside] Oauth without callbacks question
Mariano Martinez Peck
marianopeck at gmail.com
Wed Apr 30 18:24:39 UTC 2014
Indeed, it was nothing strange what I seemed to need. The thing is that
OAuth get's a bit complicated when you don't use the OAuth callbacks.
Sorry to bother you. It is working now!!!
On Wed, Apr 30, 2014 at 3:19 PM, Johan Brichau <johan at inceptive.be> wrote:
> Hi Mariano,
> I must say I have a bit of difficulties to understand what control flow
> you are trying to achieve.
> But, as you mention, is this not just a two-step process then:
> - ask for the code in the app
> - do the redirect
> something like:
> callback:[ requestcode:= self call: InputDialogWindow. self
> requestContext redirectTo: (self oathService loginUrlFor: requestcode)];
> with: 'login'
> But I'm probably missing something in your question as I have never used
> On 29 Apr 2014, at 22:46, Mariano Martinez Peck <marianopeck at gmail.com>
> > self requestContext
> > redirectTo: (self oauthService loginUrlFor: requestToken) ;
> > respond.
> > 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.
> > 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...
> seaside mailing list
> seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside