Why CUG is not getting published with content? | Community
Skip to main content
akshaybhujbale
Level 6
Aug 4, 2022 4:22 AM UTC
Solved

Why CUG is not getting published with content?

In official documents they have siad that-

"CUG policies are published with content"

I have added CUG to ClosedAclCheck

Then I have published it 

But there is no CUG in published ClosedAclCheck folder.

Why?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Sachin_Arora_
Sachin_Arora_Accepted solution
New Participant
Aug 4, 2022 5:17 AM UTC

I tried same on we-retail and its working fine in AEM 6.5.13 version. I am able to replicate the above scenario. Its happening when user is not present in Publisher. You can check if rep:cugPolicy node is replicated fine on Publisher under the folder you are replication. This node will have property rep:principalNames containing user/group name. Please refer below screenshot:

 

As test user is not available in publisher instance so its not showing in DAM.

 

 

 

View reply

3 replies

DEBAL_DAS
DEBAL_DAS
New Participant
Aug 4, 2022 11:37 AM UTC

CUG in author -

 

 

CUG is reflecting on Publish instance [AEM 6.5.11] -

 

Test on AEM 6.5.11-

 

Here Test CUG is my Closed User Group

Translate
    arunpatidar
    arunpatidar
    New Participant
    Aug 4, 2022 7:35 AM UTC

    Hi,

    Cug nodes get published with content.

    YOu may not be able to see it on publish if you don't have read ACL permissions. 

    Translate
    Arun Patidar
      Sachin_Arora_
      Sachin_Arora_Accepted solution
      New Participant
      Aug 4, 2022 5:17 AM UTC

      I tried same on we-retail and its working fine in AEM 6.5.13 version. I am able to replicate the above scenario. Its happening when user is not present in Publisher. You can check if rep:cugPolicy node is replicated fine on Publisher under the folder you are replication. This node will have property rep:principalNames containing user/group name. Please refer below screenshot:

       

      As test user is not available in publisher instance so its not showing in DAM.

       

       

       

      Translate
        Terms & ConditionsAccessibility statement

        Loading footer...