The apache 2.4 problem was the conf file for Icinga Web 2. In Apache 2.4 instead of ....
Order Alow,Deny Allow all its now.... Require all granted ________________________________________ From: icinga-users [icinga-users-boun...@lists.icinga.org] on behalf of Michael Friedrich [michael.friedr...@gmail.com] Sent: Tuesday, March 18, 2014 10:27 AM To: Icinga User's Corner Cc: icinga-de...@lists.icinga.org Subject: Re: [icinga-users] Icinga Web 2 authentication On 18.03.2014 14:18, Sherman Lilly wrote: > Thank you for your response. I will give further information and continue > testing and resolving some of the problems. I should have made notes on the > installation. Shell history also helps. > > The hardest part that took me a while was the new stable release of Apache > 2.4 on Red Hat Fedora which changed the configuration files around and the > format of the conf files. This is not a Icinga problem but maybe a heads up > for what Apache 2.4 is bringing to the table. I wasn't aware that Apache 2.4 is in any stable release yet, but if Fedora got it, well. Even though, Apache 2.4 runs fine in my Debian Testing environment, with Icinga Web 2 dev environment. Maybe some details on the error will help shed some light into the issue. Be verbose. > > Another thing is I noticed Icinga changed the PHP Framework to Zend. This is > a good thing becuae the previous framework was confusing to me but that is > just me. Zend is a well founded PHP Framework that just works and is well > known. Well. That's a political and religious mine field. Agavi and ExtJS (Sencha) for Icinga Web 1.x do a good job, but are hard to extend and debug for the normal user. Experienced developers may catch up with that, but not the ordingary guy hunting some disfunctionality. In the end, the wiki holds some guides on debug the stuff - when PHP exceptions are served via Ajax Request Handlers, you'll never know to either eat the keyboard, or jump out of the window. Icinga Web 2 drives the way to make the usability and extendability more easy, and removing the requirements to a query low level. Javascript goes the JQuery way whilst using own stuff. Even further, the code documentation should be good enough - and, for what it's worth, the capability of adding own modules. Tom did show me some prototypes lately which get the "give-it-now" sticker, but are to be finished soon enough. For details, the web developers are best to address. I've heard they got so much stuff to do that they do not read much on the mailinglists but rather commit stuff ;-) https://dev.icinga.org/projects/icingaweb2/roadmap (well, I do have as much as they do, with Icinga 2 Core) > > Should I move this topic to the dev mailing list? No. If anyone is not interested in this topic, he/she may either tell about it, or delete the mail. best regards, Michael > > Sherman Lilly > (865) 215-3536 > Senior Systems Administrator > Knox County > > ________________________________________ > From: icinga-users [icinga-users-boun...@lists.icinga.org] on behalf of > Michael Friedrich [michael.friedr...@gmail.com] > Sent: Tuesday, March 18, 2014 5:54 AM > To: icinga-users@lists.icinga.org > Cc: icinga-de...@lists.icinga.org > Subject: Re: [icinga-users] Icinga Web 2 authentication > > On 17.03.2014 14:47, Sherman Lilly wrote: >> This may be a developer question but I will start here and see what happens. > > Thanks for testing the early in-development version of Icinga Web 2. > Please keep in mind, that there is no public release nor any alpha/Beta > version yet. > > So if something breaks, or remains broken, it means no harm, and we > should work together in fixing this - best by creating a new issue at > dev.icinga.org > >> >> I have installed Icinga Web 2 and it wasn't easy. > > Care to elaborate how? > >> I am a seasoned PHP programmer and system administrator and installation >> needs more work. > > There are some issues still open for a) making the install method more > comfortable b) create a web installer and finally c) create packages. > > I am currently working on the c) part for RPMs. > > https://dev.icinga.org/issues/5638 > https://dev.icinga.org/issues/3761 > https://dev.icinga.org/issues/4075 > >> I would be willing to help but for now I need a working installation. > > In any case, when asking here or creating an issue, please provide the > following information to make the developers and users life easier > > - distribution and version > - webserver+version, php version > - additional webserver configuration > - how did you install icingaweb2? (if source, full cmd line. if > packages, which repo) > - until there is a public release, please extract git HEAD sha1 commit > (git log -1) > - icingaweb2 configuration changes, if any > - icingaweb2 logs/debuglogs containing insights > - webbrowser dev console with additional errors? > > >> I have running on my server and the login page comes up. Authenication is >> the problem. When I try to log in it gives the error that no authentication >> method works. > > Anything on the browser dev console? What is the exact error message? > Anything on the logs? (I could point you to the path if I would know how > you did attempt to install it) > >> I see the configuration for LDAP but no information on MySQL configuration. > > Where? How does it look like? > >> I have reviewed the source code and figured out some of the table layouts >> but I still don't have it quite right. Is there some sql file I am missing? > > How did you setup the icingaweb database, and apply the required schemas? > >> >> The reasoning for not using LDAP is the extra overhead. > > That's totally fine. The reason why LDAP has been chosen as primary auth > method is simple: The developers are using a Vagrant Box for their > development stages (everyone uses the same platform, etc). Within that > box, openldap is running serving a base schema allowing further > development on that feature requirement. > > But indeed you are correct that the other authentication methods require > to be tested and implemented as well. > > I recently ran into the problem that the db auth was broken too and > created an issue which had been fixed before cebit. Maybe there's a > regression that fix in the current git master. > > https://dev.icinga.org/issues/5706 > > So in order to fix that issue (and not do any nitpicking on db auth vs > ldap auth!) I'd love to see all the required information outlined above. > > Feel free to open an issue on dev.icinga.org in the Icinga Web 2 section > directly and let developers know. > > best regards, > Michael > > > -- > DI (FH) Michael Friedrich > > michael.friedr...@gmail.com || icinga open source monitoring > https://twitter.com/dnsmichi || lead core developer > dnsmi...@jabber.ccc.de || https://www.icinga.org/team > irc.freenode.net/icinga || dnsmichi > _______________________________________________ > icinga-users mailing list > icinga-users@lists.icinga.org > https://lists.icinga.org/mailman/listinfo/icinga-users > > _______________________________________________ > icinga-users mailing list > icinga-users@lists.icinga.org > https://lists.icinga.org/mailman/listinfo/icinga-users > -- DI (FH) Michael Friedrich michael.friedr...@gmail.com || icinga open source monitoring https://twitter.com/dnsmichi || lead core developer dnsmi...@jabber.ccc.de || https://www.icinga.org/team irc.freenode.net/icinga || dnsmichi _______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users _______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
