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

How to configure multiple domains? #1053

New Issue
Closed
opened 2026-03-13 08:20:36 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-03-13 08:20:36 -05:00
Owner
Copy Link

Originally created by @Scholar01 on GitHub (Apr 15, 2025).

My website has multiple domain names. When I log in through another domain name, it prompts that the domain name is not verified. How can I add support for multiple domains?

Originally created by @Scholar01 on GitHub (Apr 15, 2025). My website has multiple domain names. When I log in through another domain name, it prompts that the domain name is not verified. How can I add support for multiple domains?
GiteaMirror commented 2026-03-13 08:20:37 -05:00
Author
Owner
Copy Link

@seanlucakrueger commented on GitHub (Apr 15, 2025):

Hi,
to protect against CSRF attacks and prevent open redirects, you should explicitly define trusted origins in your auth.ts configuration.

The trustedOrigins option allows you to specify a list of allowed origins. Requests from any origin not included in this list will automatically be blocked.

Example:

trustedOrigins: ["http://localhost:3000", "https://better-auth.com"]

From the documentation:

"Trusted origins prevent CSRF attacks and block open redirects. You can set a list of trusted origins in the trustedOrigins configuration option. Requests from origins not on this list are automatically blocked."

Link:
https://www.better-auth.com/docs/reference/security#trusted-origins

@seanlucakrueger commented on GitHub (Apr 15, 2025): Hi, to protect against CSRF attacks and prevent open redirects, you should explicitly define trusted origins in your `auth.ts` configuration. The trustedOrigins option allows you to specify a list of allowed origins. Requests from any origin not included in this list will automatically be blocked. Example: `trustedOrigins: ["http://localhost:3000", "https://better-auth.com"]` From the documentation: > "Trusted origins prevent CSRF attacks and block open redirects. You can set a list of trusted origins in the `trustedOrigins` configuration option. Requests from origins not on this list are automatically blocked." Link: https://www.better-auth.com/docs/reference/security#trusted-origins
GiteaMirror commented 2026-03-13 08:20:37 -05:00
Author
Owner
Copy Link

@dencir commented on GitHub (Apr 15, 2025):

Hi, to protect against CSRF attacks and prevent open redirects, you should explicitly define trusted origins in your auth.ts configuration.

The trustedOrigins option allows you to specify a list of allowed origins. Requests from any origin not included in this list will automatically be blocked.

Example:

trustedOrigins: ["http://localhost:3000", "https://better-auth.com"]

From the documentation:

"Trusted origins prevent CSRF attacks and block open redirects. You can set a list of trusted origins in the trustedOrigins configuration option. Requests from origins not on this list are automatically blocked."

Link: https://www.better-auth.com/docs/reference/security#trusted-origins

What if you have a multi-tenant saas which allows users to link custom domains?

@dencir commented on GitHub (Apr 15, 2025): > Hi, to protect against CSRF attacks and prevent open redirects, you should explicitly define trusted origins in your `auth.ts` configuration. > > The trustedOrigins option allows you to specify a list of allowed origins. Requests from any origin not included in this list will automatically be blocked. > > Example: > > `trustedOrigins: ["http://localhost:3000", "https://better-auth.com"]` > > From the documentation: > > > "Trusted origins prevent CSRF attacks and block open redirects. You can set a list of trusted origins in the `trustedOrigins` configuration option. Requests from origins not on this list are automatically blocked." > > Link: https://www.better-auth.com/docs/reference/security#trusted-origins What if you have a multi-tenant saas which allows users to link custom domains?
GiteaMirror commented 2026-03-13 08:20:37 -05:00
Author
Owner
Copy Link

@seanlucakrueger commented on GitHub (Apr 15, 2025):

I think you can technically use:

trustedOrigins: ["*"]

This will allow all origins — but it's not recommended, especially in production, as it weakens the protection against CSRF attacks and open redirects.

If you need more flexibility or dynamic origin handling, you can either check the origin yourself in a custom Middleware or write your own Better Auth plugin to implement advanced origin logic.

But unfortunately I cannot say whether and how it works exactly.

@seanlucakrueger commented on GitHub (Apr 15, 2025): I think you can technically use: `trustedOrigins: ["*"]` This will allow all origins — but it's **not recommended**, especially in production, as it weakens the protection against CSRF attacks and open redirects. If you need more flexibility or dynamic origin handling, you can either check the origin yourself in a custom Middleware or write your own Better Auth plugin to implement advanced origin logic. But unfortunately I cannot say whether and how it works exactly.
GiteaMirror commented 2026-03-13 08:20:37 -05:00
Author
Owner
Copy Link

@Scholar01 commented on GitHub (Apr 16, 2025):

Thank you very much for your answer!

@Scholar01 commented on GitHub (Apr 16, 2025): Thank you very much for your answer!
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
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#1053
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?