Wrong PPSK entry now locks a user for 1 hour immediately (19.5.1.7-NGVA)

[carsten_buchena]

Since the upgrade to 19.5.1.7-NGVA, we noticed that users who enter a wrong PPSK (type SERVICE) are being locked for 1 hour immediately. Previously, they had a few tries before being locked.

Is this a new/expected behaviour? Is there a way to change it?

Thanks,

carsten

[dparsons]

If I had to throw a wild guess at it I would say that the client may be trying multiple times and causing the lock out. I would watch it in client monitor as well. You could also try it on a different platform and see if the behavior is the same.

[carsten_buchena]

Thanks Sam! I will do that and let you know / update this thread.

[samantha_lynn]

Hi Carsten, I tested in our lab (also on 19.5.1.7) and we had to enter an incorrect password 5 times before it locked us out. I would recommend opening a case so our engineers can do a root cause analysis with you to see why the user lock down is triggering early.