Edit Failed Login Rule

How to get here

This page is used to edit a failed login rule.

• Name. Enter a name for this rule. This name is for your reference only and can include up to 256 characters.
• Failed login limit. Specify the number of failed login attempts you want to allow before this rule is triggered.
• Users/Groups. This list contains all of the users and groups configured on the host. Select the checkboxes next to the users and groups to whom you want this rule to apply.
• Rule Notifications. This section is used to select one or more notifications to send and to specify the criteria that trigger the notifications for this rule. Notifications can be triggered when any of the following actions succeed or fail: failed attempts exceed allowed attempts, expired account, invalid user, password expired.
• Send notifications when rule is triggered as a result of:
  • Failed attempts exceeding allowed attempts. Select this option to send notifications hen a user fails to log in more times than is allowed.
  • Expired account. Select this option to send notifications when a user attempts to log in with an account that has expired.
  • Invalid user. Select this option to send notifications when someone attempts to log in using an incorrect user name.
  • Password expired. Select this option to send notifications when someone attempts to log in using a user account with an expired password.
• Notification. This list contains all of the notifications configured on the current host. Select the checkboxes beside the notifications you want to associate with this rule. To configure a new notification and associate it with this rule, click Create.
• Executable (optional). Enter the full path and file name of the program you want to run on the server when this rule is triggered.
• Arguments (optional). Enter the arguments to pass to the executable, if necessary.

  Tip: You can specify message notification variables as arguments to pass to the executable.

• Note: Executables are separate programs that WS_FTP Server runs for you under certain conditions. Depending on the volume of traffic on your server and the number of times an executable is run, these programs may consume considerable resources and may cause performance issues.