Add config for User Synchronization | Community
Skip to main content
February 10, 2019
Solved

Add config for User Synchronization

  • February 10, 2019
  • 7 replies
  • 4524 views

Hi All,

I am trying to configure the user synchronization in my application by using the config files in apps.

This is the config PID org.apache.sling.distribution.agent.impl.SyncDistributionAgentFactory.84634fbb-92e9-47b3-8aa4-4ef21ce62504 from configMgr, but the id is diffrent in each environment.

When I am trying to add config, it's creating a new configuration, but I have to override this existing one.  How to add the config to override the existing config in all environments.

Following steps from this Article: User Synchronization

Using the AEM6.4 Version.

Please help me to resolve this issue.

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 Gaurav-Behl

Why would publish servers have "existing configs"?

If there are any pre-existing configs, then you could delete them (after thorough vetting that you don't break anything) either manually, or simply create a replica in author and then deactivate.

7 replies

smacdonald2008
February 10, 2019

In the above doc topic - there is a troubleshooting section. Did you use the User Sync Diagnostics tool to see if there any problems.

Gaurav-Behl
February 10, 2019

Could you share more details regarding "When I am trying to add config, it's creating a new configuration, but I have to override this existing one.  How to add the config to override the existing config in all environments."

Have you created the config under /apps/system or /apps/<project>/config.author and config.publish?

February 11, 2019

Thank you smacdonald2008 and @gauravb41175071 for the reply.

I have created the config folders under /apps/system like

It is created a new config for Adobe Granite Distribution - Diff Observer Factory ., But we have to override the existing one.

No errors in the user sync diagnostics.

edubey
February 11, 2019

Can you delete the existing configs under /apps/system or /apps/<project>/config.author and config.publish?

and then package those configs from lower environment?

February 11, 2019

Do we need to manually delete the existing config from all publish servers or there is any way to do it

Gaurav-Behl
Gaurav-BehlAccepted solution
February 11, 2019

Why would publish servers have "existing configs"?

If there are any pre-existing configs, then you could delete them (after thorough vetting that you don't break anything) either manually, or simply create a replica in author and then deactivate.

February 11, 2019

Thanks @gauravb4115071,

It's working after deleting the existing config.