Description Be able to run Keycloak without TLS in a production configuration, not only in dev. Discussion No response Motivation If you want to run Keycloak in Kubernetes, it's much easier to terminate TLS on ingress or load balancer, there is no need to run Keycloak with TLS. You don't need to han...

Before reporting an issue I have searched existing issues I have reproduced the issue with the latest release Area admin/api Describe the bug Hi, When I call the user search API (GET /users) with the "search" and "q" parameters simultaneously, the behaviour seems inconsistent. When informing the...

Before reporting an issue I have searched existing issues I have reproduced the issue with the latest release Area admin/ui Describe the bug I'm upgrading keycloak from 16 to 20. I noticed that if I manually selected and saved theme to keycloak in realm setting, it will be saved in table realm....

Before reporting an issue I have searched existing issues I have reproduced the issue with the latest release Area authentication Describe the bug Keycloak couldn't start up when DB is MySQL innoDB cluster. The innoDB cluster has "generate invisible primary key" enabled to ensure all new tables...

Before reporting an issue I have searched existing issues I have reproduced the issue with the latest release Area authentication Describe the bug When a realm has the username=email flag active, and a user has to complete the update-email action, their username is not updated. The user is then...

Some tests are failing in BCFIPS approved mode due the SecretKey used for HmacSHA256 (or others of HmacSHA algorithms) should be at least 112 bits long (14 bytes). This means that for clients using client-secret-jwt authentication, the client secrets must be at least 14 characters long. This is an i...

org.keycloak.testsuite.model.session.OfflineSessionPersistenceTest#testPersistenceMultipleNodesClientSessionsAtRandomNode Keycloak CI - Store Model Tests / Pull Request #16478 java.lang.AssertionError: threads didn't terminate in time: [main (TIMED_WAITING): locked on java.util.concurrent.FutureTas...

org.keycloak.testsuite.ui.account2.DeviceActivityTest#signOutTest Keycloak CI - Account Console IT (firefox) / Pull Request #16478 java.lang.AssertionError: Expected WelcomeScreen but was Keycloak Account Management (https://localhost:8543/auth/realms/test/account/) at org.junit.Assert.fail(Assert....

org.keycloak.testsuite.ui.account2.WelcomeScreenTest#resourcesTest Keycloak CI - Account Console IT (firefox) / Pull Request #16478 java.lang.AssertionError: Element should be visible expected:<true> but was:<false> at org.junit.Assert.fail(Assert.java:89) at org.junit.Assert.failNotEq...