Hello, I have a new site running 3.06.02. I have configured LDAP as authentication and it seems to connect, authenticate and create the new patron correctly. The problem is though, that once the user logs in for the first time (and hence creates the Patron record) they are met with a "Error 500" screen. The actual Patron record is created and if they click the login button and login again then it will display the patron page correctly (and does for all subsequent logins). There isn't much in the logs except for a "Malformed Header - opac-user.pl" error. If I add a "Content-type" header to the opac-user.pl script (and not rely on the template to add the header) the first time user can login fine and the page shows correctly. (so this leads me to think the problem is in the page header but only on LDAP creation as a manual Patron creation is fine for first time login) I also noticed that the LDAP auto creation doesn't add an expiration date, even though it assigns the correct Parton Category. So, does anyone gave any ideas before I log a bug and start debugging it? I have used LDAP before on pre 3.06.02 sites with no problems. Thanks Barry
On Wed, Feb 8, 2012 at 18:32, Barry Cannon <barry@oslo.ie> wrote:
Hello,
I have a new site running 3.06.02. I have configured LDAP as authentication and it seems to connect, authenticate and create the new patron correctly. The problem is though, that once the user logs in for the first time (and hence creates the Patron record) they are met with a "Error 500" screen. The actual Patron record is created and if they click the login button and login again then it will display the patron page correctly (and does for all subsequent logins). There isn't much in the logs except for a "Malformed Header - opac-user.pl" error.
Could you please include exact error message including line number? Please also include <ldap_server> part of your koha-conf.xml
I also noticed that the LDAP auto creation doesn't add an expiration date, even though it assigns the correct Parton Category.
LDAP mappings can have default values, so in our example, we want to take LDAP field hredupersonexpiredate or if it's missing 2012-12-23 using following configuration: <mapping> ... <dateexpiry is="hredupersonexpiredate">2012-12-23</dateexpiry> ... </mapping> -- ...2share!2flame... http://blog.rot13.org
Could you please include exact error message including line number?
There is no line number mentioned in the log as the problem is with the header which is generated by the template file (or rather, the included header file). All that is logged is the referer URL
LDAP mappings can have default values, so in our example, we want to take LDAP field hredupersonexpiredate or if it's missing 2012-12-23 using following configuration:
<mapping> ... <dateexpiry is="hredupersonexpiredate">2012-12-23</dateexpiry> ... </mapping>
This is a non runner for any of our sites. Hard coding an expiry date seems excessive. I suspect the older versions used the default expiry period from the Category Code assigned to the new user to calculate the expiry date. I plan and rebuilding this in a staging environment to recreate the problem. Hopefully, I can track the problem down and get a patch out quickly.
participants (2)
-
Barry Cannon -
Dobrica Pavlinušić