Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. For the customers

    1. Go to Setup → Users → Customers and select the color palette for every customer you want to modify.




      .

    2. Now you can upload a picture. The needed size of that picture is described in the inline help.


      .

    3. Your customer will see that icon on the login screen and after the login.


      .

  2. For the provider

    1. For the provider, there is no GUI way to do that. So we will need to work on the command line. Inside the checkmk instance, we store the icons in:

      Code Block
      languagebash
      themeRDark
      OMD[mysite]:~$ ls share/check_mk/web/htdocs/themes/

      So there is a way to create a local branch and add your custom icon. To achieve that successfully, you must use the same icon names stored in share/check_mk/web/htdocs/themes/. The name of that icon for the log in is mk-logo.png

    2. The easiest way to move the icons to the provider is to copy the paths. Checkmk has two directories for the dark and light themes. In that example, I'm using root to copy both directories. After that, I we must change the permissions to the Checkmk instance name.

      Code Block
      languagebash
      themeRDark
      cp -r /omd/sites/mysite/local/share/check_mk/web/htdocs/themes/* /omd/sites/mysite/local/share/check_mk/web/htdocs/themes/
      chown -R cme2.mysite:mysite /omd/sites/mysite/local/share/check_mk/web/htdocs/themes/*


    3. Now you changed the login icon of the provider site successfully:


...

In the global setting (regardless of whether it's a CME or CEE), you will find an option to customize the login screen:.

Setup → General → Global setting → search for "login"


  • Here you can hide the Checkmk version, add a custom link, and put a custom login message.

Image Modified


  • After saving that, the login screen will look

...

  • similar to below.


Note

If you're running Checkmk in a distributed setup, you may want to do that in the site-specific global settings than globally!

...