1 260
szerkesztés
Módosítások
→Attribute conversion rule types: added ''negate'' concept
'''CustomRule''' class must implement the <code>net.geant.edugain.attributes.rules.Rule</code> interface, configuration can be read with the DOM API. Please refer to the Attribute Converter JavaDOC, and see the test package as it contains a sample implementation.
=== Negating matches ===
If your federation has ''optional'' attributes then sometimes it is desirable to process rules '''only if a particular attribute does not exist.''' Therefore it is possible to append a '''<code>negate</code>''' boolean attribute (setting it to '''true''') to the '''<AttributeMatch>''' and the '''<RemoteProviderMatch>''' nodes (inside '''<Condition>''' element) to revert the match. It means that the rule is only processed if there is no match in the attribute set (or to the remote provider string).
The following example creates <code>preferredLanguage</code> only if it is not set by the IdP (or by the peer's home bridging element):
<source lang="xml">
<BasicRule>
<Decription>Create preferredLanguage only if source has not supplied it</Decription>
<Condition>
<AttributeMatch attributeName="preferredLanguage" negate="true"/>
</Condition>
<Attribute attributeName="preferredLanguage">
<AttributeValue>hu, en-gb;q=0.8, en;q=0.7</AttributeValue>
</Attribute>
</BasicRule>
</source>
== Using attribute name mapper ==
