[Openid-specs-ab] Issue #2078: [Federation] Specify the applicable JSON types for each policy operator (openid/connect)

Vladimir Dzhuvinov issues-reply at bitbucket.org
Mon Oct 30 16:29:57 UTC 2023


New issue 2078: [Federation] Specify the applicable JSON types for each policy operator
https://bitbucket.org/openid/connect/issues/2078/federation-specify-the-applicable-json

Vladimir Dzhuvinov:

Currently OpenID Federation specifies a set of 7 policy operators. Operators like `value`, `default` and `essential` can be expressed with any JSON type and applied to any JSON type. Others, by their nature, like `one_of`, can only be formulated as a JSON array and operate on strings. To ensure interop the spec should define the exact applicable JSON types for every operator.

[https://openid.net/specs/openid-federation-1\_0.html#name-operators](https://openid.net/specs/openid-federation-1_0.html#name-operators)

The ambiguous places:

* Is `add` allowed to be specified as JSON string when a single value is being added to the metadata parameter?  
* What types can go into the JSON arrays of `add`, `one_of`, `superset_of`, `subset_of` ?

‌



More information about the Openid-specs-ab mailing list