Expand my Community achievements bar.

SOLVED

How to prevent the duplicate user creation in CRX during the pub1 & Pub2 sync?

Avatar

Level 1

We are getting two response call from third-party application, so two response call creating users in both PUB1 & PUB2.
(As of now we can't stop the two response call from third-party application).

Is there any way to remove/merge the duplicate users while synchronizing PUB1 & PUB2

Kind regards,

Balaji k

1 Accepted Solution

Avatar

Correct answer by
Employee

Hi Balaji,

SCD was never meant to handle this use case, and as you have already alluded to, you are trying to fix/hack something that is caused by incorrect use of the system, i.e. multiple user creation calls on both publish instances. Other than trying to extend SCD[0] I think you  should try and see if you can somehow fix the source system sending these duplicate user creation requests.

Regards,

Opkar

[0]https://github.com/apache/sling/blob/trunk/contrib/extensions/distribution/README.md

View solution in original post

4 Replies

Avatar

Employee

Hi Balaji,

what version of AEM is this? When you say synchronising PUB1 & PUB2, how is this synchronisation happening?

Regards,

Opkar

Avatar

Level 1

Hi Opkar,

Thank you for your response.

We are using AEM 6.1 and we are using SCD(sling content distribution) for synchronization.

Kind regards,

Balaji K

Avatar

Correct answer by
Employee

Hi Balaji,

SCD was never meant to handle this use case, and as you have already alluded to, you are trying to fix/hack something that is caused by incorrect use of the system, i.e. multiple user creation calls on both publish instances. Other than trying to extend SCD[0] I think you  should try and see if you can somehow fix the source system sending these duplicate user creation requests.

Regards,

Opkar

[0]https://github.com/apache/sling/blob/trunk/contrib/extensions/distribution/README.md

Avatar

Level 1

Hi Opkar,

Thank you for your response.

We ill try to fix this issue in code level from third party source.

Kind regards,

balaji k