github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-22 22:32:01 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[GH-ISSUE #1731] Follow OAuth spec RFC7591 "Dynamic Client Registration" for the OIDC plugin /register endpoint #8891

New Issue
Closed
opened 2026-04-13 04:08:32 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-13 04:08:32 -05:00
Owner
Copy Link

Originally created by @remorses on GitHub (Mar 8, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/1731

Is this suited for github?

  • Yes, this is suited for github

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

MCP is working on adding authorization support via OAuth, this means you can use better-auth with the OIDC plugin to create MCP servers that support authorization which is great!

One missing feature is a RFC7591 "Dynamic Client Registration" compliant way to register clients.

Here are the differences in the current /register endpoint and the RFC7591:

  • Change request field names to match RFC7591 standard (e.g., redirectURLs → redirect_uris)
  • Support standard metadata fields: token_endpoint_auth_method, grant_types, response_types, etc.
  • Update response format to include client_id, client_secret, client_id_issued_at, client_secret_expires_at
  • Implement standard error responses: invalid_redirect_uri, invalid_client_metadata, etc.
  • Add required HTTP headers and use 201 status code for successful registrations

Describe the solution you'd like

Make the /register endpoint RFC7591 compliant

Describe alternatives you've considered

.

Additional context

I can work on a PR if you like the idea

Originally created by @remorses on GitHub (Mar 8, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/1731 ### Is this suited for github? - [x] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. MCP is working on adding [authorization support via OAuth](https://spec.modelcontextprotocol.io/specification/draft/basic/authorization/), this means you can use better-auth with the OIDC plugin to create MCP servers that support authorization which is great! One missing feature is a RFC7591 "Dynamic Client Registration" compliant way to register clients. Here are the differences in the current `/register` endpoint and the RFC7591: * Change request field names to match RFC7591 standard (e.g., `redirectURLs` → `redirect_uris`) * Support standard metadata fields: `token_endpoint_auth_method`, `grant_types`, `response_types`, etc. * Update response format to include `client_id`, `client_secret`, `client_id_issued_at`, `client_secret_expires_at` * Implement standard error responses: `invalid_redirect_uri`, `invalid_client_metadata`, etc. * Add required HTTP headers and use 201 status code for successful registrations ### Describe the solution you'd like Make the /register endpoint RFC7591 compliant ### Describe alternatives you've considered . ### Additional context I can work on a PR if you like the idea
GiteaMirror added the locked label 2026-04-13 04:08:32 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label locked
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#8891
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?