Fixing a modify conflict - PingDirectory

Page created: 15 Jul 2022 |

Page updated: 20 Jan 2023

| 1 min read

9.2 Product PingDirectory Directory Capability Product documentation Content Type Administration User task IT Administrator Administrator Audience Software Deployment Method Troubleshooting IT Operations

To isolate conflicting entries between two replicas, use the bin/ldap-diff tool.

Note:

Replace the sourceHost value with the server that needs the adjustment.

The following example uses the tool to search across the entire base distinguish name (DN) for any difference in user attributes and reports the difference in difference.ldif.

$ bin/ldap-diff --sourceHost austin02.exmple.com --sourcePort 1389 \
                        --sourceBindDN "cn=Directory Manager" --sourceBindPassword pass \
                        --targetHost austin01.example.com --targetPort 1389 \
                        --targetBindDN "cn=Directory Manager" --targetBindPassword
                        --baseDN "dc=example,dc=com" --outputLDIF difference.ldif \
                        --searchFilter "(objectclass=*)" --numPasses 3 "*" pass \
                        "^userPassword"

To apply changes to the server that contains conflicts, use the difference.ldif file in a format compatible with ldapmodify.

Important:

Run ldap-diff command with the sourceHost value as the server with conflicts.

The following is an example of the contents of difference.ldif file.

dn: uid=user.1,ou=people,dc=example,dc=com
                        changetype: modify
                        add: mobile
                        mobile: +1 568 232 6789
                        -
                        delete: mobile
                        mobile: +1 568 591 7372
                        -

To correct the entries on the sole server with conflicts, run bin/ldapmodify.

$ bin/ldapmodify --bindPassword password -J "1.3.6.1.4.1.30221.1.5.2" \
                        --filename difference.ldif