It's a known issue, you need to use the latest SP5:https://docs.adobe.com/content/help/en/experience-manager-65/release-notes/service-pack/sp-release-notes.html 

You can possibly use a querry similar to: path=/content/damtype=dam:Assetgroup.1_daterange.property=jcr:content/metadata/@prism:expirationDategroup.1_daterange.upperBound=2020-07-14T23:59:59.000-04:00group.1_daterange.lowerBound=2020-07-13T00:00:00.000-04:00group.p.limit=-1

Despite the SAML configuration you still can log as a local user to CRXDe. For that you can possibly use someting like:curl -sv -X POST -u "admin:*******" -b <COOKIE FILE> --data "j_username=admin" --data "j_password=********" --data "j_workspace=crx.default" --data "j_validate=true" --data "_charse...

How did you configure a replication agent? Do you use an admin as a  user on a Transportation Tab of a replication agent configuration?If it's not an admin, make sure that the user has sufficient ACL for that page location on publish.Do you have any non cq:Page or dam:Asset type of nodes within the ...

I think it means that you should not overlay wcm clientlibs, which might cause some unexpected effect on OOTB UI, but specify cq.common.wcm within your custom libs as dependencies.

Your current execution includes a path D:/AEM-Jar/author/aem-author-4502.jarCan you switch to D:/AEM-Jar/author/ and run the execution command from that path? 

"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/...