If you have a look back through the groups history you will see the
google response
is they don't want people customising the google login because that
detracts from the
trust in google etc......

There's some lengthy discussions about this in the archives,

Also are you talking python or java.  If java then I will shut up.

If python, then start looking at repoze.who/what wsgi middleware
if you want to write your own auth plugin that can be combined with
the
redirecting form and auth_tkt plugins that all work fine on appengine.

I am using these for www.qtracker.com.au and all user details are
managed
in the datastore.

If you want more info, holler.


T

On Sep 26, 5:08 pm, deuce4 <[email protected]> wrote:
> Hi-
>
> I am creating an app that requires users to log in to save settings,
> etc.
>
> As this is a project for a commercial client, I have looked into ways
> to "roll my own" authorization and authentication but of course that
> is a lot of work.
>
> Is there any way to customize the normal Google User Service so that
> the login can be more compact, perhaps shown just in a small window,
> rather that a redirect to a new page? (using the code:
> signInLink.setHref(loginInfo.getLoginUrl()); )
>
> Or some other way that isn't so distracting with user's being taken
> away from the main site?  I'm not really into the OpenID solutions for
> the same reason.
>
> Alternatively, are there any open source libraries that can be used to
> create a user sign-in system that is exclusive to a particular app,
> perhaps using Datastore to store users and user data that has all the
> typical sign in features, such as "forgot password", etc.?
>
> Thanks

-- 
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.

Reply via email to