1 260
szerkesztés
Módosítások
Új oldal, tartalma: „JRA5 Attribute Conversion allows a Bridging Element administrator to define rules to transform attributes being released or received. The same logic can work in both Home ...”
JRA5 Attribute Conversion allows a Bridging Element administrator to define rules to transform attributes being released or received. The same logic can work in both Home and Remote Bridging Elements.
== Introduction ==
[[Image:JRA5Attributes_bigpicture.png|Attributes:The Big Attribute Picture]]
Attributes are travelling on the wire in eduGAIN-defined format, ie. SAML. Naming attributes and defining their contents might be a standardization task of eduGAIN operators; however it should be possible for federations to agree on custom set of attributes beyond "eduGAIN commons".
Attribute Conversion only adds attributes (or values) to the attribute set; use [[JRA5AttributeFiltering | Attribute Filtering]] for filtering out unnecessary attributes. It also means that if no rules match an attribute, then it will go to the filter unmodified - so conversion works with a '''default by-pass policy'''.
== Writing rules ==
Most of the rules are based on standard [http://en.wikipedia.org/wiki/Regular_expression regular expressions] and [http://en.wikipedia.org/wiki/Unified_Expression_Language Unified Expression Language].
Each rule works on the actual attribute set which is not necessarily the initial set, as each rule can alter the set (ie. by changing values or names, adding new attributes to the set). This means that the '''order of the rules is important'''.
Rules can contain a Condition element to declare the conditions when the rule matches. Matches can be defined for
* remote peer's name (RemoteProviderMatch)
* attribute name
* attribute value
A rule without a condition is evaluated as <code>.*</code>: it matches by default. A rule is only processed for the first matching attribute. Because the order of the attributes is undetermined, you should avoid using too general conditions.
=== BasicRule ===
=== MergeRule ===
=== SplitRule ===
=== CustomRule ===
=== Quick guide for using unified EL with rules ===
== Using name mapper ==
== Testing ==
=== XMLTest.sh ===
=== Real-life examples ===
== Introduction ==
[[Image:JRA5Attributes_bigpicture.png|Attributes:The Big Attribute Picture]]
Attributes are travelling on the wire in eduGAIN-defined format, ie. SAML. Naming attributes and defining their contents might be a standardization task of eduGAIN operators; however it should be possible for federations to agree on custom set of attributes beyond "eduGAIN commons".
Attribute Conversion only adds attributes (or values) to the attribute set; use [[JRA5AttributeFiltering | Attribute Filtering]] for filtering out unnecessary attributes. It also means that if no rules match an attribute, then it will go to the filter unmodified - so conversion works with a '''default by-pass policy'''.
== Writing rules ==
Most of the rules are based on standard [http://en.wikipedia.org/wiki/Regular_expression regular expressions] and [http://en.wikipedia.org/wiki/Unified_Expression_Language Unified Expression Language].
Each rule works on the actual attribute set which is not necessarily the initial set, as each rule can alter the set (ie. by changing values or names, adding new attributes to the set). This means that the '''order of the rules is important'''.
Rules can contain a Condition element to declare the conditions when the rule matches. Matches can be defined for
* remote peer's name (RemoteProviderMatch)
* attribute name
* attribute value
A rule without a condition is evaluated as <code>.*</code>: it matches by default. A rule is only processed for the first matching attribute. Because the order of the attributes is undetermined, you should avoid using too general conditions.
=== BasicRule ===
=== MergeRule ===
=== SplitRule ===
=== CustomRule ===
=== Quick guide for using unified EL with rules ===
== Using name mapper ==
== Testing ==
=== XMLTest.sh ===
=== Real-life examples ===
