-
-
Notifications
You must be signed in to change notification settings - Fork 328
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
OAuth 2 support #225
OAuth 2 support #225
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few small notes after reading through. I'll be able to actually run / test later today or tomorrow, and give my final review then.
Thanks. So how can I test and verify this? Do you have sample config values if I'm running Write.as locally? |
I sent my local setup to you privately. |
This checks to see if we get a response with a populated `error` field in exchangeOauthCode(). If so, we return that error message as an error, to ensure the callback logic doesn't continue with a bad response. Ref T705
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After testing, everything looks good! I committed a few changes I needed: added some helpful logging and fixed some error-passing during the code exchange process.
Last thing: we should update the database table names to be consistent with the current naming scheme. Then we'll get this merged!
Perfect -- thanks @ngerakines! Merging now. |
This PR introduces OAuth 2.0 support as a client application integrating against a OAuth provider.
Change Log
Added
Changed