Uploaded image for project: 'Red Hat build of Keycloak'
  1. Red Hat build of Keycloak
  2. RHBK-3217

Unable to configure TLS reloading in Keycloak version 26.2.0 or later [GHI#40713]

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False

      Before reporting an issue

      [x] I have read and understood the above terms for submitting issues, and I understand that my issue may be closed without action if I do not follow them.

      Area

      account/api

      Describe the bug

      We have upgraded keycloak from 26.1.4 to 26.2.5 and we started facing following error on startup.

      ERROR [org.keycloak.quarkus.runtime.cli.ExecutionExceptionHandler] (main) ERROR: java.lang.IllegalArgumentException: Unable to configure TLS reloading - The reload period cannot be less than 30 seconds

      This error occurs because of following parameter with value -1. It is working fine with other values greater than 30 like 30s, 60m, etc
      KC_HTTPS_CERTIFICATES_RELOAD_PERIOD=-1

      For our need, we want to keep it -1 and keycloak documentation also allows -1, which means reloading is disabled. But still it is failing for value less than 30 seconds.

      It was working fine with same value for this parameter in 26.1.4.

      Is there any change from 26.2.0 or it is a bug?

      Version

      26.2.0 or later

      Regression

      [ ] The issue is a regression

      Expected behavior

      There should be no error on startup and container should run fine.

      Actual behavior

      We are getting exception: ERROR: java.lang.IllegalArgumentException: Unable to configure TLS reloading - The reload period cannot be less than 30 seconds

      How to Reproduce?

      Start keycloak on version 26.2.0 or later with following parameter:

      KC_HTTPS_CERTIFICATES_RELOAD_PERIOD=-1

      Anything else?

      No response

              Unassigned Unassigned
              pvlha Pavel Vlha
              Keycloak Cloud Native
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: