[Openid-specs-ab] RP Metadata Choices Interoperability

[Filip Skokan]

The following feedback is based on an implementation of the OpenID Connect
Relying Party Metadata Choices 1.0 - draft 01
<https://openid.net/specs/openid-connect-rp-metadata-choices-1_0-01.html>
document
I did recently.

I believe the interop concerns to be valid but the proposed text solution
should be accompanied by a description of the AS behaviour when both the
choice and its related single value metadata parameters are present and the
single metadata parameter value is not supported by the AS.

The draft should also instruct the AS to

   - ignore unrecognized/unsupported members of choice metadata parameter
   arrays
   - error when none of the of the members of choice metadata arrays are
   supported


S pozdravem,
*Filip Skokan*


On Wed, 16 Apr 2025 at 05:25, Michael Fraser via Openid-specs-ab <
openid-specs-ab at lists.openid.net> wrote:

> Hi all,
>
>
>
> As mentioned on Monday’s call, I’ve raised an issue against the RP
> Metadata Choices document along with a PR with some suggested text to
> address it.
>
>
>
> The issue focuses on interoperability concerns when the metadata defined
> by this document is used in an ecosystem that may contain OpenID Provider
> deployments that might not understand or support it.
>
>
>
> Looking for thoughts and comments
>
>
>
> https://github.com/openid/rp-metadata-choices/issues/2
>
> https://github.com/openid/rp-metadata-choices/pull/3
>
>
>
> Thanks,
>
>
>
> Michael Fraser
> _______________________________________________
> Openid-specs-ab mailing list
> Openid-specs-ab at lists.openid.net
> https://lists.openid.net/mailman/listinfo/openid-specs-ab
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20250416/89087a28/attachment.htm>