Clarify FIPS instructions #40534
Merged
Clarify FIPS instructions #40534
Conversation
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
Closes keycloak#40533 Signed-off-by: AndyMunro <amunro@redhat.com>
ahus1
reviewed
Jun 17, 2025
Signed-off-by: Alexander Schwartz <alexander.schwartz@gmx.net>
|
@rmartinc / @mposolda - while updating the docs is probably correct for KC 26.2 and the current implementation, it would be great to simplify things and not needing that logging configuration in the first place. If we can assume that all people want to check that FIPS is working as expected, could we log this with INFO level by default at startup? |
ahus1
approved these changes
Jun 17, 2025
|
@ahus1 Does this need to be backported to 26.2 to support the next 26.2.x release to downstream? |
Yes |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Closes #40533