Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
while testing OAK-9775 i noticed that CompositeRestrictionProvider.validateRestrictions does not call the validation on the individual aggregated providers. IMHO this will cause OAK-1612 to resurface when the default restriction provider is combined with a additional one.
the fix would be to delegate the validation to the aggregated providers instead.
Attachments
Attachments
Issue Links
- Discovered while testing
-
OAK-9775 ACEs with unsupported restrictions must be cleared upon editing
- Closed
- incorporates
-
OAK-9793 AbstractRestrictionProvider: validation to respect aggregation for unsupported paths
- Closed
-
OAK-9786 Document changes for OAK-9782
- Closed
- is required by
-
OAK-9775 ACEs with unsupported restrictions must be cleared upon editing
- Closed