Chapter 5. Known Issues
5.1. Known Issues
The following are known issues for this release.
- KEYCLOAK-4976 - AbstractUserAdapterFederatedStorage.setSingleAttribute(,) causing deadlocks on MSSQL
- KEYCLOAK-5411 - MSSQL client creation deadlocks
- KEYCLOAK-6142 - Manual configuration page for the OTP doesn’t reflect HOTP
- KEYCLOAK-6171 and KEYCLOAK-6286 - Node.js and Java adapters for RH-SSO 7.1 don’t remove "session_state" from URL after login to RH-SSO 7.2 The issue should only affect users who were logged in but inactive before an RH-SSO upgrade who then find themselves logged out after the RHSSO upgrade is complete when they attempt to use that same session. The workaround is that the users must log in again.
-
KEYCLOAK-6309 - Eap6 SAML filter fails while downloading keys from Keycloak server when SSL is enabled Two workarounds are available. You may either use bouncy castle version 1.52 instead of 1.56 OR you may start EAP6 with the argument
`-Dcom.sun.net.ssl.enableECC=false. -
KEYCLOAK-6451 - Adapter RPMs have an obsolete dependency, meaning that any customer who previously installed adapters using RPMs that executes
yum updatewill find the package updated. The workaround is to exclude the adapter package from yum update. - When a resource permission is created with no associated policies and you try to update the permission, the Save button is not enabled in the Resource Permission UI when adding new policies to the permission.
- Authorization services client does not support JDK7 At the moment, this means you must use Java 8 if you want to try the new authorization services, which are currently in technology preview.
