Does digirunner support RFC 7591 (Dynamic Client Registration) for use as an OAuth provider with OpenAI Apps SDK?

[MonkeyBinBin]

Hi everyone,

I want to use digirunner as an OAuth provider for applications built with the OpenAI Apps SDK. According to the OpenAI Apps SDK requirements, the OAuth provider must support RFC 7591 (Dynamic Client Registration) so that third-party apps can automatically register clients and complete the authorization flow.

I’d like to confirm a few points:

1. Does digirunner currently support RFC 7591 (Dynamic Client Registration)?
2. If it does not yet support RFC 7591, is there a planned timeline or roadmap to add support? If so, can you share an estimated timeframe or priority?
3. If native support is not planned in the short term, are there recommended alternatives or integration approaches (for example, using an intermediary service, manual client registration processes, or building a proxy to provide dynamic registration) that would allow compatibility with the OpenAI Apps SDK?
4. Are there any relevant docs, examples, or test environments available to help us integrate and validate the setup?

Technical background

• Requirement source: The OpenAI Apps SDK requires the OAuth provider to support RFC 7591 so apps can register clients before the user consents.
• RFC summary: The dynamic registration API (e.g., /register) accepts client_metadata and returns client_id, client_secret, redirect URIs, and supports various client attributes and management operations.
• Goal: Enable end users to initiate the OAuth flow with digirunner through the OpenAI Apps SDK without needing pre-created clients.

Thanks — looking forward to the discussion.

[TPIsoftwareOSPO]

Hi @MonkeyBinBin ,

Thank you for this detailed and well-researched feature request. We appreciate you considering digiRunner as an OAuth provider for the OpenAI Apps SDK.

Let me address your questions directly:

1. Does digiRunner currently support RFC 7591?

You are correct; digiRunner does not currently support RFC 7591 (Dynamic Client Registration).

2. Is there a roadmap for RFC 7591 support?

This is a very valuable capability, and your use case with the OpenAI Apps SDK highlights its importance. We are adding this feature to our development roadmap for serious consideration. While we can't commit to a specific timeline or release priority today, this discussion has raised its visibility significantly.

3. Are there recommended alternatives?

Since native support for RFC 7591 is not available, we looked into other programmatic options.

Unfortunately, we also do not currently offer an Admin API for programmatic client creation.

This means the only method available at this time is manual client registration through our Admin Console. We understand this does not fit the dynamic registration requirement for the OpenAI Apps SDK, but it is the only available path for now.

4. Are there relevant docs or examples?

Because this feature (and any programmatic workaround) is not currently supported, we do not have specific docs or examples for this type of integration.

We have marked this as a feature-request and will track it internally. Thank you again for bringing this to our attention.

Best, digiRunner Team.