Hi Adam,
well, if you are using Google for authentication, then you
are logging into a google account
If you have GMail, or other google servics (e.g. Picasaweb) then you
already have a google account.
When you log into your google account you are also logging into (in a
way) to all the services you use under that google account.
Such as Gmail, calendar, contacts, picasaweb, etc....and if you have
set it up that way, your app too.
Same is true of Google Apps domain accounts.
Log out of Google and you are effectively logging out of all of them.
Log into one of them, log into all of them - although then the app can
ask you for further confirmation.
If you are accessing one of the others as a service from your app
(e.g. your app looks at your e-mail, or picasa photos or whatever) you
may get an extra step in the login process to get permission for that.
It's explained in the GAE SDK pages on authentication.
I wonder what people out there build real apps on GAE are doing for
authentication?
- going with google accounts?
- building your own authentication system INSIDE GAE (i.e. no Google
login required to access the app, but then the app tries to
authenticate you itself)?
- somehow linking to an authentication service outside of GAE?
I'd like to provide logins to my app to sets of users from different
companies (who may not have Google domains etc) and I don't think I
want to force them all to also have Google accounts.
Recommendations anyone?
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.
