Skip to content
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

Implement Keycloak for Admin Dashboard #88

Open
6 tasks done
Keegnan opened this issue Dec 5, 2024 · 1 comment · May be fixed by #106
Open
6 tasks done

Implement Keycloak for Admin Dashboard #88

Keegnan opened this issue Dec 5, 2024 · 1 comment · May be fixed by #106
Assignees
Labels

Comments

@Keegnan
Copy link
Collaborator

Keegnan commented Dec 5, 2024

Describe the task
Gate the page and any data that is sent to it using keycloak

Acceptance Criteria

  • A role is made in the keycloak integration that gives certain users admin access
  • Those users, upon login, are directed to the admin dashboard
  • Other users (or those who aren't logged in) are redirected to the main page if they try to access the admin dashboard
  • In the API, data is only returned for any /admin endpoint if the user is an authenticated admin
  • IDIR users without the "Admin" role should see a message indicating in they do not need permission
  • "Login" button changed to "Admin Login" to indicate that not all users can login

Additional context

@Keegnan Keegnan changed the title Implement Keycloak for Admin Dash Implement Keycloak for Admin Dashboard Dec 5, 2024
@raarielgrace raarielgrace self-assigned this Dec 12, 2024
@raarielgrace raarielgrace linked a pull request Dec 17, 2024 that will close this issue
4 tasks
@Keegnan Keegnan added the Ready label Dec 17, 2024
@raarielgrace
Copy link
Contributor

Moving to blocked because there's what I would consider a bug in the citz-imb-sso-react module. Messaging one of the developers about the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants