Are EntityIDs wildcardable in any of the configuration files?

[Kevin P. Foote]

On Tue, 15 Oct 2013, Martin, Andrew J. wrote:

> Is there any way I can "Wildcard" how Shibboleth treats certain EntityIDs in configuration files such as relying-party, or perhaps attribute-filter for attribute release? I can see how it might not make sense in relying-party, since you generally need to link to specific metadata per SP.

For starters you should not be messing with relying-party.xml very much 
(if any) once you are up and running.
Use some form of grouping technique that works for you all to organize
your metadata into larger chunks.

> It would be useful to be able to "match" an EntityID pattern for things like attribute release, rather than have them each listed out separately (which requires a lot of modification when our SalesForce EntityIDs change for upgrades, etc).
>

Create a release that contains all the entityIds for your salesforce
versions. You can use a <PolicyRequirementRule xsi:type="basic:OR"> for
such a release. And add the entityId(s) via the
basic:AttributeRequesterString...

> Obviously it's not the end of the world if there's no way to do it, but as we continue to add SPs, we're looking for better ways to organize and manage our configurations.

You will gain alot of miles out of grouping your RPs into a few main
buckets. Then when a new one comes along you just need to add the
metadata to the right bucket and if need be config a specific release.

There are other historic threads that echo this method.. search the
archives.

HTH

------
thanks
  kevin.foote