Summary: | ldap auth fails unless <ldapserver id="ldapserver"> | ||
---|---|---|---|
Product: | Koha | Reporter: | Jerry Marceau <marceau> |
Component: | Authentication | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | minor | ||
Priority: | P5 - low | CC: | dcook, dpavlin, jonathan.druart |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: | ||
Bug Depends on: | 28385 | ||
Bug Blocks: |
Description
Jerry Marceau
2021-06-17 16:30:21 UTC
Thanks for reporting this. My proposed fix for this is in comment 7 on original bug: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28385#c7 POD documentation in C4::Auth_with_ldap does suggest that id should be ldapserver, so I made assumption that all configurations will have it, which in retrospect seems to be incorrect. (This is a totally unrealted tangent but curious how the University of New Hampshire uses Koha! Doesn't seem to be for the university library?) For Dobrica - thanks for the response. It doesn't really matter to me if this gets 'fixed' or not - I put the bug in so other people could find it if they had the same situation. Making the change in koha-conf.xml is trivial. You're right that the documentation has id="ldapserver", but I don't think it is clear that it has to be set that way. I read the id="ldapserver" as variable - you'd set this to whatever you wanted to call your ldapserver (in our case the short server name). This seems to fit better with HTML and XML in general - you wouldn't have <div id="div">, you'd want the ID to be unique to set it apart. But in this case there aren't going to be multiple ldapservers, so maybe it doesn't matter. David - you're right - it is not for the main/official libraries. We have a few 'media lab' spaces that circulate AV gear - still and video cameras, microphones, etc. They found the library's system (millennium, I think) didn't work well for this sort of equipment. They did the research and settled on Koha - it has worked well for them and hasn't been too much work for me as an administrator. |