Re: [Resin-interest] Using Google id's with Resin

2011-10-15 Thread Stargazer
On 25-Sep-2011 18:55, Jeff Schnitzer wrote:
 How are you getting the person's real name out of GAE's UserService?
 I don't see that.  Maybe this is just something you get with Android
 auth?

 The short answer is to use OpenID (and OAuth to get permission on
 extra fields).  But there is a problem with this - if you have a
 database full of google ids (not openids) there's no way to migrate.
 You can switch GAE to federated login and you'll get both the google
 id and openid, which will let you start populating your database when
 people log in, but to go full openid you'll have to do email matching
 with the accounts that haven't set their openid.  Messy.
Hi Jeff  list!

Thanks. This is something I have to do now. I was hoping for some 
example I can use, in our case there is nothing legacy at all, its an 
empty db. All I want is for users to visit the site, see one of those 
popup boxes you see where it asks you to login with Google, get 
authenticated and continue back to my Resin site as if they are logged 
into Google. I don't need any of the extra fields mentioned earlier - 
just the fact they are have a legit Google acc.

I read up on federated login and think that's it, Scott also mentioned a 
future Resin release would include this but I'm hoping for something 
quick now please.

Thanks

-- Carl

 Jeff

 On Sun, Sep 25, 2011 at 9:45 AM, Stargazerstarga...@blueyonder.co.uk  wrote:
 We have a Resin powered JEE app and are expanding it to work with
 Android. One of the cool things on Android is you know the user is
 logged into a Google account. With the Google App Engine, you can do
 more that just authenticate since they provide all the back end service
 data. For example, if I created a simple App Engine app which asked for
 the Google id and password, I could then say Hi John having pulled
 John as the real username, rather than the email address.

 So to expand we can either (gulp) lose Resin and move entirely to the
 App Engine, which I really don't want to do, or replicate the
 authentication system Google uses, as in the simple example above, to do
 it on Resin (which is what I prefer). In other words I want to
 authenticate a valid Google user using Resin but never see the password.

 I see this issue as becoming more and more common, for example Google
 just opened the API for Google+, and a great use case for us is to be
 able to access a users circles from server side java.

 So as usual its over to you smarts on this list for ideas, or
 suggestions such as if I should be looking at some OpenId or whatever
 based system I can roll in ;-) Sincere thanks...


 ___
 resin-interest mailing list
 resin-interest@caucho.com
 http://maillist.caucho.com/mailman/listinfo/resin-interest


 ___
 resin-interest mailing list
 resin-interest@caucho.com
 http://maillist.caucho.com/mailman/listinfo/resin-interest




___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


Re: [Resin-interest] Using Google id's with Resin

2011-09-28 Thread Scott Ferguson
On 09/25/2011 09:45 AM, Stargazer wrote:
 We have a Resin powered JEE app and are expanding it to work with
 Android. One of the cool things on Android is you know the user is
 logged into a Google account. With the Google App Engine, you can do
 more that just authenticate since they provide all the back end service
 data. For example, if I created a simple App Engine app which asked for
 the Google id and password, I could then say Hi John having pulled
 John as the real username, rather than the email address.

I've also added this as a bug report at 
http://bugs.caucho.com/view.php?id=4780.

At minimum, we should have a built-in open-id authenticator and login.

-- Scott

 So to expand we can either (gulp) lose Resin and move entirely to the
 App Engine, which I really don't want to do, or replicate the
 authentication system Google uses, as in the simple example above, to do
 it on Resin (which is what I prefer). In other words I want to
 authenticate a valid Google user using Resin but never see the password.

 I see this issue as becoming more and more common, for example Google
 just opened the API for Google+, and a great use case for us is to be
 able to access a users circles from server side java.

 So as usual its over to you smarts on this list for ideas, or
 suggestions such as if I should be looking at some OpenId or whatever
 based system I can roll in ;-) Sincere thanks...


 ___
 resin-interest mailing list
 resin-interest@caucho.com
 http://maillist.caucho.com/mailman/listinfo/resin-interest




___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


[Resin-interest] Using Google id's with Resin

2011-09-25 Thread Stargazer
We have a Resin powered JEE app and are expanding it to work with 
Android. One of the cool things on Android is you know the user is 
logged into a Google account. With the Google App Engine, you can do 
more that just authenticate since they provide all the back end service 
data. For example, if I created a simple App Engine app which asked for 
the Google id and password, I could then say Hi John having pulled 
John as the real username, rather than the email address.

