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

fix: Use SASLprep normalization for SCRAM authentication #2054

Merged
merged 1 commit into from
Feb 10, 2021

Conversation

jorsol
Copy link
Member

@jorsol jorsol commented Feb 10, 2021

Not sure what is the correct flow to merge to release/42.2 and master branches, so here is the PR that targets master.

Using NO_PREPARATION the handling of spaces was incorrect, the driver should use SASL_PREPARATION.

Signed-off-by: Jorge Solórzano <jorsol@gmail.com>
@davecramer
Copy link
Member

We won't be merging them. This is the right answer.

@jorsol
Copy link
Member Author

jorsol commented Feb 10, 2021

We won't be merging them. This is the right answer.

Fair enough 😅, I probably was not clear... my question would be that if all the release/42.2 changes are cherry-picked and applied to master (like in #1965) and/or changes "could" be applied to release/42.2 and master.

@davecramer
Copy link
Member

cherry picking as necessary

@jorsol jorsol merged commit 61af1be into pgjdbc:master Feb 10, 2021
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

Successfully merging this pull request may close these issues.

None yet

2 participants