Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • C cosmos-backend
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Cosmos
  • cosmos-backend
  • Merge requests
  • !25

Merged
Created Oct 28, 2024 by Paulo Ricardo Carnovale Cardoso@paulo.cardosoDeveloper

Feature/us 06 meus projetos

  • Overview 5
  • Commits 7
  • Changes 4

In this merge request, I implemented the "My Projects" functionality on the backend, allowing users (students, professors, and institutions) to view and create extension projects they are involved in. This implementation follows the acceptance criteria outlined in the user story and related test cases.

However, it's important to note that a secure authentication mechanism has not been implemented at this stage. Currently, any user with access to the userId parameter could potentially view or modify project information without proper verification. In a production environment, this poses a significant security risk. The current implementation lacks proper protection to ensure that only authenticated and authorized users can access or manage their projects.

Looking ahead, it will be necessary to address this issue by implementing a secure authentication and authorization mechanism, such as JWT (JSON Web Token), to ensure that users can only access their own data and perform actions they are authorized for. This will help prevent unauthorized access and provide a more secure user experience.

While this implementation meets the functional requirements, revisiting and securing these routes in the future will be essential to guarantee the integrity and safety of user data.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: feature/US_06_meus_projetos