No responses means that no one knows, or it's not possible. I'm guessing the latter?
The only way I can figure this to work is for the App owner to (temporarily) create an Apps account for us to use so that we can set up both 'sides' of the configuration. Not very secure. And I hope this isn't one of the new "single-user-only-for-app-engine" Apps accounts. Have I mentioned before that all of this stuff should be possible via API so that the Apps ugliness can be avoided and we can just configure App Engine how we need it? ;) j On Wednesday, 13 February 2013 15:42:57 UTC-6, Jason Collins wrote: > > We allow our customers to map their custom domains to our App Engine > application - meaning they control the Google Apps account, while we > control the App Engine application. > > If they want to add an SSL cert to their custom domain, but they are not > an admin/owner of the App Engine application, how can this be achieved? > > I think that the billing aspect of SSL requires that it is associated to > the App Engine application, and since billing is involved, only an App > Engine application owner can approve it. > > Any thoughts on the least awkward way to achieve this? > > Aside: it would be great if the Google Apps owner incurred the SSL costs > instead of us (the App Engine application owner), but I'm pretty sure this > is not possible. > > Thanks for any advice, > j > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
