AEM 6.5 - CUG policies(rep:cugPolicy) are not replicated to publish instances during page activation

Avatar

Avatar
Validate 1
Level 1
Andrii_H
Level 1

Likes

0 likes

Total Posts

3 posts

Correct reply

1 solution
Top badges earned
Validate 1
Affirm 1
View profile

Avatar
Validate 1
Level 1
Andrii_H
Level 1

Likes

0 likes

Total Posts

3 posts

Correct reply

1 solution
Top badges earned
Validate 1
Affirm 1
View profile
Andrii_H
Level 1

16-01-2021

Hi All!

 

During page activation rep:cugPolicy is not activated and is missed on the publish instance.

Environment AEM 6.5.6.0(with aem-service-pkg-6.5.6-1.0.zip installed) upgraded from AEM 6.4

Author:

screenshot_8.png

 

Publish:

screenshot_9.png

During activation, I am logged in as an admin user. replication-receiver(part of administrators group) set as transport user for the replication agent(I also tried with admin user).

At the same time at local AEM 6.5(not upgraded from 6.4), everything works fine.

 

I would be grateful for any help or point in the right direction.

 

Regards,

Andrii

 

 

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Validate 1
Level 1
Andrii_H
Level 1

Likes

0 likes

Total Posts

3 posts

Correct reply

1 solution
Top badges earned
Validate 1
Affirm 1
View profile

Avatar
Validate 1
Level 1
Andrii_H
Level 1

Likes

0 likes

Total Posts

3 posts

Correct reply

1 solution
Top badges earned
Validate 1
Affirm 1
View profile
Andrii_H
Level 1

18-01-2021

I found out the reason. jcr:readAccessControl was missed for the replication-service user under the root path.screenshot_10.png

Answers (1)

Answers (1)

Avatar

Avatar
Validate 10
MVP
kunal23
MVP

Likes

166 likes

Total Posts

565 posts

Correct reply

173 solutions
Top badges earned
Validate 10
Validate 1
Ignite 3
Ignite 1
Give Back 50
View profile

Avatar
Validate 10
MVP
kunal23
MVP

Likes

166 likes

Total Posts

565 posts

Correct reply

173 solutions
Top badges earned
Validate 10
Validate 1
Ignite 3
Ignite 1
Give Back 50
View profile
kunal23
MVP

16-01-2021

Have you checked the error logs of publish instance and replication agent ? Do you see any errors there ?