Feature/new guard - #1
Open
NayanthaRC wants to merge 11 commits into
Open
NayanthaRC wants to merge 11 commits into
NayanthaRC wants to merge 11 commits into
Conversation
…lations for new dashboards
…oss all dashboards
… Azure AD claims processing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces role-based dashboards and authentication guards for "Administrator", "Model Trainer", and "Super Admin" roles in the Global Classifier application. It adds backend endpoints and frontend pages for each dashboard, implements role-based routing and access control, and defines the necessary role constants and environment variables.
Key changes:
Backend: Role-based dashboards and guards
/admin/dashboard,/model-trainer/dashboard, and/super-admin/dashboard, each with its own guard logic and authority check templates. These endpoints return role-specific dashboard data. [1] [2] [3] [4] [5] [6] [7] [8].env.exampleto include a mapping for theROLE_SUPER_ADMIN.Frontend: Dashboard pages and routing
AdminDashboard,ModelTrainerDashboard, andSuperAdminDashboard, each displaying user info and permissions relevant to the role. [1] [2] [3]App.tsxto import these dashboards, define role constants, and add role-based routes that render the appropriate dashboard or an unauthorized message based on user authorities. [1] [2] [3]AdminDashboardcomponent.These changes collectively provide a foundation for secure, role-specific access and user experience in the application.