Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use refresh token instead of requiring user re-authenticate with Google #4

Open
ryanfb opened this issue Feb 1, 2017 · 2 comments
Open

Use refresh token instead of requiring user re-authenticate with Google #4

ryanfb opened this issue Feb 1, 2017 · 2 comments
Assignees
@ryanfb

Comments

@ryanfb
Copy link
Owner

ryanfb commented Feb 1, 2017

No description provided.

@ryanfb ryanfb self-assigned this Feb 1, 2017
@ryanfb ryanfb mentioned this issue Feb 3, 2017
Open
@ryanfb
Copy link
Owner Author

ryanfb commented Feb 3, 2017

See: http://stackoverflow.com/questions/10827920/not-receiving-google-oauth-refresh-token

@ryanfb
Copy link
Owner Author

ryanfb commented Feb 6, 2017

It looks like they really don't want you to use refresh tokens or offline access with Javascript. Maybe what we should do instead is validate the access_token on submit, and then (if it's expired), save, redirect through Google Auth with immediate: true (should be non-prompting since they've already auth'd once), then when we come back, load the form and submit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ryanfb ryanfb

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ryanfb