Where the existence of such a configuration conflict can be verified?

ARTIFACTORY:How to resolve ‘Duplicate key errors during startup caused by Federated members associated with the Artifactory instance?’
AuthorFullName__c
Yuvarajan Johnpaul
articleNumber
000005347
ft:sourceType
Salesforce
FirstPublishedDate
2022-08-10T07:27:50Z
lastModifiedDate
2023-01-22T11:06:38Z
VersionNumber
5

I have shared a sample configuration snippet highlighting the duplicate entries. 

User-added image

This configuration would be available in the Artifactory’s Config Descriptor (/var/opt/jfrog/artifactory/etc/artifactory/artifactory.config.latest.xml). 

  1. Use the repository reference indicated in the log snippet.
  2. Search for the conflicting entries from the Config Descriptor.
  3. Remove the duplicate snippet and for the changes to be deployed, we need to Bootstrap the configuration file using the instructions defined here. 

Note: A restart of the Artifactory is required for the configuration update to take effect. This issue arises in rare scenarios where automation is involved for provisioning the Artifactory repositories that attempt to send creation requests on a loop/concurrent basis, at a specific point in time.