Summary: | LDAP fallback behaviour not consistent | ||
---|---|---|---|
Product: | Koha | Reporter: | Nick Clemens (kidclamp) <nick> |
Component: | Authentication | Assignee: | Nick Clemens (kidclamp) <nick> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P5 - low | CC: | dpavlin, jonathan.druart, kyle, martin.renvoize, nick |
Version: | Main | ||
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: |
Description
Nick Clemens (kidclamp)
2017-07-27 15:52:38 UTC
Bumping severity here, this broke our ldap config after upgrade to 17.05, will try to provide patch next week (In reply to Jonathan Druart from comment #2) > Is this related to bug 18880? I commented on wrong bug, meant for 18947 (In reply to Jonathan Druart from comment #2) > Is this related to bug 18880? And no, I think this exists separate from the work there - the decision is whether we should fallback if the user exists in ldap but password is wrong ( I think we should) |