AEM communites implementation

[praveenk9004043]

Hi Friends

I am using the below url for AEM communities implementation.

https://docs.adobe.com/docs/en/aem/6-1/administer/communities/getting-started/published-site.html

In the publish environment one the user does the self registration and logs in to the communities

when he click on the profile page I am able to see the Profile blank page. But in the author environment for Admin I am able to see the Profile page

Can someone help me

Regards

Pr@veen

[Lokesh_Shivalingaiah]

Did you check your logs to see if there are any errors ?

[JK_Kendall]

Hi Pr@veen,

I 'm not reproducing this with a 'clean' install of AEM 6.1 + SP1 + FP3 (communities package v1.8.305.1).

I know you're using AEM 6.1.  

What is the history of this install? 

• do you have SP1 installed?
• which feature packs have you installed for Communities?

Did you follow the getting started tutorial exactly?  If multiple FPs were installed, under which FP was the community site created?

- JK

[praveenk9004043]

Friends,

i am using SP-AEM-6.1-Service-Pack-1-6.1.SP1 abd communities feature pack AEM-6.1-Communities-Feature-Pack-3-1.8.305.1.zip.

I do not see any errors in the log file.

Regards

Pr@veen

[JK_Kendall]

A little more history -

is this a 'clean install' of AEM 6.1 + SP1 + FP3 (1.8.305.1) ?

did you choose an SRP other than JSRP? 

If you look at the network traffic, you should see a request like

http://localhost:4503/content/sites/engage/en/profile.html/home/users/community/{userId}/profile

If you follow the tutorial a second time to create a new site (takes less than a minute), publish it, register as a new user, and login with the new registration, can you reproduce it?  

We need a way to reproduce the issue.

- JK

[praveenk9004043]

we are not using any SRP for SP installation.

Regards

Pr@veen

[JK_Kendall]

praveenk9004043 wrote...

we are not using any SRP for SP installation.

Regards

Pr@veen

Which means you are using the default JSRP.  

The Storage Resource Provider (SRP) is how user generated content (UGC), also referred to as community content, is stored and accessed.

You can read more about it on the Community Content Storage page.  It describes the characteristics of the SRP options.

- JK

[JK_Kendall · Accepted solution]

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