Are EntityIDs wildcardable in any of the configuration files?

[Peter Schober]

* Martin, Andrew J. <AMartin at towson.edu> [2013-10-15 16:38]:
> 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).

That isn't really too useful considering the number of SPs out there,
most of which don't share anything in their entityID to group them
by. Simply OR'ing their entityIDs together in the
PolicyRequirementRule (one of the things Kevin suggested) will make
this work in a single AttributeFilterPolicy, allowing you to effect
changes for all of those SPs at once.

Also by auto-reloading the filter after changes adding an entityID
isn't too much work, really.

Btw, you can always add a pseudo-URI (or your own test-SP) to OR' it
together with any existing entityID, so that you don't have to
restructure your rules for a service should there be another entityID
added later (i.e., going from 1 to more than 1 entityIDs would require
rewriting your rule from a single AttributeRequesterRule to an OR rule
with a attribute requester child rule).
-peter