[Openid-specs-ab] Issue #2143: Evaluation order of custom metadata policy operators (openid/connect)

[rolandh]

New issue 2143: Evaluation order of custom metadata policy operators
https://bitbucket.org/openid/connect/issues/2143/evaluation-order-of-custom-metadata-policy

Roland  Hedberg:

The document specifies the evaluation order of the standard operators. What if one adds a custom operator ? Can it be inserted anywhere in the ordered list of are there restrictions as to where they can be added.

To begin with I think the evaluation order of the standard operators are fixed and can not be modified.

I also think that **value** must come first since it ‘over rides’ any other operator and that **essential** should come last since you would like to have the result of applying all the other operators before evaluation **essential.**

My proposal is that:

* The evaluation order of the standard operators are fixed and can not be modified.
* Custom operators MUST be placed after the **value** operator in the evaluation order
* Custom operators MUST be placed before the **essential** operator in the evaluation order

‌

Responsible: Roland  Hedberg