Hi, If I read your email correctly, this is expected behavior. See this article for more details: http://code.google.com/appengine/articles/auth.html
To summarize, the issue is that your app can only serve the authentication page that matches the type of authentication chosen when registering your application. Since the app is using Google Apps authentication, you can not sign in to any part of the actual application with a Google Accounts email, even if you are an admin for that app. This restriction does not apply to the admin console - so you can still upload your application and view the Admin Console pages for an app with Google Apps authentication using a Google Accounts account. Hope this helps clarify the issue. -Marzia On Wed, Jan 21, 2009 at 4:53 PM, theillustratedlife <toonscr...@nvbell.net> wrote: > > I've got a Django app with some functions I'd like to keep people from > running, so I've sandboxed them to admins using app: > > - url: /[a-zA-Z/_]*/admin/.* > script: main.py > login: admin > > - url: /.* > script: main.py > > > It's working too well - I'm an admin, and I can't access them! > > My friend is the admin for the domain it's on. He created the app > with Google Apps authentication (which it doesn't look like I could > change if I wanted to). He created me a Google Apps account and made > it an admin. I can access the admin section of http://google.com/a/ > for this domain just fine, yet I still get this forbidden error when I > try to access resources protected by app.yaml. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
