[Openid-specs-ab] Question to Dynamic Client Registration implementers

[Filip Skokan]

Hi Vladimir,

see below

curl -sX POST https://op.panva.cz/reg -H 'content-type: application/json'
-d '{"redirect_uris":["https://rp.example.com"], "grant_types":null}' | jq


*{*

  *"error"**: *"invalid_client_metadata"*,*

  *"error_description"**: *"grant_types must be an array"

*}*

During DCR Management Update however, null, or property omission, is
considered a signal to remove, or set a default value to a property.

IIRC my initial implementation had null treated as "not provided" for DCR
create as well, for some reasons which I cannot recall (but git blame &
commit history could probably reveal that) this was changed.

S pozdravem,
*Filip Skokan*


On Fri, 22 Sept 2023 at 20:41, Vladimir Dzhuvinov via Openid-specs-ab <
openid-specs-ab at lists.openid.net> wrote:

> This is a question to implementers of OIDC Dynamic Client Registration:
>
> Does your implementation return an "invalid_client_metadata" error when
> parsing a metadata parameter with a null value, or does it treat that as if
> the metadata parameter is absent from the request?
>
> For example:
>
> POST /clients HTTP/1.1
> Content-Type: application/json
>
> {
>    "redirect_uris":
>      ["https://client.example.org/callback" <https://client.example.org/callback>],
>    "grant_types": null <--- metadata parameter with null value
> }
>
>
> Thanks,
>
> Vladimir
>
> --
> Vladimir Dzhuvinov
>
> _______________________________________________
> 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/20230923/caa33fe5/attachment-0001.html>