[OKAPI-851] ensure compatibility between Okapi 3.0 and mod-perms/mod-authtoken - FOLIO Issue Tracker

XML

Word

Printable

We have discussed the following approach:

mod-permission "permission" interface MUST be upgraded to 5.3 from current 5.2 and mod-authtoken dependency on this interfaces must be updated to 5.3
_tenantPermission system interface should be updated to 1.1 from current 1.0 and Okapi 3.0 should check which version is provided at runtime:

if 1.0 is provided, Okapi should fallback to the old behavior which does not wrap modulePermission in a "system" set OR it should fail (adam hji I think failure is acceptable since Okapi 3.0 does not need to be backwards compatible with 2.x and it could simplify code paths
if 1.1 is provided Okapi should wrap modulePermission sets in a "system" set (before posting to mod-permissions) AND use these sets in the X-Module-Permission header (behavior for 3.0)

blocks

MODAT-73 Release mod-authtoken for Q2

MODPERMS-81 Release mod-permissions for Q2

OKAPI-836 Release Okapi for Q2

relates to

MODPERMS-85 Invalid CQL when encoding permission name value

OKAPI-855 Incorrect for _tenantPermissions interface version.

ensure compatibility between Okapi 3.0 and mod-perms/mod-authtoken