BugLogHQ is a tool to centralize the handling of automated bug reports from multiple applications. BugLogHQ provides a unified view of error messages sent from any number of applications, allowing the developer to search, graph, forward, and explore the bug reports submitted by the applications.
I've setup BugLogHQ to work inside a Kerberos-secured environment (via Apache integration, using mod_auth_kerb). This allows me to use it in a enterprise-like environment, with Active Directory integration and single sign-on features.
It would be great if I could tell the app not to bother with logging the user in but instead just trust the HTTP auth info available in headers, you could even auto-create the user just like hosts and apps, this would allow us to set admins manually after they've logged in.
I've setup BugLogHQ to work inside a Kerberos-secured environment (via Apache integration, using mod_auth_kerb). This allows me to use it in a enterprise-like environment, with Active Directory integration and single sign-on features.
It would be great if I could tell the app not to bother with logging the user in but instead just trust the HTTP auth info available in headers, you could even auto-create the user just like hosts and apps, this would allow us to set admins manually after they've logged in.