What's Changed
- π SASL: Clarify usage of username vs authcid vs authzid by @nevans in #187
- Improved SASL authenticator parameter documentation.
- Aliases have been added from
username
toauthcid
orauthzid
βor in the other direction, fromauthcid
orauthzd
tousername
. OAuthBearerAuthenticator
may now receive two arguments, to match the commonauthenticate(username, secret)
style.authzid
(i.e.username
) is still optional for the mechanism (although in practice many servers do require it).- Instead of raising an exception, conflicting arguments are silently ignored. This allows more specific arguments (like
authcid
or a keyword argument) to override more generic terms (likeusername
or a positional argument). This improves compatibility with other projects, and can also simplify dynamic mechanism negotiation. - Keyword argument support has been added to the deprecated
LOGIN
andCRAM-MD5
mechanisms. This is for consistency and compatibility with other projects. These mechanisms are obsolete and should be avoided.
- β¨ Add
secret
alias (forpassword
,oauth2_token
, etc) to relevant SASL mechanisms by @nevans in #195
Full Changelog: v0.4.1...v0.4.2