...
Most use cases for this feature tend to be for relying party overrides, which are already supported separately. If you need to use this kind of condition elsewhere, you can reuse the same code with this example:. The example shows the use of two different tag “values” to check for, one that’s standardized and one that’s custom, just to show how to handle two values at once.
| Expand |
|---|
| title | Relying Party By Tag |
|---|
|
| Code Block |
|---|
| <!-- Tag condition -->
<bean id="MyCondition" parent="shibboleth.Conditions.EntityDescriptor">
<constructor-arg name="pred">
<bean class="net.shibboleth.idp.saml.profile.logic.MappedEntityAttributesPredicate">
<constructor-arg>
<list>
<bean class="org.opensaml.saml.common.profile.logic.EntityAttributesPredicate.Candidate"
c:name="http://macedir.org/entity-category"
p:values="#{{ 'http://refeds.org/category/research-and-scholarship', 'http://example.org/mycategory' }}" />
</list>
</constructor-arg>
</bean>
</constructor-arg>
</bean> |
|
...