Implement the server-side OAuth 2.0 flow #13
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Google’s sign-in JS is convenient, but it requires end users to allow third-party cookies. Some people have third-party cookies disabled by IT mandate, and more use tracker-blocking browser extensions. Our support team at Basecamp deals with issues like these frequently.
This PR replaces the
google_sign_in
helper withgoogle_sign_in_button
:The resulting button initiates the OAuth 2.0 authorization code flow on the server. We redirect to Google for authorization and await a callback request with an authorization code. Upon receiving the authorization code, we exchange it for an ID token, store the ID token in
flash[:google_sign_in_token]
, and redirect to theproceed_to
URL. To mitigate open redirects,proceed_to
is required to reside on the same origin as the Rails app.Before, apps needed only to configure
GoogleSignIn::Identity.client_id
. Now, they’ll setconfig.google_sign_in.client_id
andconfig.google_sign_in.client_secret
instead:To-do: