shibboleth.Conditions.RelyingPartyId regex?

[Cantor, Scott]

On 7/16/15, 11:37 AM, "users on behalf of Liam Hoekenga" <users-bounces at shibboleth.net on behalf of liamr at umich.edu> wrote:

>Can this go in global.xml, or should I put it directly in my intercept flow?

I don't actually recall the use case here.

Any beans in global.xml are, not surprisingly, global. Every Spring context across every little bit of code should be able to reference them (which is why the shibboleth. prefix is used everywhere to make sure we take care with global bean names).

After that it gets more complicated to explain what's visible where. Usually the best choice is either global for sharing or local to the place it's being used for locality of reference, but I suppose if you have a particular organizing philosophy, that trumps anything else, they're your beans.

If you're actually using it inside a flow, it pretty much has to be global or inside the beans file loaded into the flow definition. Each flow gets its own little Spring context at runtime and won't see much else.

If you're using it as a condition attached to, say, a flow descriptor, the best place for that is probably in the intercept-config file where the flow descriptors are.

That's all a little simplified. A lot of the files in conf/ are actually imported into the global Spring context, so a lot of the time anything you put in one of them will be visible everywhere, but that's confusing and not really a great way to think about it, so it isn't organized that way. We tried to create conceptual containers for things even if no actual Spring boundary exists.

-- Scott