Were you able to resolve this?I'm facing this when copying the truststore between instances. I'm following the procedure in Managing Subscriptions  which I expected to fix this problem.I've found the solution to this, see Security Checklist -> "Replicating Keys for AEM 6.3"

Have a look at SAML 2.0 Authentication Handler There's a section about creating a saml logger. Debug entries should tell what's wrong.

Yes, but it's definitely not that case. I've checked with the authors and also I can see the "Refuse to create new version" msg across all the different sites. Even if they created a version of the page before rolling it out, I don't think it would produce this behaviour.

Update: simply excluding the anonymous user seems to have fixed the problem. It's a dynamic path though.

> Did this issue start happening or always been happening?I really don't know, since I just started investigating this and our logs don't go too far back. But there have been some reports of missing versions in the past, so I assume it has happened before. Seems rather infrequent though.> typically ...

Hi,I've a few pages that have been rolled out using MSM and then manually activated/published. The problem is that some of them don't have any versions created on publication.Looking at a page with versions I see:{"jcr:primaryType": "cq:Page","jcr:createdBy": "...","jcr:created": "Tue Aug 15 2017 22...

Yeah, that's a good idea. For other people's reference it's ticket 1435759.

As suggested I've posted it in http://mail-archives.apache.org/mod_mbox/jackrabbit-users/201708.mbox/%3CSYXPR01MB0879C47F31087A00D98726BF94B00%40SYXPR01MB0879.ausprd01.prod.outlook.com%3E​

Hi,java  -jar ${UPGRADE_JAR} --mmap --copy-versions=false --copy-orphaned-versions=false --include-paths=/content,/etc/tags,/home,/var/<removed>/widgets,/jcr:system/rep:namespaces,/jcr:system/rep:permissionStore,/etc/workflow/instances,/var/eventing/scheduled-jobs,/var/eventing/distribution --merge-...

Hi,We're using crx2oak to do blue-green deployments. As a baseline I'm trying the parameter --copy-versions=false to see how much time/space can by gained by excluding versions. However when doing this, in the migrated repository on startup, I consistently get this error:31.07.2017 13:21:12.855 *ERR...