Skip to content

Role based access control implementaion #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 8 commits into from
May 18, 2025

Conversation

fulleni
Copy link
Member

@fulleni fulleni commented May 18, 2025

Status

ready

Description

implemented a role based access control

Type of Change

  • ✨ New feature (non-breaking change which adds functionality)
  • 🛠️ Bug fix (non-breaking change which fixes an issue)
  • ❌ Breaking change (fix or feature that would cause existing functionality to change)
  • 🧹 Code refactor
  • ✅ Build configuration change
  • 📝 Documentation
  • 🗑️ Chore

fulleni added 8 commits May 16, 2025 16:14
- Added permissions and roles
- Created AuthorizationService
- Defined role-permission mapping
- Use UserRole enum
- Use Permission class
- Replaced isAnonymous and isAdmin
- Used UserRole enum for clarity
- Updated auth checks accordingly
…y serialize the UserRole enum in the JWT payload. This change addresses the JWTException seen in the server logs for the /api/v1/auth/anonymous and /api/v1/auth/verify-code routes
- Added key capabilities section
- Updated API endpoints description
- Added access and licensing details
@fulleni fulleni merged commit f665430 into main May 18, 2025
1 check passed
@fulleni fulleni deleted the role_based_access_control_implementaion branch May 18, 2025 16:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant