Troubleshooting a data release issue for InCommon and RandS

[Peter Schober]

Cooper, Robert A via users <users at shibboleth.net> [2025-08-07 16:29 CEST]:
> I fixed a similiar issue last year for another entity by creating an
> explicit deny rule for the email attribute, but I'd like to figure
> out a more general solution that doesn't require tacking on each
> entityID as we come across the broken ones.  Has anyone else
> experienced this, or have any suggestions that might provide a fix?

So you're asking how to deal with SPs that cannot handle multi-valued
mail attributes, but without having to enumerate those SPs?

Seems the only answer that's left then would be to stop asserting
multi-valued mail attributes in general then.
Which sounds involved if your environment is such that you do have
(and likely: require/desire) to assert those.

In other words: Unless you manage to turn your current system of
expectations and practices on its head (by stopping to assert
multi-valued mail attributes in all/most cases) Whac-A-Mole
(enumerating SPs that can't handle this) seems the only way of
handling this, IMO.

Best,
-peter