Capabilities and capability sets now have “permission“ attribute which has value equal to “permissionName“ value of corresponding Folio permission. This allows for direct matching between Folio permissions to Eureka capabilities/sets.

But for some permissions, corresponding capabilities/sets cannot be found using this approach.

Scope:

1. Find all permissions for which capabilities/sets cannot be found by using mapping approach when capability/set is found by permission attribute equal to permissionName attribute of Folio permission. Module descriptors for each module can be used to get all actual valid and usable permissions.

2. Fix issues with matching permissions to capabilities/sets.

Acceptance criteria:

All Folio permissions can be matched to either capability of capability set granting a user the same abilities as original Folio permission

Additional info:

• Resolving issues with permission-capability matching is a pre-requisite for starting work on updating Cypress test framework to assign appropriate capabilities/sets to each test user (currently, an admin user is used to run auto-tests on Eureka environments)

• Attached a file with permissionNames for which capabilities/sets were not found using approach described above (only permissions currently used in Cypress E2E tests were used) - for this file, LoC Phase 2 Sandbox 2 dry run (FSE/INT) (non-ECS) environment was used (on February 19th)

Open

• Attached a file with problematic matchings from https://folio-org.atlassian.net/browse/MODROLESKC-154 (presumably, contains all entries unmatched due to duplicates). According to information from developers, for this file, LoC Phase 2 Sandbox 2 dry run (FSE/INT) environment was used (on February 15th)

Open