Hi Nick,
It has been a rough week, so my brain isn't functioning well, so likely I'm still not explaining well. GoogleHighSchool.com decides to deploy an attendance app at Attendance.GoogleHighSchool.com They don't use unified logins just TeacherName and a Password. Very Clean, doesn't care about OAuth, logins anything. But to deploy the app GoogleHighSchool.com has to be registered with Google Apps For Domains. Students who used their [email protected] email address to Register for Youtube, Picasa, Google+, Etc. When those Accounts login the next time they get the "You need to Migrate your Personal Account" thing that I got on my adwords 2 weeks ago. The School also now administers their Google Docs, their passwords, and a whole host of other things. The School that has gone out of its way to make sure that it doesn't have access to social media sites of students now could have. And whenever the student forgets their Youtube password, the request no longer goes to Google Support with an automated reset, it goes to the Apps For Domain Administer and they have to reset it. With 8500 email addresses, that could be a lot of support. The obvious solution is to run on AttendanceatGoogleHigh.com instead. But that is kind of counter intuitive. From: [email protected] [mailto:[email protected]] On Behalf Of Nick Johnson Sent: Friday, September 30, 2011 12:02 AM To: [email protected] Subject: Re: [google-appengine] More Apps For Domains "getting in the way" stuff Hi Brandon, On Fri, Sep 30, 2011 at 4:52 PM, Brandon Wirtz <[email protected]> wrote: I may have explained poorly. It isn't that the App needs the logins, it's that all of the personal accounts become Managed accounts, Every one of the users would go through the "Migration" on their Google Voice, Google Plus, Picasa, etc. The worry of the school is that the pic of a 12 year old girl in her underwear posted to picasa goes from being "owned" by the personal account, to being owned by an organizational account. Also every time a user forgets their password, they go from doing support through Google, to support through the administrator. That's a lot of overhead on a bunch of students. This is not a big deal for me, the client isn't going to pay me enough that I care, but I though they raised some good points that I wanted to share. There's no need to migrate any accounts at all. Your app can accept signins from any Google account, not just those on an Apps domain. -Nick Johnson From: [email protected] [mailto:[email protected]] On Behalf Of Nick Johnson Sent: Thursday, September 29, 2011 11:14 PM To: [email protected] Subject: Re: [google-appengine] More Apps For Domains "getting in the way" stuff Hi Brandon, What you describe isn't compatible with the current configuration. Simply set up Google Apps on the domain solely to associate the domain name with the App Engine app, and configure the app to accept logins from any Google Account. There's no need to create accounts for users of the app on the domain. -Nick Johnson On Fri, Sep 30, 2011 at 3:57 PM, Brandon Wirtz <[email protected]> wrote: I ranted once before about the issues Apps For Domains created for my Adwords account with the unified login, but I have a new rant from a potential customer. They currently use exchange mail and Group policy objects. They don't want to be responsible, for these student accounts Documents, Messenger, Google+ etc. They quite specifically want those to be personal accounts, so that they don't have any potential liability for how students use those accounts. In my view this makes for a pretty good case of why not to require GAE to be tied to Apps For Domains. Not just in my app, but in any org that would decide the wanted an app on their domain but the email addresses they provide are not employees, or there are so many of them they wouldn't want to administer them through AFD (which is not designed for administering 100k people. I know BestBuy and some other large Orgs are on GAE, are they using AppsForDomains? Are they running on their primary domain? -- 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] <mailto:google-appengine%[email protected]> . For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- Nick Johnson, Developer Programs Engineer, App Engine -- 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. -- 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] <mailto:google-appengine%[email protected]> . For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- Nick Johnson, Developer Programs Engineer, App Engine -- 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. -- 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.
