Dynamic Client Registration (DCR) lets a client register itself automatically with an authorization server instead of using fixed, preconfigured credentials. The client sends its metadata to the server, receives a client ID and possibly a client secret in return, and can immediately use these for OAuth2 or OpenID Connect flows. This enables automated onboarding and removes the need for manual credential setup.
The idea is:
Native support for OAuth2 Dynamic Client Registration (DCR), allowing clients to obtain their OAuth2 credentials (client ID/secret) dynamically at runtime.
My use case:
An API offers DCR to obtain credentials at runtime. While I could look up the OpenID configuration and handle the client registration manually with curl, this is only a workaround. Built-in support would streamline the process and remove the need for manual steps.
I think it would be beneficial to add this because:
Currently, such APIs can only be integrated through workarounds using HTTP Request nodes. Built-in DCR support would simplify connecting to modern APIs, reduce potential errors, and provide a clear quality-of-life improvement.