Question about Oauth
Locked
 
|
Hi,
Sorry for the multiple list mail. I am analyzing the possibility to implement a API that requires OAuth. I have been reading this link from Sven: https://github.com/svenvc/docs/blob/master/zinc/zinc-sso-paper.md and I have a few questions:
1) I get lost in the #handleOAuth1Callback: part. I understand I need to provide to oauth a callback url so that this is call once the user has logged in. The thing is that Sven demo seems to be using a (RESTfull) server directly. In my case, this is a Seaside app. So...how should I do this? I guess I could create a WAComponent but then I should use Seaside rest or something? Because I need to map that url to the component (and implement handleRequest: in the component?). Is there another way? 2) #loginUrlFor: seems to only set 'oauth_token' however, my protocol says the url should be: <a href="https://whatever/authorize?key={oauth_consumer_key}&token={oauth_token}">https://whatever/authorize?key={oauth_consumer_key}&token={oauth_token} would that still work or I should adapt it? 3) Does anyone tested the mention code/repository in GemStone? Thanks in advance, Mariano http://marianopeck.wordpress.com _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Re: Question about Oauth
|
|
Have in mind that these days doesn’t pay off to do all yourself.
The social APIs of the vendors are very easy to use in js (even more than with the callback way) And, if that weren’t enough, you have this: So the old way for me is a game-over tactic PS: not trying to downplay anything here, just send a heads up On Apr 17, 2014, at 4:37 PM, Mariano Martinez Peck <[hidden email]> wrote:
_______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Re: Question about Oauth
|
|
In reply to this post by Mariano Martinez Peck
There is a Seaside example (look in the repository) and even a live demo: http://sso.doit.st
On 17 Apr 2014, at 21:37, Mariano Martinez Peck <[hidden email]> wrote: > Hi, > > Sorry for the multiple list mail. > > I am analyzing the possibility to implement a API that requires OAuth. I have been reading this link from Sven: https://github.com/svenvc/docs/blob/master/zinc/zinc-sso-paper.md and I have a few questions: > > 1) I get lost in the #handleOAuth1Callback: part. I understand I need to provide to oauth a callback url so that this is call once the user has logged in. The thing is that Sven demo seems to be using a (RESTfull) server directly. In my case, this is a Seaside app. So...how should I do this? I guess I could create a WAComponent but then I should use Seaside rest or something? Because I need to map that url to the component (and implement handleRequest: in the component?). Is there another way? > > 2) #loginUrlFor: seems to only set 'oauth_token' however, my protocol says the url should be: https://whatever/authorize?key={oauth_consumer_key}&token={oauth_token} > would that still work or I should adapt it? > > 3) Does anyone tested the mention code/repository in GemStone? > > > Thanks in advance, > > -- > Mariano > http://marianopeck.wordpress.com > _______________________________________________ > seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Re: Question about Oauth
|
|
If I understood correctly what Mariano needs is server side OAuth.
I might need this too, because to properly integrate managed accounts in Android, you must have something very similar to OAuth (tokens, etc.) Otherwise hello.js for the browser will work, and Zinc's SSO to access an API using Smalltalk. Regards! Esteban A. Maringolo 2014-04-17 16:50 GMT-03:00 Sven Van Caekenberghe <[hidden email]>: > There is a Seaside example (look in the repository) and even a live demo: http://sso.doit.st > > On 17 Apr 2014, at 21:37, Mariano Martinez Peck <[hidden email]> wrote: > >> Hi, >> >> Sorry for the multiple list mail. >> >> I am analyzing the possibility to implement a API that requires OAuth. I have been reading this link from Sven: https://github.com/svenvc/docs/blob/master/zinc/zinc-sso-paper.md and I have a few questions: >> >> 1) I get lost in the #handleOAuth1Callback: part. I understand I need to provide to oauth a callback url so that this is call once the user has logged in. The thing is that Sven demo seems to be using a (RESTfull) server directly. In my case, this is a Seaside app. So...how should I do this? I guess I could create a WAComponent but then I should use Seaside rest or something? Because I need to map that url to the component (and implement handleRequest: in the component?). Is there another way? >> >> 2) #loginUrlFor: seems to only set 'oauth_token' however, my protocol says the url should be: https://whatever/authorize?key={oauth_consumer_key}&token={oauth_token} >> would that still work or I should adapt it? >> >> 3) Does anyone tested the mention code/repository in GemStone? >> >> >> Thanks in advance, >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> _______________________________________________ >> seaside mailing list >> [hidden email] >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > _______________________________________________ > seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
In reply to this post by Mariano Martinez Peck
On Thu, Apr 17, 2014 at 9:37 PM, Mariano Martinez Peck
<[hidden email]> wrote: > Hi, > > Sorry for the multiple list mail. > > I am analyzing the possibility to implement a API that requires OAuth. I > have been reading this link from Sven: > https://github.com/svenvc/docs/blob/master/zinc/zinc-sso-paper.md and I have > a few questions: > > 1) I get lost in the #handleOAuth1Callback: part. I understand I need to > provide to oauth a callback url so that this is call once the user has > logged in. The thing is that Sven demo seems to be using a (RESTfull) server > directly. In my case, this is a Seaside app. So...how should I do this? I > guess I could create a WAComponent but then I should use Seaside rest or > something? Because I need to map that url to the component (and implement > handleRequest: in the component?). Is there another way? something like this may work: html callbacks store: (MyOAuthCallback on: [ ]) Cheers Philippe _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Re: Question about Oauth
|
|
In reply to this post by Esteban A. Maringolo
On Sun, Apr 20, 2014 at 10:40 PM, Esteban A. Maringolo <[hidden email]> wrote: If I understood correctly what Mariano needs is server side OAuth. Actually, I need client-side OAuth. I checked hello.js but the server that provides me the API and that requires OAuth is NOT a social network or whatever. Is not listed in the supported servers from hello.js. So I don't know...maybe it is easier to use Zinc's SSO. In fact, as Sven pointed out, there is a nice example of SSO and Seaside!
Mariano http://marianopeck.wordpress.com _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Re: Question about Oauth
|
|
In reply to this post by Philippe Marschall
On Mon, Apr 21, 2014 at 6:14 AM, Philippe Marschall <[hidden email]> wrote:
Thanks Philippe. Sven pointed me to a Seaside example and indeed he does that: | callback url | callback := WAActionCallback on: [ self handleCallback ] . url := html actionUrl copy addField: (html callbacks store: callback).
Thanks guys. Cheers Mariano http://marianopeck.wordpress.com _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
«
Return to Seaside General
|
1 view|%1 views
| Free forum by Nabble | Edit this page |