Closed User Group Registration Users on Publishers

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-replication-in-aem-as-cloud-service/td-p/448187

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-as-a-cloud-service-alternatives-for-aem-communities/m-p/619656

Hope this helps

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

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 

@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!