Machine to Machine Dynamic Application Registration

I’m wondering, how can I specify a dynamically created client as type Machine-to-Machine (for use with an API) at creation time? My high-level goal is to allow our partners and clients the ability to create their own applications, then use a consent flow, access information via a resource server, as per OIDC spec.

Seems like every approach requires me to manually update a “Generic” dynamic application. For instance I can do something like

curl --request POST \
  --url 'https://<tenant>' \
  --header 'content-type: application/json' \
  --data '{"client_name":"My Dynamic Application","redirect_uris": ["", ""] }'

But then it defaults My Dynamic Application to type “Generic”. Ideally, i’d like to specify something like { "app_type": "m2m" }, and be able to “extend” the functionality of the oidc/register endpoint.


Dec 23rd, 2022,

@matiasb had an almost identical issue. It was answered by @dan.woda; his response seems to be about the best solution, but is a lackluster solution…

I haven’t gotten many views (or replys) on this issues. Tagging @konrad.sopala in hopes that this issue gets some eye balls!