Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >

KB-1075: How to monitor local account login failures using pam_tally

Auditing and Monitoring Service ,   Authentication Service ,   Mac & PC Management Service ,  

12 April,16 at 11:45 AM

Applies to:  All versions of Centrify DirectControl


How to monitor local account login failures using pam_tally on a server with Centrify agent installed?


The latest releases of Linux PAM includes a module called pam_tally which rejects a user if the user failed to login too many times. Although this functionality is not coordinated with Windows domain policy settings, the use of pam_tally may add value for local account logins.

If the requirement is to monitor local account login failures then place pam_tally after the Centrify lines:
auth       sufficient
auth       requisite deny
account    sufficient
account    requisite deny
session    required homedir
password   sufficient try_first_pass
password   requisite deny
auth       required /lib/security/$ISA/ per_user deny=3 onerr-fail
account    required /lib/security/$ISA/

Placing pam_tally auth and account after the Centrify lines means that an AD user login failure will not be recorded.  Only a local user who falls through all Centrify checking will come to this pam_tally logic.