How to Resolve Repository Error During Node Import: rep:cugPolicy in AEM | Community
Skip to main content
Ravi_Joshi
Ravi_Joshi
Level 4
October 23, 2024
Solved

How to Resolve Repository Error During Node Import: rep:cugPolicy in AEM

  • October 23, 2024
  • 4 replies
  • 1638 views

 

Hi Everyone,

I'm facing an issue during the replication of content into AEM. Specifically, I'm encountering the following error:

Repository error during node import: rep:cugPolicy

I have checked the below points and these are in place:

  • User group is already there on both Author and Publish.
  • Replication agent (service users) has the required permissions.

Any Thoughts ? What causes this error during replication of a page ? 

 

Thanks,

Ravi

 

--- Compact log from publisher ---

 

Caused by: javax.jcr.PathNotFoundException: rep:cugPolicy at org.apache.jackrabbit.oak.jcr.session.NodeImpl$7.perform(NodeImpl.java:558) [org.apache.jackrabbit.oak-jcr:1.22.13]

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Ravi_Joshi

Hi Everyone,

I’ve found a solution to this issue and here’s a quick overview:

Reason: By default, rep:cugPolicy nodes are protected and aren’t included in replication.

Solution: To enable CUG policies on publishers, we need to configure the Apache Jackrabbit Oak CUG configurations in the Config Manager on the publish instance.

Let me know your thoughts, and feel free to share any suggestions or references.

4 replies

arunpatidar
Community Advisor
arunpatidarCommunity Advisor
Community Advisor
October 23, 2024

Hi @ravi_joshi 
Could you please try with admin credentials? could be that Author does not have acl read permissions.

Arun Patidar
    Ravi_Joshi
    Ravi_JoshiAuthor
    Level 4
    October 24, 2024

    Hi @arunpatidar , I am using admin credentials only.

      daniel-strmecki
      Community Advisor and Adobe Champion
      daniel-strmeckiCommunity Advisor and Adobe Champion
      Community Advisor and Adobe Champion
      October 23, 2024

      Hi @ravi_joshi,

      check if your replication-service user has jcr:readAccessControl permissions on the root path.

       

      Good luck,

      Daniel

        Ravi_Joshi
        Ravi_JoshiAuthor
        Level 4
        October 24, 2024

        Hi @daniel-strmecki , It is there for the replication-service.

          A
          Aakarsh
          Level 2
          October 24, 2024

          check jcr:readAccessControl permission for the replication-service user under the root path.

            Ravi_Joshi
            Ravi_JoshiAuthor
            Level 4
            October 24, 2024

            Hi @aakarsh , It is there for the replication-service.

              Ravi_Joshi
              Ravi_JoshiAuthorAccepted solution
              Level 4
              October 25, 2024

              Hi Everyone,

              I’ve found a solution to this issue and here’s a quick overview:

              Reason: By default, rep:cugPolicy nodes are protected and aren’t included in replication.

              Solution: To enable CUG policies on publishers, we need to configure the Apache Jackrabbit Oak CUG configurations in the Config Manager on the publish instance.

              Let me know your thoughts, and feel free to share any suggestions or references.

                Terms & ConditionsAccessibility statement

                Loading footer...