AEM 6.2 - how to retrieve page replication status using system user | Community
Skip to main content
rajneeshg
rajneeshg
Level 2
February 11, 2018
Solved

AEM 6.2 - how to retrieve page replication status using system user

  • February 11, 2018
  • 9 replies
  • 7161 views

AEM version - 6.2

System user has jcr:read and crx:replicate privilege on the page whose replication status is being looked up.

resourceResolverProps.put(ResourceResolverFactory.SUBSERVICE, "pageStatusSystemUser");
try {
    resourceResolver = resourceResolverFactory.getResourceResolver(resourceResolverProps);
} catch(Lo...) {
    .....
}
session = resourceResolver.adaptTo(Session.class);
replicationStatus = replicator.getReplicationStatus(session,"/content/sitename/pagename");

session object is available suggesting the system user is correct, however the replicationStatus object is always null, any clues on what is missing please? Is the system user privileges correct? (Verifying the system user using /useradmin console shows both read and replicate privileges are available on /content/sitename/pagename content )

    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 Julio_Tobar

    rajneeshg, there are few things I'd try to get it fix.

    1. use resourceResolverFactory.getServiceResourceResolver(resourceResolverProps); instead of "resourceResolverFactory.getResourceResolver(resourceResolverProps);"
    2. immediately after getting the "resourceResolver" object check to see the mapped System User: resourceResolver.getUserID(); this should map the system user you mapped; if it does not return the user you mapped then check your configuration, must likely you didn't add the right bundleId to the mapping
    3. Once you are sure you are using the system user you created and still cannot access the data then try assigning the user to the administrators group, this way you can rule out permission issues. Once you do get access to the data you need then remove the user from the administrators group and assigned tailored permissions

    /* get a handle to the resourceResolver */

            logger.info("get ResourceResolver");

            // prepare params to get system user

            Map<String, Object> serviceParams = new HashMap<String, Object>();

            serviceParams.put(ResourceResolverFactory.SUBSERVICE, SUBSERVICE);

            try {

              // get resource resolver for the system user set in user mapper

                ResourceResolver resourceResolver = resourceResolverFactory.

                                                                    getServiceResourceResolver(serviceParams);

               

                /* get a handle to ReplicationStatus */

                logger.info("get ReplicationStatus using user: " + resourceResolver.getUserID());

                Resource resource = resourceResolver.getResource(PAGE_CHECK_REPLICATION);

                logger.info("Resource: " + resource.getPath());

                ReplicationStatus replicationStatus = resource.adaptTo(ReplicationStatus.class);

               

                /* show replication status of the resource */

                logger.info("LAST REPLICATION USER: " + replicationStatus.getLastPublishedBy());

                PrintWriter out = response.getWriter();

                out.print ("REPLICATION USER FOR " + PAGE_CHECK_REPLICATION + " IS " +

                                                                      replicationStatus.getLastPublishedBy());

                out.flush();

                out.close();

               

            } catch (LoginException e) {

                e.printStackTrace();

            }

    9 replies

    Ravi_Pampana
    Community Advisor
    Ravi_PampanaCommunity Advisor
    Community Advisor
    February 11, 2018

    Hi,

    You can use session to get the jcrcontent node of the required page and read cq:lastReplicationAction property to find replication status of page.

    String activationStatus = "";

    Node pageJcrNode = session.getNode("/content/sitename/pagename/jcr:content");

         if(pageJcrNode != null && pageJcrNode.hasProperty("cq:lastReplicationAction")) {

           activationStatus = pageJcrNode.getProperty("cq:lastReplicationAction").getString();

         }

    Hope this helps.

    rajneeshg
    rajneeshgAuthor
    Level 2
    February 12, 2018

    Thanks you for the response.

    Still fails with a repository exception.(system user has jcr:read,crx:replicate privilege on /content/sitename/pagename only)

    If I am not wrong this is a privilege issue. Are any jcr/crx privilege(s) missing for the system user?

    (ReplicationStatus and Node look up works perfectly with the deprecated session method - repository.loginAdministrative(null))

    smacdonald2008
    smacdonald2008
    Level 10
    February 12, 2018

    As you said it works when using the resolverFactory.getAdministrativeResourceResolver method, i would consider white listing the bundle. I have seen cases where this happens - not matter how many permissions you give the system user - it will not work like getAdministrativeResourceResolver. I am not sure why that occurs.

    Julio_Tobar
    Julio_TobarAccepted solution
    Level 3
    February 13, 2018

    rajneeshg, there are few things I'd try to get it fix.

    1. use resourceResolverFactory.getServiceResourceResolver(resourceResolverProps); instead of "resourceResolverFactory.getResourceResolver(resourceResolverProps);"
    2. immediately after getting the "resourceResolver" object check to see the mapped System User: resourceResolver.getUserID(); this should map the system user you mapped; if it does not return the user you mapped then check your configuration, must likely you didn't add the right bundleId to the mapping
    3. Once you are sure you are using the system user you created and still cannot access the data then try assigning the user to the administrators group, this way you can rule out permission issues. Once you do get access to the data you need then remove the user from the administrators group and assigned tailored permissions

    /* get a handle to the resourceResolver */

            logger.info("get ResourceResolver");

            // prepare params to get system user

            Map<String, Object> serviceParams = new HashMap<String, Object>();

            serviceParams.put(ResourceResolverFactory.SUBSERVICE, SUBSERVICE);

            try {

              // get resource resolver for the system user set in user mapper

                ResourceResolver resourceResolver = resourceResolverFactory.

                                                                    getServiceResourceResolver(serviceParams);

               

                /* get a handle to ReplicationStatus */

                logger.info("get ReplicationStatus using user: " + resourceResolver.getUserID());

                Resource resource = resourceResolver.getResource(PAGE_CHECK_REPLICATION);

                logger.info("Resource: " + resource.getPath());

                ReplicationStatus replicationStatus = resource.adaptTo(ReplicationStatus.class);

               

                /* show replication status of the resource */

                logger.info("LAST REPLICATION USER: " + replicationStatus.getLastPublishedBy());

                PrintWriter out = response.getWriter();

                out.print ("REPLICATION USER FOR " + PAGE_CHECK_REPLICATION + " IS " +

                                                                      replicationStatus.getLastPublishedBy());

                out.flush();

                out.close();

               

            } catch (LoginException e) {

                e.printStackTrace();

            }

      smacdonald2008
      smacdonald2008
      Level 10
      February 13, 2018

      Great answer julio - do you find it works better when using getServiceResourceResolver instread of getResourceResolver?

      Julio_Tobar
      Julio_Tobar
      Level 3
      February 13, 2018

      HI Scott (-sorry if I misspelled your name-), Actually both methods work differently, as per documentation (http://sling.apache.org/apidocs/sling7/) we should be using getResourceResolver() when we provide further configurations and use getServiceResourceResolver() when we want to assign privileges via a service provided by calling the bundle; sutil but relevant.

      ResourceResolver Guatemala, Central America

      joerghoh
      Adobe Employee
      joerghohAdobe Employee
      Adobe Employee
      February 13, 2018

      HI,

      I think that it is not sufficient just to have read permissions on the content node to determine the replication status. Be aware what this functionality is doing. It checks all pending replication events if the page is part of such an replication event. If it's not, it is obviously not part of an ongoing replication and the status from the page itself can be used.

      That means that your service user should also have permissions to read all sling replication jobs (stored in /var/eventing/jobs). And I believe, that the privilege "crx:replicate" is not required.

      Jörg

      rajneeshg
      rajneeshgAuthor
      Level 2
      February 14, 2018

      Thank you everyone, here is the solution which works for me.

      1. System user has only jcr:read permission on the page - /content/sitename/pagename

      2.

      resourceResolverProps.put(ResourceResolverFactory.SUBSERVICE, "pageStatusSystemUser"); 
      try { 
          resourceResolver = resourceResolverFactory.getServiceResourceResolver(resourceResolverProps);
          Resource resource = resourceResolver.getResource("/content/sitename/pagename");
          if(resource != null) {
              ReplicationStatus replicationStatus = resource.adaptTo(ReplicationStatus.class);
          }
      } catch(Lo...) { 
          ..... 
      }
      rajneeshg
      rajneeshgAuthor
      Level 2
      February 14, 2018

      Is whitelisting used so that we continue using the deprecated methods? Starting from v6.3?

      Terms & ConditionsAccessibility statement

      Loading footer...