Failed to create comment...posted a comment with suspicious userIdentifier | Community
Skip to main content
A
Anonymous
October 16, 2015
Solved

Failed to create comment...posted a comment with suspicious userIdentifier

  • October 16, 2015
  • 5 replies
  • 1898 views

How do I configure the logic/rules for posting comments? Currently, we are using a custom authentication system but when a user attempts to create a comment, a CommentException is thrown saying the user has a suspicious identifier.

Also, I couldn't seem to find any straightforward documentation on how comments are "processed" and replicated from Author to Publish (and vise-versa) instance. Could you point me to some documentation or resource on how the lifecycle of comments work within AEM?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by

I was able to resolve this issue base on the answer here: http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manager.topic.html/forum__hlpe-newly_createdcommen.html. It appears that I need to be using the admin Social Communities functionality to delete comments. This is a bit confusing though since the author instance allows deleting comments for individual blog posts, however, those changes don't propagate to the publish instances.

5 replies

JK_Kendall
JK_Kendall
Level 9
October 16, 2015

Let's start with the CQ/AEM version you are using.  If it is CQ 5.6.1, the next question is whether you upgraded to cq-socialcommunities-pkg-1.4 or not.

- JK

A
Anonymous
October 16, 2015

We are currently using cq-socialcommunities-pkg-1.3.12.

JK_Kendall
JK_Kendall
Level 9
October 16, 2015

v1.3 shipped in CQ 5.6.1.

You could be using either /libs/collab/commons/components/comments (deprecated in 5.6.1) or /libs/social/commons/components/comments

A stack trace, if not a log of signing in and posting a comment, would also be of help.  Could it be that the Comments code caught an exception from your custom authentication code and rethrew it?

If you look at /libs/social/commons/components/comments/comments.jsp, it appears the exception would happen somewhere around here :

<%
    if (!cs.isClosed() && CollabUtil.canAddNode(resourceResolver.adaptTo(Session.class), cs.getRootPath())) {
    %><sling:include resourceType="social/commons/components/composer" replaceSelectors="simple-template"/><%
    }
    if(!CollabUtil.canAddNode(resourceResolver.adaptTo(Session.class), cs.getRootPath())) {
        %><p><%=i18n.get("You are not allowed to post here, please sign in or join")%></p>

 

The answer to replication of "comments" (UGC)  is complicated.  It depends on your deployment, but prior to AEM Communities 6.1, UGC is first reverse replicated to the author instance and then forward replicated to any other publish instances.  It can be tricky to keep all UGC appropriately synchronized.

As of AEM 6.1 (v1.7), there is a common store for UGC that is visible to all author and publish instances.  Replication is no longer used for UGC.

 

If there are any plans to move forward to a more recent release, then consideration should be given to at least upgrading now to the v1.4 socialcommunities package that's built for CQ 5.6.1.

- JK

JK_Kendall
JK_Kendall
Level 9
October 16, 2015

Hi Vincent,

Did this get resolved?

I meant to provide a link to the v1.4 package :

http://docs.adobe.com/docs/en/aem/6-0/develop/social-communities.html#Social%20Communities%20Version%201.4

- JK

A
Anonymous
Accepted solution
October 16, 2015

I was able to resolve this issue base on the answer here: http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manager.topic.html/forum__hlpe-newly_createdcommen.html. It appears that I need to be using the admin Social Communities functionality to delete comments. This is a bit confusing though since the author instance allows deleting comments for individual blog posts, however, those changes don't propagate to the publish instances.

Terms & ConditionsAccessibility statement

Loading footer...