https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27309
--- Comment #5 from David Cook <[email protected]> --- (In reply to Magnus Enger from comment #4) > (In reply to David Cook from comment #3) > > Could you elaborate more on your use case for this? I don't understand why > > you'd need to capture and store the password. > > In Norway we have a national patron database, that among other things holds > patron's PIN codes. These are encrypted using a key that only vendors have > access to. To be able to store and transmit the encypted PIN in the correct > format, we need to be able to capture it, and encrypt it in the way the > national patron database expects, so we can sync it to other ILSes. > > This was not my idea, and it might change in the future, but for now it is > something we have to implement, in order to be able to answer RFPs etc. Thanks for explaining. I think that I understand more now. I just took a peek at bug 11401 and https://lanekortet.no/ (thanks Google Translate). I wonder why they don't use something like LDAP or use SSO. Inertia maybe. I still think how the NNPDB works is bizarre but I understand the rationale. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
