🐛 Bug Report: Navbar Still Shows Login/Signup After Login — No Logout Option Available

[thissidemayur]

📜 Description

Description:

After a user logs in successfully, the navbar still shows "Login" and "Signup" options, which can be confusing. It gives the impression that the user is not logged in, even though they are.

Additionally, there's currently no "Logout" button or functionality implemented, so users have no clear way to log out of their session.

This breaks the expected authentication flow and may affect session handling and UX.

Proposed Fix:

I’d like to work on this issue from scratch. Here’s what I plan to do:
1.Detect login state using the existing auth mechanism
2. Dynamically update the navbar to:

• Show "Logout" when the user is logged in.
• Hide "Login" and "Signup" after login.

3. Implement a proper Logout function that clears the session/token and redirects the user to the login or home page.

🙋‍♂️ Request:

Please assign this issue to me if it’s valid — I’d be happy to implement the fix and make the UX smoother for logged-in users.

💻 Operating system

Linux

What browsers are you seeing the problem on?

Chrome

📃 Relevant Screenshots (Links)

demo Screenshot and screenshots showing the issue

[MishtiGarg250]

I want to contribute to this task. please assign me

[mehul-m-prajapati]

@MishtiGarg250 : This issue has been opened by some one else. So, he will work on this.

You can open new issue or work on existing ones which are created by me.

[mehul-m-prajapati]

⏰ This issue was automatically unassigned because no pull request was raised within 5 days. Feel free to reassign if you're still working on it.

[MishtiGarg250]

/assign

[vaish12345678]

Hi! I’m a GSSoC’25 contributor and really interested in working on this issue. If the current assignee becomes inactive or is unable to proceed, I’d love to take it up. Please consider me next in line. Thanks! 😊

[mehul-m-prajapati]

⏰ This issue was automatically unassigned because no pull request was linked within 7 days of assignment. Please request reassignment if you are still working on it.

[vaish12345678]

Hey! I’m facing an issue with session handling after login using Passport.js.

The login is successful — Passport authenticates the user correctly, but the session is not being stored or persisted afterward.

I created a debug route (/debug-session) to inspect the session, and here’s the output: {
"isAuthenticated": false,
"user": null,
"session": {
"cookie": {
"originalMaxAge": null,
"expires": null,
"secure": false,
"httpOnly": true,
"path": "/",
"sameSite": "lax"
}
}
}
I also checked the cookies in browser dev tools — the session cookie is not being set for the backend (localhost:5000), only Clerk cookies are visible for the frontend (localhost:5173).

Additionally, there's no toast message shown after login, such as “Login Successful”.

If it's alright with you, I can replace the current session-based login with JWT-based login/signup/logout, and also implement:

Toast messages for login/logout success/failure.

Token storage securely on the frontend and backend.

However, this approach is more time-consuming, so if you’re okay with this, I’d suggest labeling it as a Level 3 task.

Let me know how you'd like to proceed

[Pranjal-077]

Hey! it seems like the issue is still not resolved. If it's okay, could you please assign it to me? I'd be happy to work on it. 😊