We've got a running, implemented setup of Finesse and regularly we have the issue where users will change their LDAP passwords and then they can't get back into Finesse for up to an hour.
Does anyone know the scenario's that cause this beyond them being logged into Finesse when they change it in Windows?
I'd like to be able to communicate a process so they don't run into walls with scissors... Given the design of LDAP, nothing is being saved "on" CUCM/UCCX/Finesse (or it shouldn't be for any extended period of time) and I'm confused how someone changes a password and when a net new login attempt occurs it doesn't internally refresh the instance and just kick out the old one. Performing a full sync doesn't help on it either.
Sorry, to note, this is on: 184.108.40.20600-18 for CUCM 220.127.116.1101-34 for UCCX
This is probably caused by AD site replication timers. If the domain controller CUCM is sending Authentication bind requests to does not yet know the new password, the login attempt to Finesse/Jabber/CCM user webpage/etc. will fail. You could prove this with a packet capture from the CUCM publisher assuming you have TLS off on LDAP Auth - you should see the password being sent (in the clear!!) and the domain controller’s response.
This document is intended to receive any new ideas for TAC to create new useful walkthrough videos to help set up deployments, integrations, etc.
Feel free to share any feedback about new walkthrough videos you consider useful, please share your o...
Configuring Cloud Connected PSTN (CCP) – Easy as 1-2-3!
STEP 1: PREPARE
Before you can configure your CCP in Control Hub, you must procure PSTN services from an authorized Webex Calling CCP Partn...
To participate in this event, please use the button to ask your questions
This topic is a chance to discuss more about how to read Cisco Unified Communications trace files. In this session, Cisco D...