-
Notifications
You must be signed in to change notification settings - Fork 28
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
Allow for updating the Graph API access token via the OAuth web flow #6
Labels
Comments
Does persisting in Firebase make sense? |
I think so. You can't access the Firebase instance without a admin secret, which basically makes it a hosted database. Or, we can move off Firebase to another data store (perhaps an embedded one? The data we persist is tiny). |
Redis? |
Works for me. I'll get to it this week. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hackbot needs the ability to create and delete posts on the behalf of at least one group administrator. Users that wish to use the upcoming canned-response commands (#10, #11, #12) will also have to authenticate with the application.
We'll need to implement the OAuth 2 web flow and persist the long-lived access tokens somewhere. The hacky method described in the README isn't so user-friendly. :)
The text was updated successfully, but these errors were encountered: