https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31378 --- Comment #69 from David Cook <dcook@prosentient.com.au> --- Here is the TL;DR version: Question: 1. I noticed that the default "Mapping configuration" is just 1-to-1 for strings, but Oauth/OIDC claims can be complex data structures. How do you handle when the claim is an array or an object? The most common one I see in the real world is the "address" object, but there are others too. Looking at Koha/Auth/Client/OAuth.pm and Koha/Auth/Client.pm, I think that you have added code for this. Would it be "address.street_address" in the Mapping to get the "street_address" value out of the "address" claim? The code is uncommented and a bit obscure, so I can't tell if you can handle array values, although I'm less worried about them. Can you? TODO: 0. Add missing "Help" link to all new pages 1. Restrict "Code" to alphanumeric code 2. Add help text to "New authentication provider" UI 3. Add help text to "Edit authentication provider domain" UI 4. Fix breadcrumb on "Edit authentication provider domain" UI 5. Remove exception text from Koha staff interface login page 6. Remove exception text from Koha OPAC login page 7. Think about changing "tranverse_hash" to "traverse_hash" 8. Fix "Auto register" 9. Fix "Update on login" -- You are receiving this mail because: You are watching all bug changes.