https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23908
--- Comment #5 from David Cook <dc...@prosentient.com.au> --- So Keycloak (the open source Identity and Access Management software) has an "Email verified" attribute for users, and there are several ways that it can be enabled. Administrators can manually enable it, a registration email can include an email verification link, you can update it using a REST API. Those are the methods I know of but there might be more. -- In theory, when importing patrons, any patron may or may not have a verified email address. So I think you just include it as a patron attribute when importing. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list Koha-bugs@lists.koha-community.org 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/
