AFAIK, it doesn't really matter if you are not going to utilize Google's User API.
Also, you are able to use your own custom authentication AND Google's service if you want to; it makes your implementation a bit more complex, but that is actually what I do. On Thursday, August 9, 2012 1:09:10 PM UTC-4, zharvey wrote: > > Thanks Michael! > > Just one quick followup on the 3rd item: if I want to use my own > authorization services, which option do I select on the initial app > creation screen? It doesn't provide an option like "None of the above", it > forces me to pick one. Or does it not matter? Thanks again! > > On Thursday, August 9, 2012 1:04:23 PM UTC-4, Michael Hermus wrote: >> >> 1) You need to set up your domain with Google Apps and then you can >> configure your GAE app to use the custom domain: >> https://developers.google.com/appengine/docs/domain >> >> 2) The App title is for displaying in the Google Authentication process >> to users (if you use it). It has nothing to do with your HTML pages. >> >> 3) You are free to implement whatever custom authentication you like; >> those options are if you want to use Google's built in User Authentication >> service. >> >> On Thursday, August 9, 2012 11:18:02 AM UTC-4, zharvey wrote: >>> >>> Last night I read the online docs for GAE and today I am trying to set >>> up my first GAE app. Three questions that are all similarly-related: >>> >>> (1) I want to purchase my own domain (e.g. my-app.com); but during the >>> app creation process I have to specify an app ID of "my-app.appspot.com". >>> How do I configure my GAE app so that it is "hosted" from my-app.comand not >>> the appspot domain? >>> >>> (2) I would like to display my own page titles via HTML head/title tags, >>> but during the app creation process I have to specify an "App Title". Does >>> this mean all pages of my app will be "overridden" with this specified >>> title, and if so, how to I override that title with my own ones (for each >>> page)? If not, then where is this App Title used/displayed? >>> >>> (3) I want to authenticate my app's users using my own OWASP-compliannt >>> authentication service (so that, say, john...@example.com can sign up >>> and login to my app with that email address). But during the app creation >>> process I have to choose between: (a) making it available to all Google >>> Accounts users, (b) making it available to only certain Google Apps >>> Accounts users, or (c) making it available via OpenID. I don't want any of >>> these! Like I said, users with any email address should be able to register >>> with my app and log in to it, without having to use Google accounts or >>> OpenID. Is this possible, and if so how? >>> >>> I have to assume the 3rd question is possible, because there are apps >>> that are fully open to the public and that don't require signing in to (no >>> auth). >>> >>> Thanks in advance! >>> >>> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/hCFbGhZsKTgJ. 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.
