Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 31 Next »

In addition to this manual: https://docs.checkmk.com/latest/en/wato_user.html#_automatic_login_via_the_url, we will show you when to use which URL for automatic login via URL

LAST TESTED ON CHECKMK 2.1.0P1

Table of Contents

Access Checkmk view within an Iframe

If your site Apache is secured by cookie-based authentication

OMD[mysite]:~$ omd config show MULTISITE_COOKIE_AUTH
on


The URL for auto login needs to be set like this:

http://localhost/mysite/check_mk/login.py?_origtarget=/mysite/check_mk/view.py?view_name=allhosts&_username=cmkadmin&_password=cmk&_login=1

 

If your site Apache is secured by basic auth, the URL for auto login needs to be set like this:

http://cmkadmin:cmk@localhost/mysite/check_mk/view.py?view_name=allhosts


The same procedure for Nagios views presenting in an Iframe!

Debug HTTPS iframes

Problem

Since Werk #6774, it's not possible to use an HTTPS Iframe within Checkmk (this also affects nagvis). 

If you're considering doing this, please remember that this is a security issue and not supported by us. 

Determine the issue

You get the following broken page when opening an HTTPS Iframe within Checkmk.

Screenshot of broken page within an iFrame


For a more verbose error message, open the developer tools of the current browser, select the Header Console, and refresh the page. This is usually done with the F12 key:

Screenshot of broken page within an iFrame. Web inspector enabled with a section of the error message highlighted.


The browser also produces an error about the missing Content-Secuirty-Policy (CSP). Please keep in mind that many Software/Pages do not want to be integrated as an Iframe due to security settings.


  • No labels