Are EntityIDs wildcardable in any of the configuration files?

[Martin, Andrew J.]

Greetings fellow Shibboleth users and admins,

At Towson University, we too have recently integrated with SalesForce SSO. This integration includes one instance of production, as well as three different sandbox environments (DEV/TEST/QA). I've found that maintaining this data in Shibboleth's configuration file has become rather onerous when things change, or environments refresh. All of these environments have very similar settings and EntityIDs on the Shibboleth side.

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.

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).

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.

Thanks in advance for any replies.

-Andy

Andy Martin
Systems Developer
Architecture and Identity Services
Office of Technology Services
Towson University
410-704-4591

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20131015/73a8ca77/attachment.html