XYMON-WEBACCESS(5)
π XYMON-WEBACCESS(5) π
okay bestie, so this is xymon-webaccess β it's the whole ~web-based access controls in Xymon~ situation, and it lives in the File Formats Manual section. let's get into it π«Ά
β¨ NAME β¨
xymon-webaccess β web-based access controls in Xymon πΈ
π DESCRIPTION π
okay so first thing's first, and this is kind of a big deal: Xymon does not ship with any built-in authentication (login) mechanism. none. zero. it's giving "figure it out yourself" energy π. Instead, it fully relies on the access controls that already exist in your web server β like, for example, the Apache mod_auth modules. outsourcing the vibes, love that for us π
So that gives you a pretty simple way to control access to the physical directories that make up the pages and subpages containing the hosts defined in your hosts.cfg(5) setup. you can use the Apache require setting to allow or deny access to information on any page β usually by using a Require group ... setting. and then that group name refers to one or more groups inside an Apache AuthGroupFile file. cute, right? β¨
but here's the tea π΅ β this does not work for the Xymon CGI programs. why? because they're used to fetch information about all the hosts in Xymon, and there's only a single directory holding all of the CGI's. so here the most you can do is require that the user is logged in (that's the Apache Require valid-user directive). and likeβ¦ a user with a login can, if he knows the hostname, manipulate the request sent to the webserver and fetch information about any status by using the Xymon CGI programs β even though he cannot see the overview webpages. yeah. yikes. π
To alleviate this whole situation, these Xymon CGI's support a --access=FILENAME option, where FILENAME is an Apache compatible group-definitions file:
svcstatus.cgi(1)acknowledge.cgi(1)enadis.cgi(1)appfeed.cgi(1)
When it's invoked with this option, the CGI will read that Apache group-definitions file, and assume that an Apache group maps to a Xymon page, and then β based on the logged-in userid β determine which pages and hosts the user is allowed access to. Only information about those hosts will be made available by the CGI tool. slay π₯ access control but make it β¨personalizedβ¨
Members of the group root have access to all hosts. main character energy, honestly π
And access will also be granted if the user is a member of a group with the same name as the host being requested, or with the same name as the statuscolumn being requested. periodt π
π SEE ALSO π
The Apache "Authentication, Authorization and Access Control" documentation, http://httpd.apache.org/docs/2.2/howto/auth.html π¦
and that's the whole page bestie!! this was Xymon, Version 4.3.30, dated 4 Sep 2019, and that's XYMON-WEBACCESS(5) β go forth and lock down your access controls, ily, bye!! πβ¨π
π¦ where this page comes from
- debian bookworm: xymon 4.3.30-1+b2 Β· GPL-2.0-only WITH OpenSSL exception
- debian trixie: xymon 4.3.30-4 Β· GPL-2.0-only WITH OpenSSL exception
- ubuntu jammy: xymon 4.3.30-1build2 Β· GPL-2.0-only WITH OpenSSL exception
- ubuntu jammy: xymon 4.3.30-1ubuntu0.1 Β· GPL-2.0-only WITH OpenSSL exception
- ubuntu noble: xymon 4.3.30-2build3 Β· GPL-2.0-only WITH OpenSSL exception
- ubuntu noble: xymon 4.3.30-2ubuntu0.1 Β· GPL-2.0-only WITH OpenSSL exception
- ubuntu questing: xymon 4.3.30-4
- ubuntu resolute: xymon 4.3.30-5 Β· GPL-2.0-only WITH OpenSSL exception
- ubuntu stonking: xymon 4.3.30-6 Β· GPL-2.0-only WITH OpenSSL exception
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms