Maximum allowed users in publish | Community
Skip to main content
V
vb11
New Participant
June 14, 2023
Solved

Maximum allowed users in publish

  • June 14, 2023
  • 2 replies
  • 1025 views

Hi There,

 

We have an on-prem AEM customer who likes to use the AEM Communities add-on to move one of their existing communities site (as part of consolidating all their web experience on AEM ). So, the community site has about 1 million users in the database which got us a bit concerned as the users will have to be created on JCR and ofcourse the UGC will be stored externally on mongo/mysql. As per another thread it seems that technically there are no limits (also seen this thread - https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/maximum-number-of-users-in-aem/m-p/216170), but just wanted to see if there are any best practices/recommendations to follow and are there any known issues?

Note: the authentication itself will happen on 3rd-party (AWS incognito).

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 Saravanan_Dharmaraj

@vb11 The biggest issue we faced with authenticated users are stored in JCR is "syncing user and group" issues between publish instance. We felt SCD(Sling Content Distribution) which sync the user profile updates or new user node generated in one of the publish instance to other publish instances through Author is buggy. The distribution queue got stuck and filled with unfinished jobs in Author. So you will end up seeing new user's post in community forum coming as "Unknown" user in other publish instances since that publish instance didn't get synced with this new user. We have around 400K users(B2B). SCD set up is cumbersome and painful to troubleshoot every time we hit the user related issues.

https://experienceleague.adobe.com/docs/experience-manager-65/administering/security/sync.html?lang=en 

 

On the side note, its interesting to see client moving to AEM communities now considering Adobe is not planning to upgrade AEM communities or put more effort to improve. Just the support. So we moved out of AEM communities for the same reason. 🙂 

 

Having Mongo as SRP will be good and hope you can have control and admin privilege for this to see how the UGC are stored and troubleshoot. We had ASRP and it was total black box , you can only use SRP browser and it was buggy too. 

 

Those are my inputs, hope it helps. 🙂 

 

 

 

 

2 replies

Saravanan_Dharmaraj
Saravanan_DharmarajAccepted solution
New Participant
June 14, 2023

@vb11 The biggest issue we faced with authenticated users are stored in JCR is "syncing user and group" issues between publish instance. We felt SCD(Sling Content Distribution) which sync the user profile updates or new user node generated in one of the publish instance to other publish instances through Author is buggy. The distribution queue got stuck and filled with unfinished jobs in Author. So you will end up seeing new user's post in community forum coming as "Unknown" user in other publish instances since that publish instance didn't get synced with this new user. We have around 400K users(B2B). SCD set up is cumbersome and painful to troubleshoot every time we hit the user related issues.

https://experienceleague.adobe.com/docs/experience-manager-65/administering/security/sync.html?lang=en 

 

On the side note, its interesting to see client moving to AEM communities now considering Adobe is not planning to upgrade AEM communities or put more effort to improve. Just the support. So we moved out of AEM communities for the same reason. 🙂 

 

Having Mongo as SRP will be good and hope you can have control and admin privilege for this to see how the UGC are stored and troubleshoot. We had ASRP and it was total black box , you can only use SRP browser and it was buggy too. 

 

Those are my inputs, hope it helps. 🙂 

 

 

 

 

    MayurSatav
    MayurSatav
    New Participant
    June 14, 2023

    Hi @vb11 ,

     

    There are some best practices and recommendations to consider:

    1.Since you already have a large user database, it's important to plan and execute the user migration process carefully. You can leverage AEM's user synchronization capabilities or develop a custom solution to import the users into AEM's JCR repository. Ensure that user attributes and authentication mechanisms are properly mapped and integrated with the third-party authentication provider (AWS Cognito).

    2. With a large user base, it's crucial to design your AEM infrastructure for scalability and performance. Consider using a distributed setup, load balancing, and proper caching mechanisms to handle the increased load. Optimize your AEM instance configuration and monitor system resources to ensure smooth performance.

    3. Assess the user groups and roles in your existing community site and map them to AEM's user groups and permission models. Define appropriate access controls and permissions to manage user access and content moderation within the AEM Communities environment.

    4. As you mentioned, storing user-generated content (UGC) externally on a separate database (e.g., MongoDB or MySQL) is a recommended approach. This helps in offloading the storage requirements from the JCR repository and improves performance and scalability.

    5. Ensure seamless integration between AEM and AWS Cognito for authentication. Implement proper user synchronization and session management to maintain user authentication and authorization across the platforms.

    It's also advisable to engage with Adobe Support or Consulting Services to discuss your specific requirements, perform a thorough architecture review, and get guidance on any potential known issues or specific recommendations for your migration scenario. They can provide further insights based on their expertise and experience with similar implementations.

      Terms & ConditionsAccessibility statement

      Loading footer...