Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
while conducting additional tests with repo-init i noticed that TestUtil.parseAndExecute always persists a given operation, which doesn't entirely seem to reflect that nature of the RepositoryInitializer which will only call Session.save after the processing of a list of operations. While each create-path operation is already following by a save-call to prevent issues with the resource-based access control setup, the principal-based ac-setup will currently fail if the service user principal has not been persisted.
Proposed fix: if the principal-lookup returns null during principal-based ac setup -> retry after saving pending changes. That's at least consistent with the current behaviour in the resource-based setup.
Attachments
Issue Links
- links to