Guest

Preview Tool

Cisco Bug: CSCus42665 - Change in samAccountName in AD breaks LDAP sync for that user

Last Modified

Oct 09, 2018

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

10.5(1.11011.1) 10.5(1.11900.10) 10.5(1.11900.13) 10.5(1.11901.1) 10.5(2.10000.5)

Description (partial)

Symptom:
a) The Alias integrated with LDAP directory (whose samAccountName was changed in AD) is marked as Inactive on Unity Connection. The status on User Basics page will show message as: "User has been deleted from the LDAP Directory".

b) The updated samAccountName/alias will be available to import under LDAP Import page.

Conditions:
a) User is Integrated with LDAP Directory
b) Alias/UserId is mapped with samAccountName.
b) samAccountName is changed in AD.
c) Full DirSync is performed to fetch the changes from AD.

Related Community Discussions

Dealing with userid change in an ldap sync scenario
Hi I'm struggling trying to find a workable solution for this: I have a CUCM and CUCN both with active LDAP sync. The user's samAccountname changes (due to a name change). On CUCM, after the ldap sync has run, everything is in order.. the synched enduser has been updated. On CUCN, after the LDAP sync, I have a local user with a warning. Now, I need to restore this programmatically without breaking the box. Any ideas? And scenario 2: Same story as above but I get to the box before the ldap sync has ...
Latest activity: Apr 03, 2015
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.