(ECS) 404 errors for a user with an admin role in all tenants in role detailed view in Member tenants
Description
CSP Request Details
CSP Rejection Details
Potential Workaround
Attachments
- 05 Nov 2024, 12:41 PM
- 04 Nov 2024, 08:26 AM
- 01 Nov 2024, 10:53 AM
- 01 Nov 2024, 10:53 AM
- 01 Nov 2024, 10:53 AM
- 01 Nov 2024, 10:53 AM
- 01 Nov 2024, 10:53 AM
Checklist
hideActivity
Yauhen Viazau November 5, 2024 at 12:44 PM
@Mikita Siadykh - please set the RCA group
Yauhen Viazau November 5, 2024 at 12:43 PM
Tested on https://folio-etesting-snapshot-consortium.ci.folio.org/ - works as expected 
Authorization roles can be opened for view on Member tenants, no 404 responses in DevTools. See examples:
Mikita Siadykh November 5, 2024 at 10:56 AM
@Yauhen Viazau could you please verify, changes should be available on last etesting versions
Mikita Siadykh November 4, 2024 at 8:36 AM
@Yauhen Viazau thanks for confirming, no, it’s still need to be fixed (actually PR is prepared), but if functionality is not impacted possibly priority should be changed (but up to you, I don’t insist as fix is almost on ready stage)
Yauhen Viazau November 4, 2024 at 8:26 AMEdited
@Mikita Siadykh - Sorry for not mentioning it specifically. Yes, capabilities/sets are displayed as expected in role detailed view, edit view. Capability/set selection can be edited and saved.
You can close the ticket if you believe the 404s that we are seeing are acceptable, or remove the extra calls.
Details
Details
Assignee
Reporter
Tester Assignee
Priority
P2
Preconditions:
User is logged in https://folio-etesting-snapshot-consortium.ci.folio.org/ as a user having admin role assigned in all tenants
Steps to reproduce:
Switch affiliation to any Member tenant (f.e., “college“)
Go to “Settings“ → “Authorization roles“
Click on the name of any existing role in the second pane
Expected result:
Role detailed view is opened in the third pane, and contains “Capability sets“, “Capabilities“ accordions. Accordions can be expanded and then capabilities/sets will be shown. No failed requests in DevTools.
Actual result:
Role detailed view is opened in the third pane, and contains “Capability sets“, “Capabilities“ accordions. Accordions can be expanded and then capabilities/sets will be shown.
In DevTools, the following API calls are failing with 404 status (see screencast):
GET /roles/bf91ebc1-8ca2-41bb-a71c-427bc8f8e6fc/capability-sets?limit=5000
GET /roles/bf91ebc1-8ca2-41bb-a71c-427bc8f8e6fc/capabilities?limit=5000&query=cql.allRecords%3D1+sortby+resource&expand=true
Response body is:
{ "errors": [ { "message": "Unable to find org.folio.roles.domain.entity.RoleEntity with id bf91ebc1-8ca2-41bb-a71c-427bc8f8e6fc", "type": "EntityNotFoundException", "code": "not_found_error", "parameters": [] } ], "total_records": 1 }Additional info:
NOT reproducible on Central ECS tenant, as well as on non-ECS tenant
Also reproducible when viewing Member roles in “Consortium manager” in Central tenant
See example: