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
When an administrator is navigating a user page, for example /dashboard#!/user/1d528512-477f-4f9c-b7de-8b7bd27dceeb, the Group Requests and X.509 certificate linking requests panels should show the user's requests.
Instead, the admin requests are shown independently from the user page that they are inspecting.
This is due to the wrong username queried to the API: if we are navigating the user page of the user with userName = foo, the query should be /iam/group_requests?status=PENDING&username=foo.
Instead, the query /iam/group_requests?status=PENDING&username=admin (supposing that admin is the administrator's username) is always performed, no matter which user page the admin is watching.
The text was updated successfully, but these errors were encountered:
rmiccoli
changed the title
Admins are seeing their own group requests and cert link request instead of the users requests
Admins are seeing their own group and cert link requests instead of the users requests
Nov 7, 2024
When an administrator is navigating a user page, for example
/dashboard#!/user/1d528512-477f-4f9c-b7de-8b7bd27dceeb
, theGroup Requests
andX.509 certificate linking requests
panels should show the user's requests.Instead, the admin requests are shown independently from the user page that they are inspecting.
This is due to the wrong username queried to the API: if we are navigating the user page of the user with
userName = foo
, the query should be/iam/group_requests?status=PENDING&username=foo
.Instead, the query
/iam/group_requests?status=PENDING&username=admin
(supposing thatadmin
is the administrator's username) is always performed, no matter which user page the admin is watching.The text was updated successfully, but these errors were encountered: