Unable to resolve tags in AEM 6.3 using Tag Manager | Community
Skip to main content
M
meghag95928867
Level 2
November 17, 2017
Solved

Unable to resolve tags in AEM 6.3 using Tag Manager

  • November 17, 2017
  • 5 replies
  • 4261 views

Hi All,

We are upgrading from AEM 6.2 to AEM 6.3. In one of our jsp we are trying to get tags using Tag Manager but in publish instance tag manger is not able to find tags as etc is hidden for anonymous user.

We are getting Tag Manager by adapting resourceResolver (implicit object).

TagManager tagManager = resourceResolver.adaptTo(TagManager.class); // Geting Tag Manager value

Tag tag = tagManager.resolve("/etc/tags/abc"); // When resolving tag is null

Iterator<Tag> iteratorTag = tag.listChildren(); // null pointer exception

Could you please help in finding solution.

Thanks,

Megha Gowroji

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 manoj_devapath

The current use always need at least read access to resolve any path in this case its Tag. There is no other approach to resolve. You need to update your instance permissions.

Ref:

User, Group and Access Rights Administration

5 replies

smacdonald2008
smacdonald2008
Level 10
November 17, 2017

Does you solution work in Author?

manoj_devapath
manoj_devapath
Level 5
November 17, 2017

Can you pls check user permissions for that tag or root tag. other that API looks straight forward.

M
meghag95928867Author
Level 2
November 17, 2017

Ya it works on author and works on publish if we give etc permissions to anonymous  user.  Is it recommended to do it or any other approach?

M
meghag95928867Author
Level 2
November 17, 2017

Permissions for root tag are not given for anonymous user. issue is when we are accessing page in publish with active login.

It works if etc/tags permissions are given for anonymous user in publish environment. Is there any other way to do it? 

manoj_devapath
manoj_devapathAccepted solution
Level 5
November 17, 2017

The current use always need at least read access to resolve any path in this case its Tag. There is no other approach to resolve. You need to update your instance permissions.

Ref:

User, Group and Access Rights Administration

Terms & ConditionsAccessibility statement

Loading footer...