You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
(If I have understood the intention of the role correctly)
An user added to group authentik Read-only can't access admin interface
To Reproduce
Steps to reproduce the behavior:
add an user to group authentik Read-only
login with that user
there is no admin interface button
Expected behavior
it should be present the admin interface button
Screenshots
there is no button present
add permission to fix:
Logs
Version and Deployment:
authentik version: surely 2024.8.2 and onwards
Deployment: docker-compose
Additional context
to fix:
Adding the access admin interface permission to the role fix the problem
In the blueprint Default - RBAC -Read-only (blueprints/default/rbac-role-read-only.yaml) :
It takes all the permissions that contain the string view, thus excluding that needed to access the administration interface.
maybe renaming the permission Can access admin interface into Can view admin interface is the simplest fix
The text was updated successfully, but these errors were encountered:
Describe the bug
(If I have understood the intention of the role correctly)
An user added to group authentik Read-only can't access admin interface
To Reproduce
Steps to reproduce the behavior:
Expected behavior
it should be present the admin interface button
Screenshots
there is no button present
add permission to fix:
Logs
Version and Deployment:
Additional context
to fix:
Adding the access admin interface permission to the role fix the problem
In the blueprint Default - RBAC -Read-only (blueprints/default/rbac-role-read-only.yaml) :
It takes all the permissions that contain the string view, thus excluding that needed to access the administration interface.
maybe renaming the permission Can access admin interface into Can view admin interface is the simplest fix
The text was updated successfully, but these errors were encountered: