Facing below issue while trying to install a package contains all "groups" in one of the AEM 6.0 + SP2 environment. Already tried to delete the existing groups and re-index principalName in oak:index. Also, tried to resynch users using system/console/jmx screen. Please advice, what needs to be done to fix this issue. This package was created from other environment where all the groups exists.
Caused by: org.apache.jackrabbit.oak.api.CommitFailedException: OakConstraint0022: Authorizable property rep:principalName may not be altered after user/group creation.
at org.apache.jackrabbit.oak.security.user.UserValidator.constraintViolation(UserValidator.java:247)
at org.apache.jackrabbit.oak.security.user.UserValidator.propertyChanged(UserValidator.java:98)
at org.apache.jackrabbit.oak.spi.commit.VisibleValidator.propertyChanged(VisibleValidator.java:90)
at org.apache.jackrabbit.oak.spi.commit.VisibleValidator.propertyChanged(VisibleValidator.java:90)
at org.apache.jackrabbit.oak.spi.commit.VisibleValidator.propertyChanged(VisibleValidator.java:90)
at org.apache.jackrabbit.oak.spi.commit.VisibleValidator.propertyChanged(VisibleValidator.java:90)
at org.apache.jackrabbit.oak.spi.commit.EditorDiff.propertyChanged(EditorDiff.java:93)
at org.apache.jackrabbit.oak.plugins.segment.SegmentNodeState.compareProperties(SegmentNodeState.java:596)
at org.apache.jackrabbit.oak.plugins.segment.SegmentNodeState.compareAgainstBaseState(SegmentNodeState.java:491)
at org.apache.jackrabbit.oak.spi.commit.EditorDiff.childNodeChanged(EditorDiff.java:148)
at org.apache.jackrabbit.oak.plugins.segment.MapRecord$2.childNodeChanged(MapRecord.java:389)
at org.apache.jackrabbit.oak.plugins.segment.MapRecord.compare(MapRecord.java:473)
Solved! Go to Solution.
Views
Replies
Total Likes
I don't know the root cause of this issue but you can try the following to install your package - Unzip the package file and in the XML files representing the group nodes remove the rep:principalName property for only those groups which already exists in both source and target instances. After updating the XML, zip them again and upload and test the package on the target.
Views
Replies
Total Likes
I don't know the root cause of this issue but you can try the following to install your package - Unzip the package file and in the XML files representing the group nodes remove the rep:principalName property for only those groups which already exists in both source and target instances. After updating the XML, zip them again and upload and test the package on the target.
Views
Replies
Total Likes
Thanks Kunal, it worked.
Views
Replies
Total Likes