Removed custom SCRAM implementation in favor of library provided by... #260
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.
…Ongres and used in official JDBC driver. No need to maintain the SCRAM crypto stuff this way and guaranteed we won't have any weird compatibility issues.
BTW, the use of
SecureRandom.getInstanceStrong()
in the original implementation led to some hanging issues on machines without enough entropy. See https://tersesystems.com/blog/2015/12/17/the-right-way-to-use-securerandom/ for details on this, but this led me to investigate what the official JDBC client does for nonce creation. That then led me to this SCRAM library from Ongres which is nicely decoupled from everything JDBC.