We use cookies to ensure that we give you the best experience on our website.  Visit our Privacy Policy to learn more. If you continue to use this site, we will assume that you are okay with it.

Your choices regarding cookies on this site.
Your preferences have been updated.
In order for the changes to take effect completely please clear your browser cookies and cache. Then reload the page.

Checkmk Conference #6 goes digital. Get your tickets here!

Werk #7819: Fix 'HTTP header authentication'

TitleFix "HTTP header authentication"
Date2019-06-19 07:43:43
Checkmk EditionCheckmk Raw Edition (CRE)
Checkmk Version1.6.0b3,1.7.0i1
LevelTrivial Change
ClassBug Fix
CompatibilityIncompatible - Manual interaction might be required

The HTTP header authentication can be enabled in the Global Settings using the option "Authenticate users by incoming HTTP requests". In case you do not use this authentication method, you are not affected by this issue.

It is mostly used in some reverse proxy setups where the Checkmk apache is located behind an authentication service. The authentication service only tells Checkmk the authenticated username and the user interfaces allows the user to enter without further authentication.

The user name is handed over as HTTP header with each HTTP request to the site apache and forwarded to the GUI.

With Checkmk 1.5 or older in connection with apache 2.4 and Checkmk 1.6 with all apache versions this feature can not be used anymore using HTTP header variables containing other characters than A-z, a-z, 0-9 and -. For example X-Remote-User is still working, while REMOTE_USER (which uses the not allowed _) is not working anymore.

This 1.6.0b3 release fixes an issue in this header variable processing and changes the default setting in the GUI to X-Remote-User.

If you configured this before with 1.5, you will have to check your configuration and change the HTTP header variable in the reverse proxy and Checkmk configuration to make it work with the new variable syntax.