Hello,
I am writing to you because I notice that the Cisco Jabber application is not ...
My problem is the following:
The user is using cisco jabber on his workstation. By it happens that this has to connect on a new station and so connect to Jabber.
The user forgets that he has 2 sessions open on 2 workstations simultaneously.
one day his password will change... and thus create a massive batch of authentication failures and make my AD audit console more unusable because Jabber looks like a brute force even though the account gets locked after 8 attempts.
do you have a solution to fix this?
Personally a programmer should revise the code on the number of failed attempts from infinite to 3.. like for example filezilla.
do you think the SSO can correct this situation?
Translated with www.DeepL.com/Translator (free version)
