[DOCS-13815] Realm+Google auth Created: 08/Aug/20  Updated: 27/Oct/23  Resolved: 08/Sep/21

Status: Closed
Project: Documentation
Component/s: Realm
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Minor - P4
Reporter: Alexander Komyagin Assignee: Unassigned
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 2 years, 22 weeks ago

 Description   

Description

We used to have pretty nice docs around implementing Google Auth with Stitch, which is a killer feature (e.g. https://docs.mongodb.com/guides/stitch/react_googleauth/), but after we changed to Realm, those things are nowhere to be found

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Dachary Carey [ 08/Sep/21 ]

Just ran across this old issue. Realm docs do have a Google Authentication guide, with links to code examples for each SDK, so I assume this was added at some point after this ticket was filed. Closing this ticket as the work is done.

Comment by Alexander Komyagin [ 10/Aug/20 ]

Ok, I see, thanks Nicholas! I didn't realize that I was looking at the wrong SDK. Do you still have the code you used for the testing by any chance?

I think it will be helpful if we had a diagram explaining how the whole App<->Realm server<->Google interaction works for OAuth, as it might be a bit confusing

Comment by Nicholas Larew [ 10/Aug/20 ]

alex.komyagin Thanks for opening a ticket! We retired the Stitch version of the guide and created a simpler version for Realm based on anonymous authentication, with the goal of really focusing in on how to set up a react app with the Realm SDK.

The Google OAuth page you linked should have all the info you need for configuring Google authentication. The backend configuration steps are essentially identical to what they were in Stitch, so those docs should be correct. What do you mean by the application url here? The page lists https://realm.mongodb.com as the Authorized JavaScript Origins URL which worked in my testing a while back.

The SDK flow for Google OAuth did change slightly in the new Realm SDKs. The page you linked to in your comment is specific to the Node SDK (which is also used for React Native apps). The equivalent page for the Web SDK includes a breakdown of what's necessary for web applications.

Comment by Alexander Komyagin [ 08/Aug/20 ]

Actually, I found a page in the quick start https://docs.mongodb.com/realm/node/authenticate/#google-oauth that suggests a different flow than Stitch. Does this mean we changed things? If that's the case, I think docs should explicitly call this out to avoid confusing users. Plus, we'd need to change the Google OAuth configuration page to mention that the "Authorized JavaScript Origins" in the google project should have the application url.

Generated at Thu Feb 08 08:08:47 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.