Comments (2)
Also trying EmailProvider
w/ Resend, I am making the request on http://tenant.localhost:3000, the email URL is tenant.localhost:3000/api/auth/callback/[...] and then when I click the link, it redirects me back to localhost:3000 (no subdomain)
from next-auth.
I do face this weird issue. After being logged in, I could see the cookie authjs.callback-url
is been set to http://localhost:3000/
in my PROD for a second and then been corrected to my PROD url http://aaa.bbb.com
. Due to this at times it's been redirected to http://localhost:3000/
when session timeout. I have no traces of http://localhost:3000/
anywhere in my code or environment variable. I haven't set AUTH_URL
as it's not necessary for v5 and I faced some other issues while setting it.
I use
"next": "14.1.4"
"next-auth": "^5.0.0-beta.18",
from next-auth.
Related Issues (20)
- Simple Mistake - Easy FIX next.js sdk can't get the correct error type of credentials provider HOT 1
- [v5] AUTH_URL doesn't work from the client's side HOT 1
- What is the correct way to overwrite the function signIn in Callbacks in v5? HOT 3
- auth.js tries to import $env/dynamic/private in SvelteKit frontend
- Authorization result overriding custom `User.id` retruned in `OAuthConfig.profile` callback HOT 1
- Authorization result overriding custom `User.id` returned in `OAuthConfig.profile` callback in v5 HOT 2
- `@auth/sveltekit` should not depend on `preact` HOT 1
- `@auth/sveltekit` should not depend on `preact` HOT 1
- Unclear what GitHub bot considers to be a valid reproduction HOT 5
- Oauth custom provider wellKnown not functioning in v4->v5 update HOT 1
- Getting "The requested module 'node:crypto' does not provide an export named 'constants'" for basic SvelteKit project using Cloudflare Pages HOT 6
- Cannot return custom error to the client side in the Next-Auth v5 Credentials Auth HOT 1
- Cannot return custom error to the client side in the Next-Auth v5 Credentials Auth HOT 1
- Cannot return custom error to the client side in the Next-Auth v5 Credentials Auth HOT 5
- Custom Provider w/ wellKnown Failure (v5) HOT 2
- Invalid argument provider_providerAccountId in Prisma adapter HOT 1
- Unknown argument `provider_providerAccountId`. Did you mean `providerId_providerAccountId`? Available options are marked with ?. HOT 1
- Unknown argument `provider_providerAccountId`. Available options are marked with ? HOT 2
- I can't import GoogleProvider
- @balazsorban44 - We updated as you suggested, but we are getting the following error - "invalid_client (AADSTS7000218: The request body must contain the following parameter: 'client_assertion' or 'client_secret' HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from next-auth.