Módosítások

Attribute Conversion for eduGAIN

531 bájt hozzáadva, 2008. szeptember 3., 13:46
Writing rules
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 Attribute conversion rule concepts==
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 Every rule consists of two parts: condition and action. The condition element is used to declare determine whether this particular rule is to be processed or not. Thus, the conditions rule action is only processed when all the conditions are met (a rule matcheswithout any conditions is processed by default). Matches can be defined for The condition engine now only supports regular expression -based matching rules. There is two type of matching rules
* remote peer's name (RemoteProviderMatch)
* attribute name values (AttributeMatch)* attribute valueThe rule's action is to create new attributes (or to modify existing ones). Please refer to the detailed BasicRule, MergeRule, SplitRule documentation below.  === Rule context ===When the conversion rules are processed one after another, each rule has its own rule context bound to it. This context holds references to all the matched attributes too. The rule context is also responsible for supporting the rule's action.
A == Attribute conversion 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.types ==
=== BasicRule ===
=== MergeRule ===
=== CustomRule ===
=== Quick guide for using unified EL with rules ===
 
== Using name mapper ==
== Testing ==
=== XMLTest.sh ===
=== Real-life examples ===
565
szerkesztés

Navigációs menü