Can you try to remove the overlay under apps by creating a package? Also, try to check if you see the same issue for asset folders with 1/2 assets.

Usually, this error is observed when the service user mapping is missing to the pre-upgrade bundle. Can you add the mapping as per below and check if you still get the same issue?Go to the Web Console at http://serverhost:serveraddress/system/console/configMgrSearch for Apache Sling Service User Map...

I just tested and do not see the same issue on 6.5.2 instance. Can you log a daycare ticket with steps to reproduce the issue on we-retail content and we can further debug the issue.

For 6.5, uber jar version is 6.5.0.0 with an extra 0 at the end. So, make sure the dependency is correct.

First step will be to check if you are using the correct version of user-jar. Ex: for AEM 6.4.5, you need to use uber jar version 6.4.5

I believe this is working as designed. In case you would like to make it more secure, you can turn on the encryption and have the encrypted response saved in AEM so that it can only be decoded using the private key.

You can try to define a custom logging writer and define the messages as per your requirement. Check [1] for more details.[1] https://helpx.adobe.com/experience-manager/6-3/sites/deploying/using/monitoring-and-maintaining.html#CreateaCustomLogFile

You can use the "Synchronized Attributes" in the SAML handler to configure the attributes that should be synced/stored with AEM.

You might want to check services if AEM is started as a windows service. Check [1] for more details.[1] https://aemexperts.blogspot.com/2019/03/installing-and-starting-adobe.html

As per my understanding, maven is not deploying the latest changes to the AEM instance when deploying manually. Try to change the log level for maven to verbose and check through the various stages of build/compile.