Closed User Group Registration Users on Publishers

[SupportMember]

So even if I were to allow registration into the AEM publishers, how would we reverse replicate these users into all other publishers and have it synced. How about sticky sessions, does AEMaaCS handle this?

[EstebanBustamante]

Hi,

I don't believe there's a good solution for this use case. Reverse replication doesn't exist in AEMaaCS, and even Sling distribution isn't recommended (I don't think this would work either). I think the best approach would be to create the UGC directly on the author instance and then replicate it back to the publishers. Please check these threads for more information:

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/substitute-for-reverse-rep...

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-as-a-cloud-service-alt...

Hope this helps

[SupportMember]

But dealing with AEM customer login from the dispatcher, what are some best practices to achieve this? 

[SupportMember]

Yeah because we are not trying to server user generated content UGC, but actually we want to use AEM's out of the box features, Closed User Group to server content for logged in users only... but we can't just simply store these user nodes inside of the AEM publishers because we got 1 million users. 

[Albin_Issac]

The user sync between publisher pods is handled out-of-the-box (OOTB) in AEM as a Cloud Service, but this configuration is not enabled by default. Please raise a support ticket to enable the user sync between publish pods.

Regards,
Albin

https://myprofile.albinsblog.com

[SupportMember]

Hi, can you please help us understand what this means? Because we can definitely ask Adobe.com the experts but isn't this a problem that many AEMaaCS experts coming up against?

[arunpatidar]

Hi @SupportMember 

Caching : If CUG/protected content is not cached, you might have performance issues, to avoid this , you can use Permission Sensitive Caching 

Sticky Session: we are using sticky session at load balancer, so that for a session, user always served from 1 of the publishers

In our last project we did not had the sticky session, and we had to performed silent login if user lands on another publishers, we leverage Encapsulated Token 

[kautuk_sahni]

@SupportMember Did you find the suggestions from users helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!