So... my application is deployed, happy, and now populated with a fair
amount of data. But now we have acquired a new, sexier domain name
and need to migrate the app to the new domain name.
There seems to be one catch: I created the application to
authenticate against the Google Applications domain. It was literally
a coin-toss; our app authenticates against Facebook so I didn't think
the answer was relevant. But now it seems that you cannot add a
second domain to an application if it was configured this way.
First question: Is it really true that I can't add a second domain to
an application that was configured to auth against google apps? There
was no warning that this would be the case when I set it up to auth
this way; it's only something I have inferred from several vaguely
related discussion group threads and the fact that I keep getting
errors ("You do not have permission...") when I try.
Second question: If this really is a restriction, is there *any* way
of converting the application over to auth against google accounts? I
have a live running system in continual use, and while traffic is
still relatively modest, it would be a major effort to synchronize the
objects from one app to another during the transition. I'm in
Java-land, so I don't have easy access to bulk export/import.
I hate to sound like a whiner, but this issue (not being able to
migrate to a new domain name) is a really HUGE gotcha that really
should be mentioned in the warning text when you create an app. I
still hope I'm just misunderstanding the system and there is an easy
solution :-(
Thanks in advance for any help or advice,
Jeff
--
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.
