Hi. I tired 0.6 both standalone and with Apache 2.2 via WSGI and the admin account login worked ok for both cases. The only thing I did differently was instead of answering questions one by one I passed them all as parameters in one shot from command line. Also since I'm running on Windows server I can't use WSGI as a daemon. There was one other note I found about authentication problem that you have to put in your httpd.conf if you have login problems and it just won't login ;-)
WSGIPassAuthorization On Other than that 0.6 installed from scratch works fine for me. Cheers, Serge ________________________________ From: Steve Gaul <[email protected]> To: "[email protected]" <[email protected]> Sent: Thursday, August 1, 2013 3:35 PM Subject: bloodhound login with PostgreSQL and apache2 Has anyone seen this yet? If you install bloodhound 0.6.0 per the instructions on the website with PostgreSQL and run it standalone from tracd, $ sudo tracd ./bloodhound/environments/main --port=8000 you can login as the admin account and password that you entered from the questions asked in the bloodhound setup script, create users, etc. life is good :) but it appears that if you follow the same instructions to configure bloodhound for an apache site configuration and run it from apache, all is good, it starts up, you have all of the pages, all of the links and tabs work, etc. However, when you go to login with the admin account you used previously, that worked from tracd it fails with "Invalid username or password" In fact, you can keep both instances running, meaning tracd on port 8000 and a bloodhound site a different port, say 80 or 8080 and only the tracd instance lets the admin or users login. Did I miss a step or is there further documentation needed to setup the initial admin account when using PostgreSQL and apache? I searched thru the docs and FAQs but didn't see anything perhaps I missed it or overlooked the obvious. Please advise, thanks. SEG
