[Openid-specs-ab] Issue #2092: Consider new policy operator - intersects (openid/connect)

[Stefan Santesson]

New issue 2092: Consider new policy operator - intersects
https://bitbucket.org/openid/connect/issues/2092/consider-new-policy-operator-intersects

Stefan Santesson:

I just throw this in the mix in case you find this worth to adress.

While going through the policies we would like to apply I ran into a problem.

For cases like supported acr values, no one of the current operators seems to do the job. What I would need is a Value check that I choose to call “intersects” with the following meaning:

> Holds an Array of values. If the metadata parameter is present at least one of its values MUST be one of those listed in the operator values.

Example: I like to require that at least one of the acr values \[“loa3“, “loa4”,”eidas-substantial”,”eidas-high”\] must be included. Additional acr outside of this list may be included.

We consider including this as an additional custom operator, but perhaps more implementers have a similar need. Thus offering it here for consideration.