shibboleth.Conditions.RelyingPartyId regex?

Liam Hoekenga liamr at umich.edu
Thu Jul 16 12:36:17 EDT 2015


On Thu, Jul 16, 2015 at 11:45 AM, Cantor, Scott <cantor.2 at osu.edu> wrote:

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

Being able to match RelyingPartyID based on a regex seems like it might be
handy in general, so I put in global.

The example from relying-party.xml uses an "activationCondition" property,
but I *think* that's a RelyingParty thing.

I tried instantiating a shibboleth.RelyingPartyIdRegexPredicate bean, but
it doesn't appear to have any constructors despite it being of class
net.shibboleth.idp.profile.logic.RelyingPartyIdPredicate.

What am I missing?

Liam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20150716/30d05bf0/attachment.html>


More information about the users mailing list