Auth0 Integration and Role-Based Access Control for Event Data Management

[Chayan8837]

Auth0 Integration and Role-Based Access Control for Event Data Management

Description

This PR implements the integration of Auth0 authentication and role-based access control (RBAC) to manage event data. Admin users can now modify event data, while regular users are restricted from accessing or editing event data.

Fixes #133

Type of change

Implementation Details

1. User Model Modification:

• Added a role field to the user model in the database, where the role can be changed by an admin (via the backend/database).

2. Event Data API:

• Created an API endpoint to manage event data.
• Added middleware to ensure only users with the admin role can access and modify event data.

3. Role Verification Middleware:

• Implemented backend verification using middleware to restrict unauthorized access to API endpoints.
• Middleware checks the user’s role and blocks access to event data modification if the user is not an admin.

4. Event Page UI:

• On the frontend, the "Edit Event Data" button is now conditionally displayed based on the user’s role.
• A client-side middleware checks the user’s role to ensure the "Edit Event Data" button is only visible to admin users.

5. Token Update Middleware:

• Added middleware to update the user's role in the JWT token if their role changes in the database, allowing the user to access the new role's permissions without needing to log in again (optional but recommended for user experience).

6. Error Handling:

• Proper error handling for unauthorized access attempts to ensure users receive meaningful messages when trying to access restricted functionalities.

• user view
  

• admin view
  

• client Middleware

-- user permisions

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Test Configuration:

• Firmware version:
• Hardware:
• Toolchain:
• SDK:

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[Chayan8837]

@MAVRICK-1 @devsayanR please check the pr

[MAVRICK-1]

@Chayan8837 great work, @devsayanR could you please review it once

[devsayanR]

Hey you haven't put the api key into the .env file??

[Chayan8837]

No , base branch , using the apy key directly ,so I just add mine ,but I will chnge it before merge ,
And the firabase config too ..

[Chayan8837]

ok , add this api key in env fie

[devsayanR]

Good

[Chayan8837]

any other chnges ?