https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40023
--- Comment #10 from David Cook <[email protected]> --- (In reply to Tomás Cohen Arazi (tcohen) from comment #0) > It would be handy for external systems to be able to specify the requirement > to embed the patron object in the response of a successful patron > credentials validation. I agree that it would be useful for third-party/external systems to be able to get more information back. I imagine it would be very useful to have fields like name and email. Maybe patron category. -- I'm reminded about OAuth2/OIDC scopes and scope mappers on IdPs. I suppose one way to do this in a Koha-esque way would be to have a system preference that lets you define which fields to include in the patron object response. That way it would be easily adaptable to different Koha instances. We could default to a reasonable minimum while also allowing libraries to easily expand the patron information they want to share with third-parties. If we did a YAML syspref, you could even make different scopes and require different ones from different third-parties. That would be even more powerful. Probably not the best way to do it overall/in the long run, but it would be an all right compromise. And it would be a compromise that would be easy to convert into a different feature down the road, because all the data would be explicit. -- 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/
