Defining custom attribute names for SPs that won't map names internally

[Max Spicer]

On Thu, 16 Jun 2022 at 13:21, Cantor, Scott <cantor.2 at osu.edu> wrote:

On 6/16/22, 5:27 AM, "users on behalf of Max Spicer via users" <
> users-bounces at shibboleth.net on behalf of users at shibboleth.net> wrote:
> >    We have an SP that cannot map released attribute names to their own
> internal names.
> s/cannot/refuses to
> Obligatory: I would absolutely refuse this in the majority of cases, and I
> do that maybe 2-3 times a year.
>

Totally agree, but sadly it is sometimes a necessary evil.

> We generally use entity groups to group related SPs and then filter by
> entity group rather than specific SPs. Is
> > there an example of how to do this sort of thing?
>
> In the topic on activation conditions. Use entity attribute tags, not
> groups.
>

Thanks. I've now found
https://shibboleth.atlassian.net/wiki/spaces/IDP4/pages/1265631713/ActivationConditions#Relying-Parties-By-Tag.
Moving towards tagged metadata has been on my learning list for a while.

Cheers,

Max
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20220616/53f4f65a/attachment.htm>