Clarify how PasswordProvider in security-jpa has to be used #35682
Conversation
This file contains 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
FroMage
reviewed
Sep 1, 2023
This comment has been minimized.
This comment has been minimized.
sberyozkin
force-pushed
the
security_jpa_password_provider
branch
from
2cd14e2
to
104a4c6
Compare
quarkus-bot
bot
added
area/docstyle
Sure, have a look please how it looks now |
|
🙈 The PR is closed and the preview is expired. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #35671.
Steph, I did not add any description of supported algorithms - my understanding it is an open ended list because
PasswordprovidesAlgorithmParameterSpecso even custom hashing algorithms, as long as the corresponding providers are registered with Java Security, will be supported