AEM communites implementation

Hi Pr@veen,

I tried to reproduce what you should have done.  The fact that you see the profile on author leads me to think the user is only registered on author, not on publish.  If so, that would explain why you don't see the profile on publish

Perhaps you had some mis-steps?  The tutorial was not easy to follow?

This is what I did :

1) created two copies of AEM 6.1 quickstart as cq-author-p6102.jar and cq-publish-p6103.jar, placing them into separate folders alongside the license.properties file

2) started both author/publish servers

3) installed SP1 and FP3 on both author/publish servers using http://localhost:6102/crx/packmgr (and 6103)

4) on author 

   a) edited default agent for publish so that the transport URI was localhost:6103, not 4503 (tools > operations > replication)

   b) enabled tunnel service  (http://localhost:6102/system/console/configMgr)

   c) created community site on author, using defaults except selected Reference Site and Yeti design, and published

5) on publish

   a) browsed to new community site

   b) registered as new user

   c) signed in as new user

I DO see the new user's profile.

6) on author

   a) try to sign in as new user

FAIL - because new user does not exist on author.

For the sign-in feature, the tunnel service is not used to access users registered in the publish environment - that would be a major security violation.

The tunnel service is used at approprite times from community consoles to assign community members to various community roles, like group manager, privileged member, or as a learner for an enablement community.

If there is something about the getting-started tutorial that was not helpful, please let me know.

Please, let me know if you're able to reproduce it, and if so, what you did step-by-step.

- JK