Details
-
Task
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
None
-
customfield_11100 41767
-
CP: sprint 102, CP: sprint 103
-
3
-
Core: Platform
-
R1 2021
Description
While discussing OKAPI-839 we have identified a potential issue with overwriting existing permission sets during install/upgrade.
It's possible that a user-defined permission set may clash with a module-supplied permission set.
Potential approaches (best to worse):
- "scope" the permissions so that the clash between user-defined and module-provided permissions is not possible
- compare the "mutable" flag to check if the permission set has been created by the user and if so, rename it to e.g "USER_CREATED.xxx" and update user association
- stop the migration when clash is detected
Tasks:
- Investigate and evaluate how disruptive is the scoping solution. If it is deemed to disruptive evaluate solution number to rename user created permissions.
See https://wiki.folio.org/display/DD/Migration+of+Static+Permissions+Upon+Upgrade
TestRail: Results
Attachments
Issue Links
- blocks
-
MODPERMS-115 Implement static permission migration
-
- Closed
-
-
OKAPI-947 Implement static permission migration
-
- Closed
-
- relates to
-
OKAPI-839 SPIKE: consider migration of static permission and permissionSets
-
- Closed
-
- mentioned in
-
Page Loading...