[GH-ISSUE #5899] [oidc] Trusted clients should just be regular clients in the oauthApplication table with additional fields #27695

Closed
opened 2026-04-17 18:51:48 -05:00 by GiteaMirror · 3 comments
Owner

Originally created by @bnssoftware on GitHub (Nov 11, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/5899

Is this suited for github?

  • Yes, this is suited for github

Is your feature request related to a problem? Please describe.

No response

Describe the solution you'd like

In order to support a multi-tenant auth service in which end users can configure their own application clients, it is necessary to to manage trusted clients in the regular oauthApplication table, with a skip-consent option. The current method of hard coding this in the config will not work for this scenario.

Describe alternatives you've considered

None

Additional context

No response

Originally created by @bnssoftware on GitHub (Nov 11, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/5899 ### Is this suited for github? - [x] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. _No response_ ### Describe the solution you'd like In order to support a multi-tenant auth service in which end users can configure their own application clients, it is necessary to to manage trusted clients in the regular oauthApplication table, with a skip-consent option. The current method of hard coding this in the config will not work for this scenario. ### Describe alternatives you've considered None ### Additional context _No response_
GiteaMirror added the lockedenhancement labels 2026-04-17 18:51:48 -05:00
Author
Owner

@better-auth-agent[bot] commented on GitHub (Nov 11, 2025):

Thanks for opening this issue! It sounds like you'd like trusted clients to be managed directly within the oauthApplication table by adding additional fields—such as a flag to skip consent—instead of having them hard-coded in the configuration. This approach would certainly simplify multi-tenant setups where end users manage their own application clients.

As a next step, could you share more details on what specific fields you’d like to see added and how you envision the skip-consent behavior integrating with the rest of our client management workflows? Tag @better-auth-agent if you would like an answer from the Agent.

DiagramDiscordGitHub

Diagram Join Star

<!-- gh-comment-id:3515051372 --> @better-auth-agent[bot] commented on GitHub (Nov 11, 2025): Thanks for opening this issue! It sounds like you'd like trusted clients to be managed directly within the oauthApplication table by adding additional fields—such as a flag to skip consent—instead of having them hard-coded in the configuration. This approach would certainly simplify multi-tenant setups where end users manage their own application clients. As a next step, could you share more details on what specific fields you’d like to see added and how you envision the skip-consent behavior integrating with the rest of our client management workflows? Tag @better-auth-agent if you would like an answer from the Agent. <!-- bot:webhook reply v1 --> [Diagram](https://repodiagrams.s3.eu-north-1.amazonaws.com/better-auth_ultra_detailed_interactive.html) • [Discord](https://discord.gg/better-auth) • [GitHub](https://github.com/better-auth/better-auth) [![Diagram](https://img.shields.io/badge/Diagram-2b3137?style=flat-square)](https://repodiagrams.s3.eu-north-1.amazonaws.com/better-auth_ultra_detailed_interactive.html) [![Join](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&style=flat-square)](https://discord.gg/better-auth) [![Star](https://img.shields.io/badge/star-181717?logo=github&logoColor=white&style=flat-square)](https://github.com/better-auth/better-auth)
Author
Owner

@bnssoftware commented on GitHub (Nov 11, 2025):

The additional fields would be "skipConsent" and maybe "trustedClient", but I'm not sure why a trusted client would need to be explicitly flagged other than to allow skipping the consent screen.

<!-- gh-comment-id:3515054043 --> @bnssoftware commented on GitHub (Nov 11, 2025): The additional fields would be "skipConsent" and maybe "trustedClient", but I'm not sure why a trusted client would need to be explicitly flagged other than to allow skipping the consent screen.
Author
Owner

@dvanmali commented on GitHub (Dec 24, 2025):

Hi all, we released the new OAuth Provider Plugin which requires all clients to be on the database yet still cacheable via cachedTrustedClients. Feel free to let us know how it works :)

<!-- gh-comment-id:3688563817 --> @dvanmali commented on GitHub (Dec 24, 2025): Hi all, we released the new [OAuth Provider Plugin](https://www.better-auth.com/docs/plugins/oauth-provider) which requires all clients to be on the database yet still cacheable via `cachedTrustedClients`. Feel free to let us know how it works :)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#27695