Authenticated User Information Not Displayed in Dashboard Sidebar

[Auro993]

Description

The dashboard displays the wrong signed-in user name. I am signed in as Aurosmita, but the UI shows "Signed in as John" in the user menu / top-right corner.

This is a user session / identity mismatch bug.

---

Steps to Reproduce

1. Sign in to the application as Aurosmita.
2. Navigate to the OpsCord Dashboard.
3. Look at the top-right corner / user menu.
4. Observe the displayed name.

---

Expected Behavior

Should display: Signed in as Aurosmita

---

Actual Behavior

Displays: Signed in as John

---

Environment

• User: Aurosmita (authenticated)
• Displayed user: John
• Page: OpsCord Dashboard (/dashboard or /overview)
• Browser: [e.g., Chrome 134, Firefox 135, Safari 18]
• Environment: [e.g., Production / Staging / Dev]

---

Possible Root Cause (for devs)

• Cached user object in frontend state (localStorage / sessionStorage / Redux / Zustand)
• Backend /me or /user/profile endpoint returning wrong user data
• Session/token still associated with previous user (John)
• Mock or hardcoded fallback user in development mode

---

Workaround for User (if any)

• Clear browser localStorage, sessionStorage, and cookies for the site
• Sign out completely and sign back in as Aurosmita
• Open DevTools → Application → Storage → Clear site data

---

Additional Context

This causes confusion and could impact audit logs or permission checks if the wrong identity is used elsewhere in the app.

---

Severity

🔴 Medium – User-facing identity bug, not a crash but affects trust and usability.

[Nicks-19]

Hi @probably-ABHINAV,

I would like to work on this issue under GSSoC 2026.

I have gone through the issue carefully. The dashboard is currently showing the wrong authenticated user name in the sidebar/user menu, where the signed-in user is Aurosmita but the UI displays Signed in as John. This looks like a user session or identity mismatch issue that needs to be fixed properly without hardcoding any user-specific values.

My approach will be:

1. Trace the dashboard/sidebar user display flow to identify where the displayed name is coming from.
2. Check whether the UI is using:
   • hardcoded fallback user data
   • stale localStorage/sessionStorage data
   • cached frontend state
   • incorrect auth context/user provider data
   • wrong backend profile response
3. Ensure the sidebar always reads the currently authenticated user details from the correct auth/session source.
4. Remove or replace any hardcoded/mock fallback user such as John, if present.
5. Add proper fallback handling only for loading or missing user data, without showing incorrect identity information.
6. Verify that logout/login switching between users does not retain stale user details.
7. Test the dashboard flow after signing in with different users to confirm the correct name is displayed every time.
8. Keep the implementation aligned with the existing project structure, naming conventions, and UI style.
9. Avoid unrelated UI or logic changes and keep the PR focused only on fixing the authenticated user display bug.

I will submit a clean, readable, and focused PR, including proper validation of the auth/user display flow before submission.

Please assign this issue to me.

[github-actions]

👋 This issue has been automatically marked as stale because it has had no activity for 7 days. It will be closed in 3 days if no further activity occurs.
If you're still working on this, please comment to keep it open.