- Joined
- Mar 29, 2014
- Messages
- 2,422
- Reaction score
- 910
Hi all,
We (@DNF Admin and @birajst) are continuing work on the DNF AI Hub and would appreciate technical advice from developers, registrars, SaaS operators, and anyone who has implemented OAuth connections in a hosted multi-user platform.
The AI Hub already has two working connection methods:
The next planned connection is OpenAI ChatGPT / Codex OAuth.
The intention is clear: a DNForum member with an eligible OpenAI subscription should be able to authorise their own account and use the connection through DNForum, without needing to create, fund, and enter an API key.
The problem
The current OpenAI / Codex authorisation flow appears to return the user to a
callback.
That works well for a local application, desktop application, or CLI. The app starts a local listener, opens the authorisation page, receives the callback on the same machine, and completes the flow.
DNForum is different. It is a hosted, HTTPS, multi-user web application.
For a production implementation, we would need an OAuth flow with a registered HTTPS callback similar to:
The callback needs to securely preserve the member session and OAuth state, validate the response, exchange the authorisation code server-side, and save only the resulting account connection for that individual DNForum member.
A localhost callback cannot directly complete that server-side connection because the member’s browser is on their own device, while the DNForum integration runs on our infrastructure.
What we are trying to establish
What we will not do
We do not want to work around this by proxying localhost callbacks, asking members to run a local service, copying authorisation codes manually, or handling ChatGPT session cookies. If this is not a supported hosted OAuth use case, we would rather keep the OpenAI API-key connection as the proper route and wait for an official option.
One reason this became especially interesting is that local agent tools such as Hermes Agent show how smooth OAuth can be when a user connects an account to software running on their own machine. Bringing that same simplicity safely into a hosted community product is a different technical problem.
If you have relevant experience, documentation, architecture suggestions, or a contact at OpenAI who can clarify the supported path, please reply here or contact us privately.
The DNF AI Hub is here:
Original announcement:
Any thoughts? Suggestions? Ideas?
Any input is welcome! Helmuts
We (@DNF Admin and @birajst) are continuing work on the DNF AI Hub and would appreciate technical advice from developers, registrars, SaaS operators, and anyone who has implemented OAuth connections in a hosted multi-user platform.
The AI Hub already has two working connection methods:
- OpenAI API key connection, enabling the
command.Code:
/gpt - xAI OAuth connection, enabling the
command.Code:
/grok
The next planned connection is OpenAI ChatGPT / Codex OAuth.
The intention is clear: a DNForum member with an eligible OpenAI subscription should be able to authorise their own account and use the connection through DNForum, without needing to create, fund, and enter an API key.
The problem
The current OpenAI / Codex authorisation flow appears to return the user to a
Code:
localhostThat works well for a local application, desktop application, or CLI. The app starts a local listener, opens the authorisation page, receives the callback on the same machine, and completes the flow.
DNForum is different. It is a hosted, HTTPS, multi-user web application.
For a production implementation, we would need an OAuth flow with a registered HTTPS callback similar to:
Code:
https://www.dnforum.com/account/ai-hub/codex/callbackThe callback needs to securely preserve the member session and OAuth state, validate the response, exchange the authorisation code server-side, and save only the resulting account connection for that individual DNForum member.
A localhost callback cannot directly complete that server-side connection because the member’s browser is on their own device, while the DNForum integration runs on our infrastructure.
What we are trying to establish
- Is there a supported OpenAI OAuth client flow for a hosted web application, with a registered HTTPS redirect URI?
- Can an eligible ChatGPT or Codex subscription be connected to a third-party web platform through an official OAuth flow?
- Is the localhost callback intentionally limited to OpenAI’s local Codex clients and desktop/CLI-style applications?
- Is there an official OpenAI developer route, partner route, or supported alternative that we should use?
- Have any registrars, marketplaces, portfolio tools, or SaaS platforms solved a similar user-account OAuth connection?
What we will not do
We do not want to work around this by proxying localhost callbacks, asking members to run a local service, copying authorisation codes manually, or handling ChatGPT session cookies. If this is not a supported hosted OAuth use case, we would rather keep the OpenAI API-key connection as the proper route and wait for an official option.
One reason this became especially interesting is that local agent tools such as Hermes Agent show how smooth OAuth can be when a user connects an account to software running on their own machine. Bringing that same simplicity safely into a hosted community product is a different technical problem.
If you have relevant experience, documentation, architecture suggestions, or a contact at OpenAI who can clarify the supported path, please reply here or contact us privately.
The DNF AI Hub is here:
Original announcement:
Any thoughts? Suggestions? Ideas?
Any input is welcome! Helmuts
Upvote
0
