Re: [google-appengine] Federated login and integrated applications

2011-02-09 Thread Iap
>
>
> So, to sum this up: with federated login enabled, is there a way to
> implement login for applications which does not require user interaction?
> For example a cron job takes username & password from a file when loggin in
> to my app at GAE. Just like ClientLogin does?
>

What if  you save the authorized token instead of the username and password?
>From the interaction diagram in
http://code.google.com/apis/accounts/docs/OpenID.html#oauth,
it seems that the action in step 9 can be performed in the cron job too
provided that the cron job has the authorized token.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.



Re: [google-appengine] Federated login and integrated applications

2011-02-09 Thread anatoliy
Singuan, the identifier (OAuth request token) has limited lifetime. 
Therefore, there is no sense to store it as it will be obsolete rather soon.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.



Re: [google-appengine] Federated login and integrated applications

2011-02-09 Thread Robert Kluin
IIRC, gdata access tokens (which is what you'll upgrade the request
token to) don't expire.  Are you sure App Engine access tokens expire?



Robert





On Wed, Feb 9, 2011 at 14:40, anatoliy  wrote:
> Singuan, the identifier (OAuth request token) has limited lifetime.
> Therefore, there is no sense to store it as it will be obsolete rather soon.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.



Re: [google-appengine] Federated login and integrated applications

2011-02-11 Thread anatoliy
Thank you guys!

GAE OAuth docs clearly say that "The access token is valid until the user 
revokes the access using the Google Accounts management interface."

Sorry for the useless question - didn't notice that at first reading :(

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.