So to expand we can either (gulp) lose Resin and move entirely to the 
App Engine, which I really don't want to do, or replicate the 
authentication system Google uses, as in the simple example above, to do 
it on Resin (which is what I prefer). In other words I want to 
authenticate a valid Google user using Resin but never see the password.

I see this issue as becoming more and more common, for example Google 
just opened the API for Google+, and a great use case for us is to be 
able to access a users circles from server side java.

So as usual its over to you smarts on this list for ideas, or 
suggestions such as if I should be looking at some OpenId or whatever 
based system I can roll in ;-) Sincere thanks...


___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


Re: [Resin-interest] Using Google id's with Resin

2011-09-25 Thread Jeff Schnitzer
How are you getting the person's real name out of GAE's UserService?
I don't see that.  Maybe this is just something you get with Android
auth?

The short answer is to use OpenID (and OAuth to get permission on
extra fields).  But there is a problem with this - if you have a
database full of google ids (not openids) there's no way to migrate.
You can switch GAE to federated login and you'll get both the google
id and openid, which will let you start populating your database when
people log in, but to go full openid you'll have to do email matching
with the accounts that haven't set their openid.  Messy.

Jeff

On Sun, Sep 25, 2011 at 9:45 AM, Stargazer starga...@blueyonder.co.uk wrote:
 We have a Resin powered JEE app and are expanding it to work with
 Android. One of the cool things on Android is you know the user is
 logged into a Google account. With the Google App Engine, you can do
 more that just authenticate since they provide all the back end service
 data. For example, if I created a simple App Engine app which asked for
 the Google id and password, I could then say Hi John having pulled
 John as the real username, rather than the email address.

 So to expand we can either (gulp) lose Resin and move entirely to the
 App Engine, which I really don't want to do, or replicate the
 authentication system Google uses, as in the simple example above, to do
 it on Resin (which is what I prefer). In other words I want to
 authenticate a valid Google user using Resin but never see the password.

 I see this issue as becoming more and more common, for example Google
 just opened the API for Google+, and a great use case for us is to be
 able to access a users circles from server side java.

 So as usual its over to you smarts on this list for ideas, or
 suggestions such as if I should be looking at some OpenId or whatever
 based system I can roll in ;-) Sincere thanks...


 ___
 resin-interest mailing list
 resin-interest@caucho.com
 http://maillist.caucho.com/mailman/listinfo/resin-interest



___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


Re: [Resin-interest] Using Google id's with Resin

2011-09-25 Thread Stargazer
On 25-Sep-2011 18:55, Jeff Schnitzer wrote:
 How are you getting the person's real name out of GAE's UserService?
 I don't see that.  Maybe this is just something you get with Android
 auth?

Could be, though where I got that from stongly suggests just being 
authed in a GAE app gives it to you: 
http://www.youtube.com/watch?v=M7SxNNC429U (From 13 min onwards)

 The short answer is to use OpenID (and OAuth to get permission on
 extra fields).  But there is a problem with this - if you have a
 database full of google ids (not openids) there's no way to migrate.
 You can switch GAE to federated login and you'll get both the google
 id and openid, which will let you start populating your database when
 people log in, but to go full openid you'll have to do email matching
 with the accounts that haven't set their openid.  Messy.

 Jeff

 On Sun, Sep 25, 2011 at 9:45 AM, Stargazerstarga...@blueyonder.co.uk  wrote:
 We have a Resin powered JEE app and are expanding it to work with
 Android. One of the cool things on Android is you know the user is
 logged into a Google account. With the Google App Engine, you can do
 more that just authenticate since they provide all the back end service
 data. For example, if I created a simple App Engine app which asked for
 the Google id and password, I could then say Hi John having pulled
 John as the real username, rather than the email address.

 So to expand we can either (gulp) lose Resin and move entirely to the
 App Engine, which I really don't want to do, or replicate the
 authentication system Google uses, as in the simple example above, to do
 it on Resin (which is what I prefer). In other words I want to
 authenticate a valid Google user using Resin but never see the password.

 I see this issue as becoming more and more common, for example Google
 just opened the API for Google+, and a great use case for us is to be
 able to access a users circles from server side java.

 So as usual its over to you smarts on this list for ideas, or
 suggestions such as if I should be looking at some OpenId or whatever
 based system I can roll in ;-) Sincere thanks...


 ___
 resin-interest mailing list
 resin-interest@caucho.com
 http://maillist.caucho.com/mailman/listinfo/resin-interest


 ___
 resin-interest mailing list
 resin-interest@caucho.com
 http://maillist.caucho.com/mailman/listinfo/resin-interest




___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest