Univention Bugzilla – Bug 40000
SAML configuration collides with Nagios
Last modified: 2020-05-04 07:40:47 CEST
The nagios configuration currently collides with SAML configuration, if the SAML IdP is configured to be the DC master: /var/log/apache2/error.log [...] [2015-11-16 16:26:00]: uid: (114/samlcgi) gid: (121/samlcgi) cmd: php-cgi [2015-11-16 16:32:13]: uid: (114/samlcgi) gid: (121/samlcgi) cmd: tac.cgi [2015-11-16 16:32:13]: command not in docroot (/usr/lib/cgi-bin/nagios3/tac.cgi) /var/log/apache2/suexec.log [...] [2015-11-16 16:32:13]: uid: (114/samlcgi) gid: (121/samlcgi) cmd: tac.cgi [2015-11-16 16:32:13]: command not in docroot (/usr/lib/cgi-bin/nagios3/tac.cgi) This is currently a problem on demo.univention.de (cf. Bug 39738)
See also: http://forum.univention.de/viewtopic.php?f=48&t=4897
*** Bug 41606 has been marked as a duplicate of this bug. ***
Workaround: Install Nagios on a DC Slave.
As far as I can see, the workaround does not work, as univention-saml is also installed on every DC-Salve. The only workaround, I know is to: ucr ucs/server/sso/virtualhost=true
(In reply to Sven Anders from comment #4) > As far as I can see, the workaround does not work, as univention-saml is > also installed on every DC-Salve. The only workaround, I know is to: > > ucr ucs/server/sso/virtualhost=true univention-saml should never be installed on a DC Slave.
Maybe we should fill an upstream bug report that suexec can be limited to virtual hosts only. Otherwise there is no way to fix this bug. Except if nagios could be moved into a docker container.
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018. Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact your partner or Univention for any questions. If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.