Developer

Handling Previous User Transactions

Set up security to handle previous user transactions.

You can configure the Agentry Client to cache the user's encrypted password in the encrypted client database on the local device, and use it to complete user transactions following an interruption.

Examples of interruption include:
  • The user changes the back-end password, and then logs into the Agentry Client with the new password.

  • The user selects the Change Password sequence to change the password.

  • The server forces the Change Password sequence with a "Password Expired" response to the user validation back-end step.

  • Another user initiates the Change User sequence. Note that user ID and password should not be updated until the previous user login, previous user transactions, and new user relogin sequence completes successfully.

Setting up security to handle previous user transactions

To enable this feature:
  1. In Agentry Editor, navigate to the Application Definition, and enable the configuration option "Device Sharing: Support sending transactions on user change" (located in the Application Security Attributes tab, under Client Database Encryption). This enables the client's password to be saved locally.

  2. Check the Application Definition configuration option "Client Database will be encrypted" (located in the Application Security Attributes tab, under User Settings).
    • If checked, Agentry Client saves the encrypted user password in the encrypted client database.

    • If unchecked, the encrypted password is not stored in the local database, and Agentry Client sends an empty string during a Previous User Login message.