http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8785 Priority: P5 - low Change sponsored?: --- Bug ID: 8785 CC: dpavlin@rot13.org Assignee: gmcharlt@gmail.com Summary: Basic authentication troubleshootings Severity: normal Classification: Unclassified OS: All Reporter: matthias.meusburger@biblibre.com Hardware: All Status: NEW Version: master Component: Authentication Product: Koha I've ran several tests with basic http authentication in koha, and here's what I found: When using basic http authentication at OPAC, if the loggedin username does not match a valid koha user, that leads to a session with borrowernumber 0. When using basic http authentication at Intranet, if the loggedin username does not match a valid koha user, that also leads to a session with borrowernumber 0. At the top-right of the screen, I can see "insecure" in bold black. However, my "insecure" syspref is set to 0. Is this behavior normal? Steps to reproduce: To use basic http authentication at OPAC, create a .htaccess and a .htpasswd file in the 'opac' directory. To use basic http authentication at Intranet, create a .htaccess and a .htpasswd file at the root of the source directory (don't forget to backup the existing .htaccess) In order to easily generate .htaccess and .htpasswd, you can use the following tools: http://www.htaccesstools.com/htaccess-authentication/ http://www.htaccesstools.com/htpasswd-generator/ -- You are receiving this mail because: You are watching all bug changes.