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

Allow for updating the Graph API access token via the OAuth web flow #6

Open
kern opened this issue Mar 10, 2015 · 4 comments
Open

Comments

@kern
Copy link
Owner

kern commented Mar 10, 2015

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. :)

@rubinovitz
Copy link
Contributor

Does persisting in Firebase make sense?

@kern
Copy link
Owner Author

kern commented Aug 6, 2015

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).

@rubinovitz
Copy link
Contributor

Redis?

@kern
Copy link
Owner Author

kern commented Aug 9, 2015

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
Projects
None yet
Development

No branches or pull requests

2 participants