> Am 12.02.2016 um 19:18 schrieb Markus Joosten <[email protected]>: > > Hello, > > currently i'm using Icingaweb 2 + PNP + NagVis with Apache being the > authentication provider for all 3 tools (using basic auth with files and ldap > backend). > This works fine, both NagVis and PNP don't have to worry about authenticating > the users, since authenticated users are indicated within the HTTP headers. > > Now i would like to move away from Apache handling all authentication data > and would like to use PostgreSQL as a user backend within Icingaweb 2. > This all works fine with Icingaweb 2 alone, but of course breaks my current > implementation of PNP and NagVis, they don't know about Icingaweb's DB > authentication. >
The Nagvis web2 module has a way to implement this (check the readme). PNP would need a patch to integrate well though I haven't heard anything on those plans from neither Tom and Jörg. Regards, Michael > Does anyone know about a way how to indicate the current (Icingaweb 2) user > via HTTP header to these seperate tools? > > (I know, this would be some seriously sketchy integration, but still would > help a lot at the time being.) > > Regards, > Markus > _______________________________________________ > icinga-users mailing list > [email protected] > https://lists.icinga.org/mailman/listinfo/icinga-users -- Michael Friedrich, DI (FH) Senior Developer NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg Tel: +49 911 92885-0 | Fax: +49 911 92885-77 CEO: Julian Hein, Bernd Erk | AG Nuernberg HRB18461 http://www.netways.de | [email protected] ** OSDC 2016 - April - netways.de/osdc ** ** OSBConf 2016 - September - osbconf.org ** _______________________________________________ icinga-users mailing list [email protected] https://lists.icinga.org/mailman/listinfo/icinga-users
