Staff user incorrectly blocked for too many failed login attempts
- Article Type: General
- Product: Aleph
- Product Version: 20
Problem Symptoms:
With $alephe_tab/tab100/PASSWORD-FAIL-BLOCK=Y, users receive the message their account is blocked even though they have *not* had the three failed attempts which the tab100 header says are necessary to trigger this.
Cause:
Uncertain.
Resolution:
When the block occurs, the System Librarian has to unblock the account:
--> Staff Privileges
--> Modify User
--> Uncheck "Blocked" and blank out Blocked Reason.
Additional Information
When such a report is received,
1. do this SQL:
> s+ $pw_library
SQL> select Z66_NO_FAIL from z66 where z66_rec_key like 'xxxxxxxx%';
z66_no_fail should show "3" (or higher?).
2. perform the following grep to see how many entries the user has in the pc_server log:
grep -c XXXXX pc_server_nnnn.log <where XXXXX is the username>
* This site chose to set PASSWORD-FAIL-BLOCK=N since they had had so many (incorrectly) blocked accounts.
Category: Staff privileges (500)
- Article last edited: 10/8/2013