Red Hat SummitChapter 5. Known Issues
5.1. Known Issues
- (7.1.z) SAML encrypted assertion with newlines fails during parsing
- No proper way to set JDBC_PING
- Client’s logout handling gets stuck between HTTP-POST and HTTP-Redirect
- (7.1.z) SAML logouts are not invalidating the sessions for all logged-in applications
- SAML isPassive not working with 7.0 adapter
- Fuse adapter: Login to Hawt.io with user without admin role
- "Add user federation provider" form doesn’t validate "Custom User LDAP Filter" field
- Disabling Authorization for a client deletes all authorization data
- searchForUserByUserAttribute does not filter users by realm
- Deleting a client with existing sessions/offline_tokens leads to Internal Server Errors
- MAX_LIFESPAN cache policy does not evict objects
- NPE when requesting .well-known URI for which no provider exists
- Unexpected error when creating client with existing client ID
- Kerberos flow is executed even when no Kerberos provider is present
- keycloak-nodejs-auth-utils chokes on TLS errors instead of catching them
- NPE fix for HttpMethod
- Wrong message when a temporarily disabled user requests password reset
- TypeError: this.reject is not a function
- Import of huge certificates fails
- Periodic sync of User Storage Provider SPI does not work
- Access token appears to be valid even though session has expired in the background
- Error when session expired and ajax request execute in Keycloak
- SAML IdP only imports one key from metadata
- Export/Import clients functionality not working as expected
- Unhandled ReadOnlyException in Account Management when updating user from read-only store
- Cannot import realm, which contains user-based authorization policy
- UserRemovedEvent not triggered when userStorage provider is removed
- Removing userSessions is very slow when removing many sessions
- SAML federation link fails to work with read-only LDAP user
