Bug#831532: [Pkg-nagios-devel] Bug#831532: Bug#831532: icingaweb2: handle auth DB with dbconfig-common
On Mon, 2016-07-18 at 07:43 +0200, Alexander Wirt wrote: > Thats the case with web2. Run the wizard, give it an empty database > and it > will fill the tables. Ah? Okay I didn't know that… the documentation seemed to have mentioned that one needs import: /usr/share/icingaweb2/etc/schema/mysql.schema.sql /usr/share/icingaweb2/etc/schema/pgsql.schema.sql and I thought then that of course further steps could be needed when schemas change on upgrade. Anyway, if you think it's better not to manage this with dbconfig, then you can also just close the issue. Cheers, Chris. smime.p7s Description: S/MIME cryptographic signature
Bug#831532: [Pkg-nagios-devel] Bug#831532: Bug#831532: icingaweb2: handle auth DB with dbconfig-common
On Sun, 17 Jul 2016, Christoph Anton Mitterer wrote: > Hey Alex. > > On Sun, 2016-07-17 at 08:28 +0200, Alexander Wirt wrote: > > given our experience with dbconfig in icinga2, this won't happen. > > Oh I wasn't aware that there were bigger troubles (other than those > I've reported recently,... i.e. that it doesn't work flawlessly when > only using UNIX sockets... but apart from that it seemed to work nicely > for me). > > Well it was just an idea,... :) > > Ideally all those projects would just require people to set up a plain > empty DB and user... and fill those on their own when started first > time. Thats the case with web2. Run the wizard, give it an empty database and it will fill the tables. Alex
Bug#831532: [Pkg-nagios-devel] Bug#831532: icingaweb2: handle auth DB with dbconfig-common
Hey Alex. On Sun, 2016-07-17 at 08:28 +0200, Alexander Wirt wrote: > given our experience with dbconfig in icinga2, this won't happen. Oh I wasn't aware that there were bigger troubles (other than those I've reported recently,... i.e. that it doesn't work flawlessly when only using UNIX sockets... but apart from that it seemed to work nicely for me). Well it was just an idea,... :) Ideally all those projects would just require people to set up a plain empty DB and user... and fill those on their own when started first time. Best wishes, Chris. smime.p7s Description: S/MIME cryptographic signature
Bug#831532: [Pkg-nagios-devel] Bug#831532: icingaweb2: handle auth DB with dbconfig-common
tag 831532 wontfix thanks On Sun, 17 Jul 2016, Christoph Anton Mitterer wrote: > 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. given our experience with dbconfig in icinga2, this won't happen. Alex
Bug#831532: icingaweb2: handle auth DB with dbconfig-common
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.
