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

Contribute to cyrusimap/cyrus-sasl #5

Closed
stbischof opened this issue Jun 4, 2020 · 1 comment
Closed

Contribute to cyrusimap/cyrus-sasl #5

stbischof opened this issue Jun 4, 2020 · 1 comment

Comments

@stbischof
Copy link

stbischof commented Jun 4, 2020

Hi @moriyoshi,

would you may add an PR of your cyrus-sasl-xoauth2-plugin to
https://github.com/cyrusimap/cyrus-sasl

ref: cyrusimap/cyrus-sasl#522

@moriyoshi
Copy link
Owner

moriyoshi commented Jun 5, 2020

Thanks for the heads-up. There are several points worth a note:

  1. The issue OAUTHBEARER SASL mechanism support cyrusimap/cyrus-sasl#522 refers to RFC 7628, which describes a mechanism similar to XOAUTH2, but those are different in how to build the payload sent to the server. OAUTHBEARER uses base64-encoded HTTP-esque key-value pairs while XOAUTH2 uses plain base64-encoded KV.
  2. Addition of XOAUTH2 to cyrus-sasl was discussed before on the list.
    https://lists.andrew.cmu.edu/pipermail/cyrus-sasl/2018-May/003132.html
    The key point is the client plugin needs some external mechanism that initiates initial token retrieval and subsequent token refreshment and it isn't standardized at the moment.

FYI: #4 implements a conversation protocol with the external credential provider. For now it isn't my intention to make it official.

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

2 participants