- Mar 10, 2014
- Reaction score
Blue Iris uses its own cookie named "session" and it kind of looks like you might be making a cookie that conflicts with that. However I would expect the result of such a misconfiguration to be you getting redirected back to your apache login page after a successful apache login...We run an apache reverse proxy server for accessing all internal services using subdomain names.
My setup works fine for everything I have added in except for blueiris.
Our setup uses a custom LDAP form so that when anypage is accessed, the user has to login with their domain credentials then apache will show the page requested. This works fine for any services provided thru the proxy and in some cases you have to login twice, once for the apache access, then second for the service access. For example, accessing the nas is nas.example.com, you then get an LDAP authentication page, then once logged in you get the NAS login page.
But for Blue Iris, and again happens on both UI2 and UI3, the Apache LDAP login just sits there and eventually timesout. If I remove the Apache Auth, then all works perfectly and I get direct access to the Blue Iris login page.
Is there something tricky going on with the login page that I need to accomodate for in Apache? Would rather prefer to have the LDAP authentication prior to accessing BI as it logs all staff access. If someone is interested, here is the Virtual Host for BI, removing the <location> section removes Apache Authentication and all works: