Your message dated Tue, 11 Mar 2025 07:21:28 +0100
with message-id <[email protected]>
and subject line icingaweb2: handle auth DB with dbconfig-common
has caused the Debian Bug report #831532,
regarding icingaweb2: handle auth DB with dbconfig-common
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
831532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831532
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: icingaweb2
Severity: wishlist
Hi.
Currently, icingaweb2 doesn't set up/manage the Icinga Web 2 specific DBs
at all, it even doesn't depend on php-mysql|php-pgsql...
This is of course great, as Icinga Web 2 doesn't stricly need and DB for
authentication, but can also use local files, LDAP, etc..
But it also seems, that even when auth/authz is done e.g. via webserver
authentication (HTTP Basic auth) and local INI files, one would need
a DB if one wanted to use groups.
So in the end it would be nice, if icingaweb2 would provide and *optional*
way to manage that DB (and perhaps even initially add an admin user if
the installing user wishes to do so), ideally with dbconfig-common.
My idea would be, that perhaps icingaweb2 Suggests a icingaweb2-db-auth
package (or perhaps using some better name).
This could then depend on dbconfig-common, contain the schema files and
depend on php-psql|php-mysql.
On installation, dbconfig would kick in and allow the user to take over
management and future schema upgrades.
Since icingaweb2-db-auth would be only Suggested, users could still opt-out
of the whole DB-for-Icinga-Web2 thingy.
And of course php-icinga would still continue to Recommend php-mysql|php-pgsql
which are of course e.g. still needed to connect to IDO.
Cheers,
Chris.
--- End Message ---
--- Begin Message ---
No use keeping wontfix issues open.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
--- End Message ---
