vauth/cleartext: Update the PLAIN login function signature to match RFC 4616 - #3757
Closed
captain-caveman2k wants to merge 1 commit into
Closed
vauth/cleartext: Update the PLAIN login function signature to match RFC 4616#3757captain-caveman2k wants to merge 1 commit into
captain-caveman2k wants to merge 1 commit into
Conversation
captain-caveman2k
force-pushed
the
master
branch
from
April 9, 2019 21:52
ae53a8f to
0e6e693
Compare
bagder
requested changes
Apr 10, 2019
…FC 4616 Functionally this doesn't change anything as we still use the username for both the authorisation identity and the authentication identity.
captain-caveman2k
force-pushed
the
master
branch
from
April 10, 2019 21:18
0e6e693 to
d6142b4
Compare
bagder
approved these changes
Apr 11, 2019
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Functionally this doesn't change anything as we still use the username
for both the authorisation identity and the authentication identity.