[Koha-bugs] [Bug 22461] New: Regression in #20287: LDAP user replication broken with mapped extended patron attributes

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Wed Mar 6 12:09:09 CET 2019


https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22461

            Bug ID: 22461
           Summary: Regression in #20287: LDAP user replication broken
                    with mapped extended patron attributes
 Change sponsored?: ---
           Product: Koha
           Version: 18.11
          Hardware: All
                OS: All
            Status: NEW
          Severity: critical
          Priority: P5 - low
         Component: Architecture, internals, and plumbing
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: oliver.behnke at aei.mpg.de
        QA Contact: testopia at bugs.koha-community.org
  Target Milestone: ---

Reproduce:

1) Use LDAP authentication with user replication
2) Add a field mapping for an extended patron attribute (e.g. MYATTRIB)
3) Try to log in for the first time (new Koha user)
4) Error: "opac-user.pl: DBIx::Class::Row::store_column(): No such column
'MYATTRIB' on Koha::Schema::Result::Borrower at
/usr/share/koha/lib/Koha/Object.pm line 75"

Presumed cause:

Commit [1] changed the way new patrons are created during LDAP replication
(first login). The previous implementation (C4::Members::AddMember) took into
account extended patron attributes by filtering them out before instantiating
the new patron DB object [2]. The current implementation lacks this vital step.

I chose a severity of critical because after upgrading from 18.05 to 18.11 no
new users are able to log in anymore.

Cheers


[1]
https://github.com/Koha-Community/Koha/commit/a6059c4d2d43e43aa021069ce97d6424a76c4f41#diff-56b596ea4e46031303c060d360a16eddL226
[2]
https://github.com/Koha-Community/Koha/blob/1b13c453e20e47c5e25bd946b50dd3838e29c3ce/C4/Members.pm#L448

-- 
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.


More information about the Koha-bugs mailing list