parent
593c14cd26
commit
a4b5d66aa0
2 changed files with 2 additions and 2 deletions
|
@ -45,7 +45,7 @@ spec:
|
||||||
|
|
||||||
[NOTE]
|
[NOTE]
|
||||||
====
|
====
|
||||||
With custom images, every build time option passed either through a dedicated field or the `additionalOptions` is ignored.
|
With custom images, every build time option is passed either through a dedicated field or the `additionalOptions` is ignored.
|
||||||
====
|
====
|
||||||
|
|
||||||
</@tmpl.guide>
|
</@tmpl.guide>
|
||||||
|
|
|
@ -264,7 +264,7 @@ earlier. If you prefer to avoid this option, you can for instance ask all your u
|
||||||
|
|
||||||
== Keycloak FIPS mode on the non-fips system
|
== Keycloak FIPS mode on the non-fips system
|
||||||
|
|
||||||
Keycloak is tested on a FIPS enabled RHEL 8 system and `ubi8` image. It is supported with RHEL 9 (and `ubi9` image) as well. Running on
|
Keycloak is supported and tested on a FIPS enabled RHEL 8 system and `ubi8` image. It is supported with RHEL 9 (and `ubi9` image) as well. Running on
|
||||||
the non-RHEL compatible platform or on the non-FIPS enabled platform, the FIPS compliance cannot be strictly guaranteed and cannot be officially supported.
|
the non-RHEL compatible platform or on the non-FIPS enabled platform, the FIPS compliance cannot be strictly guaranteed and cannot be officially supported.
|
||||||
|
|
||||||
If you are still restricted to running Keycloak on such a system, you can at least update your security providers configured in `java.security` file. This update does not amount to FIPS compliance, but
|
If you are still restricted to running Keycloak on such a system, you can at least update your security providers configured in `java.security` file. This update does not amount to FIPS compliance, but
|
||||||
|
|
Loading…
Reference in a new issue