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.

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

Do not leak credentials #140

Open
cristianuibar opened this issue Feb 5, 2019 · 0 comments
Open

Do not leak credentials #140

cristianuibar opened this issue Feb 5, 2019 · 0 comments

Comments

@cristianuibar
Copy link
Contributor

Build a redirected flow in 3 steps via toplytics.presslabs.net so that the client id and client secret will not be leaked to the end user when connecting via the public method.

Keep a record of all refresh_tokens on toplytics.presslabs.net so that we can revoke access in case something is off.

The steps are:

  • client site => toplytics.presslabs.net/auth?return_url=...
  • topltyics.presslabs.net => google auth to grant access
  • google auth => return to toplytics.presslabs.net (which stores the user as well that came from google)
  • toplytics.presslabs.net => return to client return_path with the refresh_token
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant