Cisco Bug: CSCvt05408 - J4W: authenticateError should not be reset upon receipt of other error code.[enableadlockprevention]
Jun 17, 2020
- Cisco Jabber for Windows
Known Affected Releases
Symptom: As per the defect, CSCvp98042 fix, the solution could cover the below cases when the key authenticateError in Credential is cached. Jabber will not send any requests if Jabber got 401 error. Jabber will not send any requests while do network switch (OnPrem to Edge) if Jabber got 401 error before. However, in some cases, after authenticateError is set to true, if Jabber gets any other error code , for example- unresolved host error, 503 unavailable, then authenticateError is set to false , and Jabber starts sending requests again, locking the credentials in Active Directory, though EnableADLockPrevention parameter is set to true. This shouldn't happen. Conditions: <enableADlockprevention>true</enableadlockprevention> User changes password, and dont update in accounts tab ( settings--> options). Phone services fail to connect, however, Jabber keep sending requests though it receives a 401 and suthenticateError is set to true.Eventually AD credentials get locked.
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)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases