I wish to enhance the shibboleth system such that you can adapt the config used depending upon some attribute returned from the identity provider.
Use case: Given an academic institution, such a place may have rather differing information on record for students as opposed to staff. I've had instances where the mapping between attributes and koha fields has differed wildly between these two groups. Given the there is probably an attribute that can differentiate between the two, then we should be able to use that to load a set of mapping specific to that usergroup.
Example intended implementation.
<shibboleth selector="affiliation" value="student">
<shibboleth selector="affiliation" value="staff">
So, in the above example config, the intention would be for koha to look for an 'affiliation' attribute first and foremost, and then depending upon it's value (student or staff) load the corresponding configuration and continue as per normal.