chore: added xoauth2 support, as needed by Microsoft and Google servers #23
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
NACK. Sorry. |
|
Well at least your response was quick, thanks : ). Any more details, or you simply don't want to support anything that is strictly non RFC? edit: NVM #19 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
One of our older services retrieves email from IMAP and doesn't support OAUTH2, so I used the libraries to create a proxy which does the auth part on behalf of the client. However, it seems that Google and Microsoft don't support OAUTHBEARER, but implement a slightly different standard XOAUTH2 (I couldn't find an RFC for this), but their docs are similar:
MS
Google
xoauth2is basically a copy ofoauthbearerbut the fields updated:From
To