RelyingPartyByTag require multiple entity attribute values

Cantor, Scott cantor.2 at osu.edu
Wed Jun 10 17:19:33 EDT 2015


On 6/10/15, 4:37 PM, "users on behalf of Jeffrey Crawford" <users-bounces at shibboleth.net on behalf of jeffreyc at ucsc.edu> wrote:

>That almost worked on the first try! If you wanted to use that as a template for someone else, the only thing I needed to do was replace '>' with '/>' on the TagCandidate lines.

Yeah, I caught that afterward, sorry.

>From the example structure it seems like I should also be able to arbitrarily mix and match "matching Types".

Yes, it's just more wiring, though in some cases it will end up that you need to put the AND/OR part around the outside at the activationCondition property level, not inside the structure I built.

> I know I originally only asked for a combination of tags but a global group might
> be interesting too. So I tried the following in one of the "AND'd" constructor-args:
><bean class="org.opensaml.saml.common.profile.logic.EntityGroupNamePredicate"
>      c:groupNames="urn:mace:ucsc.edu:metadata:local" />

In that specific case, yes, it should work. Both Predicates run against the same input, the EntityDescriptor in the metadata, so the top level Predicate is that StrategyIndirectedPredicate weird thing I built, with the actual Predicate sitting inside that class.

>But I think I'm missing something in the section:
><bean class="com.google.common.base.Functions"
>      factory-method="compose">
>
>because the log is complaining about a missing beans in the constructor arguments, however I'm not understanding the connection between the classes to understand what's missing.

I'd have to see the underlying error but a lot of the time when it complains it's either a mistyped property or argument name.

-- Scott



More information about the users mailing list