Expand my Community achievements bar.

Replication of facebook oath failed

Avatar

Level 2

Hi all, 

we upgraded author and publish from CQ 5,6,1 to AEM 6.2. We have facebook oauth functionality on our site.

But when user register himself via facebook and then his data is activated back to author we got error:

 *ERROR* [172.30.1.102 [1488554579240] POST /bin/receive HTTP/1.1] com.day.cq.replication.impl.servlets.ReplicationServlet Error during replication: Repository error during node import: No matching node definition found for oauth
com.day.cq.replication.ReplicationException: Repository error during node import: No matching node definition found for oauth
        at com.day.cq.replication.impl.content.durbo.DurboImporter.createNode(DurboImporter.java:312)
        at com.day.cq.replication.impl.content.durbo.DurboImporter.createNode(DurboImporter.java:214)
        at com.day.cq.replication.impl.ReplicationReceiverImpl.receive(ReplicationReceiverImpl.java:183)

..............

Caused by: javax.jcr.nodetype.ConstraintViolationException: No matching node definition found for oauth
        at org.apache.jackrabbit.oak.plugins.nodetype.EffectiveNodeType.getNodeDefinition(EffectiveNodeType.java:395)
        at org.apache.jackrabbit.oak.plugins.nodetype.ReadOnlyNodeTypeManager.getDefinition(ReadOnlyNodeTypeManager.java:395)
        at org.apache.jackrabbit.oak.jcr.xml.ImporterImpl.getDefinition(ImporterImpl.java:550)
        at org.apache.jackrabbit.oak.jcr.xml.ImporterImpl.endNode(ImporterImpl.java:485)
        at org.apache.jackrabbit.oak.jcr.xml.SysViewImportHandler.processNode(SysViewImportHandler.java:88)
        at org.apache.jackrabbit.oak.jcr.xml.SysViewImportHandler.endElement(SysViewImportHandler.java:220)
        at org.apache.jackrabbit.oak.jcr.xml.ImportHandler.endElement(ImportHandler.java:197)

 

This blocks replication queue a lot.
What should I do to get rid of this problem?

2 Replies

Avatar

Level 9

You may need to update your social-login configuration (OSGi configs).  It was updated to work with the latest Facebook api.

Please visit the current documentation for 6.2 : Social Login with Facebook and Twitter.

- JK

Avatar

Level 2

We found out that the problem was not in oath node. It was just first nt:unstructured node after rep:Cache in xml

So, reason was in new rep:Cache node. See http://jackrabbit.apache.org/oak/docs/security/principal/cache.html This functionality was enabled and these nodes were created automatically for users. But during replication user node (for facebook users only that is still strange) it was some problem with creation rep:Cache node on target instance. 

Unfortunately we did not find why we have this problem and why rep:Cache is not excluded for facebook users during replication.

But solution for us was to disable caching functionality via org.apache.jackrabbit.oak.security.user.UserConfigurationImpl  and remove via script all already created rep:Cache nodes