github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-07-16 23:20:14 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[GH-ISSUE #2720] Allow to specify wildcard domains for trusted origins #9319

New Issue
Closed
opened 2026-04-13 04:45:12 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-13 04:45:12 -05:00
Owner
Copy Link

Originally created by @BjoernRave on GitHub (May 19, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/2720

Is this suited for github?

  • Yes, this is suited for github

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

I have a wildcard url, where I want to accept requests from, so currently I can only do: trustedOrigins: ["*"].

Describe the solution you'd like

trustedOrigins: ["example.com", "*.foo.com"]

Describe alternatives you've considered

trustedOrigins: ["*"]

Additional context

No response

Originally created by @BjoernRave on GitHub (May 19, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/2720 ### Is this suited for github? - [ ] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. I have a wildcard url, where I want to accept requests from, so currently I can only do: `trustedOrigins: ["*"]`. ### Describe the solution you'd like `trustedOrigins: ["example.com", "*.foo.com"]` ### Describe alternatives you've considered `trustedOrigins: ["*"]` ### Additional context _No response_
GiteaMirror added the locked label 2026-04-13 04:45:12 -05:00
GiteaMirror commented 2026-04-13 04:45:14 -05:00
Author
Owner
Copy Link

@Kalyankr commented on GitHub (May 20, 2025):

I do have the issue, I have dynamic subdomains and cannot list all in the trustOrigins, not sure how to handle those.
example
trustedOrigins: [ "http://portal.localhost:3000", "http://oakwood.localhost:3000", ],

TrustOrgins can grow, so having then in list is not possible, do we need to get them from db and pass it as array or any wildcard url can be used.

<!-- gh-comment-id:2895902088 --> @Kalyankr commented on GitHub (May 20, 2025): I do have the issue, I have dynamic subdomains and cannot list all in the trustOrigins, not sure how to handle those. example ` trustedOrigins: [ "http://portal.localhost:3000", "http://oakwood.localhost:3000", ],` TrustOrgins can grow, so having then in list is not possible, do we need to get them from db and pass it as array or any wildcard url can be used.
GiteaMirror commented 2026-04-13 04:45:16 -05:00
Author
Owner
Copy Link

@dosubot[bot] commented on GitHub (Aug 19, 2025):

Hi, @BjoernRave. I'm Dosu, and I'm helping the better-auth team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You requested support for wildcard domains like "*.foo.com" in the trustedOrigins configuration for more granular control.
  • Another user mentioned difficulties with dynamic subdomains and the impracticality of listing all trusted origins.
  • The core need is for more flexible origin matching to efficiently handle dynamic or numerous subdomains.
  • No resolution or official support for wildcard or database-driven origin lists has been implemented yet.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of better-auth by commenting below.
  • If I don’t hear back within 7 days, I will automatically close this issue to keep the backlog manageable.

Thanks for your understanding and contribution!

<!-- gh-comment-id:3201345166 --> @dosubot[bot] commented on GitHub (Aug 19, 2025): Hi, @BjoernRave. I'm [Dosu](https://dosu.dev), and I'm helping the better-auth team manage their backlog and am marking this issue as stale. **Issue Summary:** - You requested support for wildcard domains like "*.foo.com" in the trustedOrigins configuration for more granular control. - Another user mentioned difficulties with dynamic subdomains and the impracticality of listing all trusted origins. - The core need is for more flexible origin matching to efficiently handle dynamic or numerous subdomains. - No resolution or official support for wildcard or database-driven origin lists has been implemented yet. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of better-auth by commenting below. - If I don’t hear back within 7 days, I will automatically close this issue to keep the backlog manageable. Thanks for your understanding and contribution!
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#9319
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?