Dashboard need to be locked 1st login/sSignup to access the page

[Amrit1604]

🧩 Summary

Implement authentication-based access control to ensure that the dashboard page remains locked for unauthenticated users. Only users who have successfully logged in or signed up should be able to view or interact with the dashboard.

🎯 Motivation

Currently, the dashboard can be accessed without verifying user authentication, which poses potential security and privacy risks.
By restricting access to authenticated users only, we can:

Prevent unauthorized data exposure

Maintain a consistent and secure user experience

Strengthen the overall application’s access control mechanism

💡 Possible Solution

Implement authentication middleware (for backend routes) or route guards (for frontend routes).

Verify if a valid user session, token, or cookie exists before allowing dashboard access.

Redirect unauthenticated users to the Login or Signup page.

Optionally, show a toast or alert message like “Please log in to continue.”

🧱 Additional Context

This feature aligns with best practices for user authentication and session security.

It will enhance the app’s reliability and help prepare for future role-based access control (RBAC) features.

This issue is being raised under GSSoC '25 (GirlScript Summer of Code).

🚀 Request

I’d love to work on this issue under GSSoC '25.
Please assign it to me so I can begin the implementation. 🙌

🏷️ Tags:

GSSoC25 enhancement authentication backend frontend security

[github-actions]

👋 Thanks for opening this issue! We'll look into it as soon as possible, estimated time for response is 18–24 hrs.
If your issue goes stale beyond this timeframe, kindly contact mentors or PAs via our Discord server.

⏱️ Issue response & contact

• In the meantime, provide screenshots, videos, or other context to speed review and assignment.
• If relevant, please mention whether this issue is raised under GGSoC or OSCI when you create the issue.
• If you have questions, comment below or ping any mentor on discord.

---

📝 Guidelines for Raising Issues

To ensure quality moving forward:
For UI/UX contributions

• You must include a design (Figma link, image, or wireframe) when raising an issue (if applicable).
• Issues without visual references will not be accepted.
• If the change is a modification, share screenshots of the area you want to change.
  For Backend contributions
• You must share a brief execution plan what you intend to build, how it works, and why it's needed.
• Vague issues will be closed without review.

---

📝 Guidelines for Opening Pull Requests

• Your PRs should target the master branch.
• No one is allowed to push directly to main.
• All PRs which do not mention an issue will be closed without review.
• Do NOT raise a PR unless the issue is assigned to you.

---

✅ Quick checklist (please attach before requesting assignment)

• Design link or screenshot (for UI/UX)
• Execution plan (for backend)
• Mention if this is under GGSoC / OSCI
• Any related issue/PR numbers referenced

---

Happy contributing 🚀

[github-actions]

Thank you for opening your first issue in the Open Source Society project. We're excited to have you here! Please make sure to follow the issue template and provide as much detail as possible so we can assist you quickly.Feel free to check out our contributing guidelines and other open issues. Welcome to the community! 🌱

[Amrit1604]

Hi, I'd like to work on this issue under GSSoC. Please assign it to me. 🙌

Checklist:

• This issue is raised under GSSoC.
• I will provide an execution plan before starting the implementation.
• I will ensure clean, tested, and documented code.
• I’ll follow all contribution and PR guidelines.

Thank you! 😊

[Amrit1604]

🧩 Summary

Implement authentication-based access control to ensure that the dashboard page remains locked for unauthenticated users. Only users who have successfully logged in or signed up should be able to view or interact with the dashboard.

🎯 Motivation

Currently, the dashboard can be accessed without verifying user authentication, which poses potential security and privacy risks.
By restricting access to authenticated users only, we can:

Prevent unauthorized data exposure

Maintain a consistent and secure user experience

Strengthen the overall application’s access control mechanism

💡 Possible Solution

Implement authentication middleware (for backend routes) or route guards (for frontend routes).

Verify if a valid user session, token, or cookie exists before allowing dashboard access.

Redirect unauthenticated users to the Login or Signup page.

Optionally, show a toast or alert message like “Please log in to continue.”

🧱 Additional Context

This feature aligns with best practices for user authentication and session security.

It will enhance the app’s reliability and help prepare for future role-based access control (RBAC) features.

This issue is being raised under GSSoC '25 (GirlScript Summer of Code).

🚀 Request

I’d love to work on this issue under GSSoC '25.
Please assign it to me so I can begin the implementation. 🙌

🏷️ Tags:

GSSoC25 enhancement authentication backend frontend security