07-14-2015 12:17 PM - edited 03-13-2019 09:03 PM
Wanted to see if anyone else has hit this bug(CSCuv04411). Upgraded from 10.5.2.10000-5 to 10.5.2.12900-14 and we are hitting this bug after the upgrade. The affected version does not specifically reference the upgraded version, but an ES version(10.5(2)ES31) is referenced as an affected version. Considering rolling back due to the amount of MAC'd(Moves/Adds/Changes) work and do not want to grant additional rights nor want to get involved every time a DN/extension changes. We do not keep this field sync'd with AD since there are other systems which feed that field.
07-14-2015 03:13 PM
Hi,
Seems the bug has not been fixed yet. I checked the details and it says it will be addressed in version 11.5. There is a workaround for it:
1. On the user's page, change the LDAP Integration Status to "Do Not Integrate with LDAP Directory”.
2. After making the change to the Extension, change the LDAP Integration Status back to "Integrate with LDAP Directory”.
I understand why you might want to rollback.
Regards,
Tere.
08-03-2015 09:11 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide