Cross domain auth

I have a scenario where a single hono api serves different frontends
the api is at domain a.com
frontends are at domain b.com, c.com, etc

I set config like this

defaultCookieAttributes: {
  httpOnly: true,
  path: '/',
  sameSite: process.env.NODE_ENV === 'production' ? 'none' : 'lax',
  secure: process.env.NODE_ENV === 'production',
 },

defaultCookieAttributes: {
  httpOnly: true,
  path: '/',
  sameSite: process.env.NODE_ENV === 'production' ? 'none' : 'lax',
  secure: process.env.NODE_ENV === 'production',
 },

but no luck.

Is there anything I'm missing or is this case not possible?

Client has this enabled:

fetchOptions: {
 credentials: 'include',
},

fetchOptions: {
 credentials: 'include',
},

Allowed origins all set

Better Auth•9mo ago

Tom Ebeyer

Cross domain auth

I have a scenario where a single hono api serves different frontends
the api is at domain a.com
frontends are at domain b.com, c.com, etc

I set config like this

defaultCookieAttributes: {
  httpOnly: true,
  path: '/',
  sameSite: process.env.NODE_ENV === 'production' ? 'none' : 'lax',
  secure: process.env.NODE_ENV === 'production',
 },

defaultCookieAttributes: {
  httpOnly: true,
  path: '/',
  sameSite: process.env.NODE_ENV === 'production' ? 'none' : 'lax',
  secure: process.env.NODE_ENV === 'production',
 },

but no luck.

Is there anything I'm missing or is this case not possible?

Client has this enabled:

fetchOptions: {
 credentials: 'include',
},

fetchOptions: {
 credentials: 'include',
},

Allowed origins all set

Cross domain auth

Similar Threads

Cross domain auth

Similar Threads

Similar Threads

Similar Threads