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>.us.auth0.com/oidc/register' \
--header 'content-type: application/json' \
--data '{"client_name":"My Dynamic Application","redirect_uris": ["https://application.example.com/callback", "https://application.example.com/callback2"] }'
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.
update
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…