e.
Either we need to adapt the apache configuration not to pass the user at
this point or we would probably adapt the code to remove the auth info
if response 200 is encountered.
Any ideas?
Best regards, Jakob Curdes
Am 07.12.2016 um 19:57 schrieb Jakob Curdes:
Hello Sven, than
a
second time with a different URL.
JC
On 06/12/16 17:40, Jakob Curdes wrote:
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 th
ication
So next time someone asks he has the chance to find something :-)
Cheers,
Sven
On 06/12/16 17:40, Jakob Curdes wrote:
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 informa
ver there we seem to
get stuck in the rewrite rules used for the cookie based auth. It seems
that even if the user is passed the rewrite rule changes the status.cgi
to the login page.
Has anybody gotten a working solution for such a setup? Are we doing
something wrong?
