Account locked out after 3 wrong passwords

You can discuss anything concerning Clarity in this section.
Post Reply
lewiscrouch
Posts: 3
Joined: Tue Mar 27, 2012 4:06 pm

Account locked out after 3 wrong passwords

Post by lewiscrouch »

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,
Lewis Crouch

User avatar
Daniel Mentlik
DataApex Support
DataApex Support
Posts: 353
Joined: Fri Mar 27, 2009 3:15 pm

Re: Account locked out after 3 wrong passwords

Post by Daniel Mentlik »

Dear Lewis,
this is clearly not intended behavior. Thank you for pointing the issue to our notice, it has been entered under the ISS49852 and will be solved in one of the next updates of Clarity (unfortunately not the one which will be released this week as we are almost done with testing procedure). We will let you know once the issue is solved.
Daniel Mentlí­k
DataApex

User avatar
Ivan Vins
DataApex Support
DataApex Support
Posts: 183
Joined: Fri Mar 27, 2009 3:16 pm

Re: Account locked out after 3 wrong passwords

Post by Ivan Vins »

Dear Lewis,

the reported bug was fixed in the current release 4.0.2.784 available for download from our web site.
Ivan Vinš

Post Reply