https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39224 --- Comment #2 from Jacob O'Mara <jacob.omara@openfifth.co.uk> --- Created attachment 189234 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=189234&action=edit Bug 39224: add database schema for shibboleth configuration Add shibboleth_config and shibboleth_field_mappings tables to store Shibboleth authentication configuration in the database. Includes atomic update to migrate existing XML-based configurations. TEST PLAN: Prerequisites - A SAML setup - Enable ShibbolethAuthentication system preference - Access staff interface with manage_identity_providers permission Test Configuration Interface (Staff → Administration → Shibboleth) 1. Access UI - Navigate to Shibboleth configuration page 2. Basic Settings - Toggle force SSO for OPAC/staff, autocreate, sync, welcome email 3. Field Mappings - Add mappings with IdP field names 4. Set Matchpoint - Mark one field as matchpoint; verify only one can be active 5. Default Values - Test mappings with default_content when idp_field is empty Test Authentication Behavior 6. OPAC SSO - Enable force_opac_sso; verify OPAC auto-redirects to Shibboleth login URL 7. Staff SSO - Enable force_staff_sso; verify staff interface auto-redirects 8. Disable force SSO; verify local login form shows with Shibboleth link 9. Autocreate - Enable autocreate; authenticate new user; verify patron record created 10. Sync on Login - Enable sync; modify IdP attributes; login; verify patron data updated Test Error Cases 11. No Matchpoint - Remove matchpoint; reload login page; verify Shibboleth login option disappears entirely; check logs for "No matchpoint configured" warning 12. Invalid Mapping - Create mapping without koha_field or (idp_field + default_content); verify validation error 13. Duplicate Matchpoint - Set second matchpoint; verify first is auto-cleared Verify Legacy Compatibility 14. Syspref Removed - Confirm OPACShibOnly and staffShibOnly sysprefs no longer exist/used 15. Run tests and ensure they pass and that the migration will work as expected. prove -vv t/db_dependent/Auth_with_shibboleth.t t/db_dependent/Koha/ShibbolethConfigs.t t/db_dependent/Koha/ShibbolethFieldMappings.t t/db_dependent/Shibboleth/Migration.t t/db_dependent/api/v1/shibboleth_config.t t/db_dependent/api/v1/shibboleth_field_mappings.t -- You are receiving this mail because: You are watching all bug changes.