Celestix MSA 4200 Series Installation Guide Page 34

  • Download
  • Add to my manuals
  • Print
  • Page
    / 101
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 33
Celestix HOTPin Appliance Installation Guide Page | 30
General Tab
The general system settings provide configuration options for user-related
functionality.
Authentication
Note: For both Authentication items, a lower value offers higher security, a
higher value offers more flexibility.
Maximum Authentication Failures determines the number of login
failures before a user is locked out of the system (each successful
authentication resets the authentication failure counter). Once locked
out of the system, the user will need to be unlocked by a system
administrator (HOTPin|Users).
Note: It will be helpful to your users if you consider how long it will
take them to log in when you set the maximum authentication
failure feature in HOTPin. This is also true for timeout settings
if you combine HOTPin with other authentication options.
While these values should only be set as long or high as is
necessary, consider that shorter duration timeout
values/fewer login attempts may lead to system lockouts on
legitimate users, especially for the first-time login where users
may require two token codes to complete the process.
OTP look ahead valuecreates a window of valid token codes that
can be used for authentication.
Token Provider
Sent Code TTL – determines how long a token code will be valid when
sent by a custom provider.
Send command string – requests a token code from the HOTPin server
when entered in the login page password field. If a PIN is required, the
user combines the PIN and send command string separated by a
comma (PIN,send). The command string is not case sensitive. A
maximum of 32 characters can be used. The default value is send.
Important: Changing the string to a customized value from the default
is recommended.
Increment authentication failures when code is sent – limits the
number of times a user can be sent a token code before successful
authentication must occur. When enabled, the user's login
authentication failure counter is incremented each time a provider sends
a token code; the user will be locked out of the system if they exceed
the maximum limit as defined in the Settings : Authentication : Maximum
Authentication Failures field. The counter is reset after successful
authentication.
Send ahead the next OTPprovides the next valid token to end users.
The provider will send another token code when a user successfully
authenticates. The advance code is held in case users can’t receive
Page view 33
1 2 ... 29 30 31 32 33 34 35 36 37 38 39 ... 100 101

Comments to this Manuals

No comments