"But if we delete the group from AEM and try re-sync again from LDAP the group query does not trigger at all or inconsistent behavior" - it's expected. To sync the group, you need to delete at least one user that is a member of that group. Note: it syncs groups only in conjunction with syncing users...
I don't think it will be a trivial task to complete. Check the CF node structure: - original /content/dam/test/t3/jcr:content/renditions/original - version /content/dam/test/t3/jcr:content/renditions/test_var_1 and teh metadata placeholder is common for both variations: /content/dam/test/t3/jcr:cont...
user.membershipNestingDepth=I"2" - controls groups sync. Note, it does not syncing individual groups only when syncing a user's membership ancestry, i.e. if a syncing use is a member of a group, then teh group will be synced with AEM repository.
What's stripping the custom tags is XSS filter [0], which is based on OWASP AntiSamy. You can find and customize the configuration for it under /libs/cq/xssprotection/config.xml. There you can add rules to allow your custom tag.Also, check if this article helps [1] [0]https://docs.adobe.com/docs/en/...
What exact version of AEM 6.4 do you have? Can you try the latest SP? One more test, if you drop the campaign component to your template, something Text and Personalization (Campaign) component, do you see campaign variables?
"why I should I monitor the CQ-number although I get notified via an update of the case" - that is not what I've explained to you. While working on the case we will let you know to what service pack the code fix will be added. SP release date can be located at https://helpx.adobe.com/experience-mana...
Well, our established process is to wait up until we know to what SP release the code fix will be included. Support has to share this information in the case's notes. As such you will know for sure the SP release date.