Hi there. I'm not an expert on the subject, maybe others can reply, but this is the classical behaviour of applications integrating with LDAP for authentication (and sometimes also authorization): after first login the application creates data in its database, in this example as "Patron". No idea if there's anything out there, but a high level approach would be: 1. Create a test account in LDAP (Active Directory in your case) 2. Dump Koha database (one insert per line is useful) mysqldump --extended-insert=FALSE my_koha_database -u root -psecret > koha.sql 3. Perform first login with user created at step 1. 4. Repeat step 2: mysqldump --extended-insert=FALSE my_koha_database -u root -psecret > koha.after.sql 5. See differences diff koha.sql koha_after.sql Now you are very close to build the SQL statements to add a new Patron once authenticated. Cheers. Javier On Fri, 10 Sept 2021 at 10:46, Tadas G <tadas.kaupa@gmail.com> wrote:
Hello,
We have Koha 21.05 installed and configured to work with AD. Everything is fine, users can login to Koha using AD credentials, but in Patron list they appear only after successful authorisation. It is quite annoying, because if you want to assign book to the reader, he/she has to be in patron list. Is it possible to create Cron job to import users to patron list automatically from AD (it is enough to import only a few fields, all other fields can be updated after user login)?
Thanks for the answers _______________________________________________
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha