Account data templates define the format of account data to be stored for credentials captured using a specific AccessProfile. The account data name and description are available in multiple languages. It is displayed in the language specified by the user during an AccessAgent installation.
An account data template includes:
A key account data item indicates that it is a unique identifier for that set of account data. Information captured for the key account data item cannot be changed. For a non-key item, information is considered non-constant and can be changed within that set of account data.
For example, a user name can be considered as the key item for the account data and the password the non-key. The password for that user name can change as many times as required. However, the password retains its identity as part of the account data with the given user name.
The credentials are regarded as part of a different data if the user name changes, whether the password is changed or not.
Account data templates are identified through IDs in AccessStudio. Each ID provides you with the properties of the account data items in the template.
For example, adt_csuser_cspwd can be divided into three parts: adt, csuser, and cspwd. adt refers to 'account data template'. csuser refers to 'case-sensitive user name', and cspwd refers to 'case-sensitive password'. This account data template ID indicates that it contains two account data items - a case-sensitive user name and a case-sensitive password.
Account data templates can be associated with AccessProfiles and authentication services. When associated, the account data template is used by the account data bag of each AccessProfile.
An account data bag is a temporary data holder or cache that stores user credentials after their capture from the application screen, and before auto-fill.
The credentials are retrieved from the Wallet and stored in the account data bag before they are automatically inserted on the application screen fields. The user credentials are also stored in the account data bag after capture, before they are transferred to the Wallet of the user.
The account data template information is extracted either from the AccessProfile or the associated authentication service when an AccessProfile is executed. This template is then used to set the structure of the account data bag.
For example, the account data template adt_csuser_cspwd contains two account data items: a case-sensitive user name and a case-sensitive password. A structure is created for the account data bag, which includes two slots. The first slot captures a case-sensitive user name. The second slot captures a case-sensitive password.
Store the information in the corresponding fields. Then, associate an account data item template user name and password fields when you configure them in the AccessProfile.
In this example, users associate the aditi_csuser account data item template with the user name field of the application, and the aditi_cspwd account data item template with the password field. A simple match is conducted to identify data from which field belongs to which slot in the account data bag.