AEM 6.2: NonExistingResource for node under etc

[srikanth_pogula]

Hi,

Is there any change in behaviour of ResourceResolver(org.apache.sling.api.resource) in AEM 6.2 because it returns me NonExistingResource when trying to resolve resource(node) under /etc/xxx.

This used to work fine in AEM 6.0 SP3.

For example, We have few data pages under /etc/lists/top-navigation-configuration-page which we(anonymous users in publish) were able to resolve in WCMUse classes in AEM 6.0 SP3 using getResourceResolver.resolve("etc/lists/top-navigation-configuration-page"). But this piece of code is returning NonExistingResource in AEM 6.2. However, using service resource resolver(resolverFactory.getServiceResourceResolver(param)), resources under /etc/xxx are resolved.

Thanks in advance

[Feike_Visser1]

author or publish?

[srikanth_pogula]

Hi Feike Visser,

The issue is in publish for anonymous user.

[Feike_Visser1]

Validate the ACL/permissions, they have changed since 6.1.

It is most likely an issue with permissions.

[bhaskar3bk]

I believe, you should create a System User and get resource resolver using Resource Resolver Factory and then try to resolve any path.

[srikanth_pogula]

Hi Feike,

Permissions for anonymous user? Can you please elaborate.

[srikanth_pogula]

Hi bhaskar3bk,

The approach you have mentioned i.e. service resource resolver(in AEM 6.2) is a replacement for admin resource resolver(in AEM 6.0), but the issue i reported is about resource resolver implicit object in AEM component jsp or WCMUse class unable to resolve resources under /etc/*** even the cloud service configurations.

In AEM 6.0 SP3, we were able to resolve without admin resource resolver.

[Feike_Visser1 · Accepted solution]

Every user has permissions, also the anonymous user.

Since 6.1 those permissions are more strict in /etc

[srikanth_pogula]

Hi Feike,

Thanks for the information. Anonymous user do not have read permissions in AEM 6.2 but available in AEM 6.0.

Workaround is to get service resource resolver and resolve resources under /etc/xxx