8000 Clarify FIPS instructions by andymunro · Pull Request #40534 · keycloak/keycloak · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Clarify FIPS instructions #40534

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

Merged
merged 2 commits into from
Jun 17, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion docs/guides/server/fips.adoc
< 6194 /tr>
Original file line number Diff line number Diff line change
Expand Up @@ -118,7 +118,14 @@ Using that option results in stricter security requirements on cryptography and
NOTE: In strict mode, the default keystore type (as well as default truststore type) is BCFKS. If you want to use a different keystore type
it is required to use the option `--https-key-store-type` with appropriate type. A similar command might be needed for the truststore as well if you want to use it.

When starting the server, you can check that the startup log contains `KC` provider with the note about `Approved Mode` such as the following:
When starting the server, you can include TRACE level in the startup command. For example:

[source,bash,subs=+attributes]
----
--log-level=INFO,org.keycloak.common.crypto.CryptoIntegration:TRACE
----

By using TRACE level, you can check that the startup log contains `KC` provider with the note about `Approved Mode` such as the following:

[source]
----
Expand Down
0