Closed razor999920 closed 10 months ago
We could not detect a valid reproduction link. Make sure to follow the bug report template carefully.
To be able to investigate, we need access to a reproduction to identify what triggered the issue. We need a link to a public GitHub repository. Example: (NextAuth.js example repository).
The bug template that you filled out has a section called "Reproduction URL", which is where you should provide the link to the reproduction.
Depending on the reason the issue was closed, you can do the following:
In general, assume that we should not go through a lengthy onboarding process at your company code only to be able to verify an issue.
In most cases, a private repo will not be a sufficient minimal reproduction, as this codebase might contain a lot of unrelated parts that would make our investigation take longer. Please do not make it public. Instead, create a new repository using the templates above, adding the relevant code to reproduce the issue. Common things to look out for:
Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps by opening a new issue.
We look into every issue and monitor open issues for new comments.
However, sometimes we might miss a few due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.
Upvoting issues to show your interest will help us prioritize and address them as quickly as possible. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it.
Environment
Reproduction URL
N/A
Describe the issue
I am trying to make my authentication work using the middleware.ts file. However, the system does not redirect back to the callback URL from the middleware.
Let's say you are in the dashboard and you have a protected route in your nav menu (Let's say your protected route is /ab). You click on the ab button in the nav menu which will check if the user is logged in through the middleware file. If the user is not logged in, they are redirected to /login page and are required to log in. Once the user is logged in, they are redirected back to the dashboard. Now as a logged-in user, if they click on the ab button in the Nav menu they are not redirected to the /ab page and instead, the system just reloads the dashboard.
The following screenshot represents the network stack of the steps mentioned above (after a logged in user clicks on the /ab protected route:![redirect](https://github.com/nextauthjs/next-auth/assets/43019476/16443565-3c14-455d-bf42-f9232bfb5083)
How to reproduce
middleware.ts
api/auth/[...nextauth]/route.ts
Expected behavior
The expected behavior should be to redirect to the specified back in the callback URL after the middleware checks the authentication.