Google Consent Page shows mongodb.com
D
Dimitar Kurtev
I followed MongoDb Stitch docs to setup Google OAuth. Everything works fine, except that the user consent screen shows "mongodb.com" instead of my own domain. Google shows the domain from which the request is coming from, not the app name set in the Google console. OK, I figured out that I have to let Google verify my web app to make it show my web apps name and logo. After 5-6 email exchanges I received an email from Google telling me that I have to be the owner of mongodb.com to proceed with my verification. All of the Authorized Javascript Origins and Redirect URLs should be owned by me. So in summary, with current setup it is not possible to show your own web app name because there is no way for me to claim ownership of mongodb.com.
Any ideas on how to solve this?
Drew DiPalma
Hi Folks!
As part of our upcoming re-brand of "Stitch" to "Realm" we'll also be migrating our feedback forum and joining the rest of MongoDB at feedback.mongodb.com – as part of that transition, we'll be shutting down this forum. We're still keeping track of this feedback and all of the related comments/discussions, but have only migrated feedback with 5+ votes at this time. If you would like us to continue to track this item in the new forum please let us know.
Drew DiPalma
Hi Dimitar – After some additional investigation with the engineering team, there doesn't seem to be a way around this at this time. We are looking into an improvement for later in the year that would allow greater flexibility with using Custom Domains + Stitch and will keep this in mind.
D
Dimitar Kurtev
Drew DiPalma: This is unfortunate. More than 50% of users in my beta test used Google login.
I assume, as a workaround, I can implement custom JWT Google authentication.
Nevertheless, thank you and the team for looking into this issue.
Drew DiPalma
Dimitar Kurtev: I don't foresee any issues using custom authentication + Google. We'll keep this issue open and update when there are changes.