Hello all, hello Sven,
(I am top-posting as the original post is rather old and most info
should be in the new text)
we have finally had time to re-test the combination of
"default_user_name" and a cookie-based auth for issuing commands only.
I think we are pretty near the result and it looks
Am 06.12.2016 um 20:00 schrieb Sven Nierlein:
Hi,
i did implement that once in a customer setup but i cannot remember all
details. Basically you need to change the
apache config in a way, that everything except /thruk/cgi-bin/cmd.cgi is
not protected and free to access.
In order to do so you
Hello Sven, thank you, the approach sounds sensible and I will try that
out and document a working setup.
Regards, Jakob
Am 06.12.2016 um 20:00 schrieb Sven Nierlein:
Hi,
i did implement that once in a customer setup but i cannot remember all
details. Basically you need to change the
apache
Hi,
i did implement that once in a customer setup but i cannot remember all
details. Basically you need to change the
apache config in a way, that everything except /thruk/cgi-bin/cmd.cgi is
not protected and free to access.
In order to do so you need to add an exception to the rewrite block whi
Hello, we use an OMD-based system with naemon and thruk for our
monitoring and are trying to implement a two level access model:
- anonymous access to status information (read-only)
- cookie-based access for the rest.
This means that apache and thruk must interact to allow access to
certain U
