nextauthjs / nextauthjs/next-auth

Next auth credentials authentication

Open
#12,005 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug triage
Dominant language
TypeScript
Stars
28.4k
Forks
4k
PR merge metrics
No merged PRs in 30d

Description

Environment
Paste here

System:
OS: Windows 11 10.0.22631
CPU: (4) x64 Intel(R) Core(TM) i5-4300U CPU @ 1.90GHz
Memory: 1.17 GB / 7.90 GB
Binaries:
Node: 20.16.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.22 - ~\AppData\Roaming\npm\yarn.CMD
npm: 10.8.1 - C:\Program Files\nodejs\npm.CMD
pnpm: 9.11.0 - ~\AppData\Local\pnpm\pnpm.CMD
Browsers:
Edge: Chromium (127.0.2651.98)
Internet Explorer: 11.0.22621.3527
npmPackages:
@auth/firebase-adapter: ^2.5.3 => 2.5.3
next: 14.2.13 => 14.2.13
next-auth: ^5.0.0-beta.22 => 5.0.0-beta.22
react: ^18 => 18.3.1

Reproduction URL

https://github.com/Ikuzweshema/next-auth-example

Describe the issue

Next js credentials authentication when a user loggs in with email and password user is redirected but the session remains null and url does not change until you refresh the page do you also face that error??.i dont know if it is for me only or you also face that issue.

How to reproduce

image
i think client components do not get the session when we redirect back and the url does not update so i think you can fix this issue

Expected behavior

As like other providers like google the session should be working as expected and also url should change.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the behavior in the linked next-auth-example repository with the reported Next.js 14.2.13 and next-auth 5.0.0-beta.22 setup, then trace the credentials sign-in redirect and client session update. Done means the URL changes after login and the session is available without a page refresh, as it is with the reported Google provider.

Written by the indexing model from the issue text.

Assessment

Tech stack
next.js, node.js, react, typescript
Domain
authentication, frontend, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.