Account locked out after 3 wrong passwords
Posted: Mon Oct 01, 2012 1:59 pm
Hello,
We are running version 4.0.1.700 of Clarity. We have set for accounts to be locked out if password is entered incorrectly 3 times. This works, but it appears that Clarity takes into account the number of incorrect passwords entered 'per session' rather than 3 incorrect entries consectutively. So the result is that if a user enters their password incorrectly, then correctly enters their password, Clarity remembers and still counts this as 1 incorrect entry. If the same user then does this later in the day they end up locking themselves out even though they have only entered it incorrectly once (because they have done it wrong more than 3 times total in that session). The count should be reset after entering the correct password.
This causes problem if a sequence is running as the software cannot be restarted. There is also no way for an administrator to re-activate the account without closing the instrument.
Is this by design or a bug in Clarity? I dont know of any other commerically available software that behaves this way.
Thanks,
We are running version 4.0.1.700 of Clarity. We have set for accounts to be locked out if password is entered incorrectly 3 times. This works, but it appears that Clarity takes into account the number of incorrect passwords entered 'per session' rather than 3 incorrect entries consectutively. So the result is that if a user enters their password incorrectly, then correctly enters their password, Clarity remembers and still counts this as 1 incorrect entry. If the same user then does this later in the day they end up locking themselves out even though they have only entered it incorrectly once (because they have done it wrong more than 3 times total in that session). The count should be reset after entering the correct password.
This causes problem if a sequence is running as the software cannot be restarted. There is also no way for an administrator to re-activate the account without closing the instrument.
Is this by design or a bug in Clarity? I dont know of any other commerically available software that behaves this way.
Thanks,