This procedure describes how to configure the user lockout behavior on the mobile application, which occurs after the defined number of failed login attempts by the mobile user. A part of this configuration is the resulting behavior, as set by the “lockout level”, when a user is to be locked out.
These settings should be configured to match the security requirements of the implementation environment. Possible lockout behaviors range from simply requiring the user to perform a successful login and full transmit with the Agentry Server before being allowed to proceed; removing all module-level production data (including object instances and pending transactions) and requiring a full login and transmit; or completely resetting the Agentry Client executable, removing all data stored by the application, and requiring a full transmit and synchronization before being allowed access to the application.
Defining this behavior requires the modification of the Application Security attributes found in the Application definition, followed by publishing the changes to the Agentry Server, with a subsequent transmit by each Agentry Client to update the mobile application with the new settings.
The desired lockout behavior for mobile users reaching the maximum number of failed login attempts has been defined. The behavior will be exhibited on the Agentry Client for mobile users in the production environment once published or deployed to that environment.