Jump to main content

# Edit profile

The Change profile operation allows changing the profile settings specified in the current profile list.

The following profile parameters are available for modification:

- Profile's name;
- Storage device;
- Storage device parameter;
- Password;
- Password confirmation;
- Key container format;
- Container's name.

Perform the actions described below to change the current profile settings:

1. Select the required profile in the active Key profiles list panel of the main Configurator window.
2. Right-click on the context menu – select Edit profile or click on the Edit profile button.
3. Display the Profile edition dialog window.
4. Enter the necessary changes in the settings and click on the Save button:

   - Profile's name – the parameter should not contain Kazakh characters. Latin and Cyrillic are allowed. The characters 0-9, A-Z, А-Я, “an underscore” and “a hyphen” may be included in the profile name;

   - Storage device – select the required key container storage device from the list – File system, DigiFlow LLP & Aladdin Token JC& ARDS JaCarta or the required parameter from Table 2 when ;

   - Storage device parameter – set the values shown in Table according to the connected device;

   - Password – enter the password (PIN) in the field to access the storage device. The entered password is displayed hidden in the fields – (**********);

   - Confirmation – enter the password (PIN) in the field to access the key container, which is the same as the entered password in step;

   - Container's name – enter the container name. By default, the container name is the system user account name.

5. At correct operation performance the generated profile will be displayed on the accessible profile list.
   Figure 1: Profile editing window

Table 1. The interconnection between the profile setting parameters of the key information storage device used

External device | Storage device | Storage device parameter
JaCarta | DigiFlow LLP. & Aladdin Token JC & ARDS JaCarta | ARDS JaCarta 0, ARDS JaCarta 1 etc. according to the device connection order
New algorithm for tokens* | ARDS JaCarta 0, ARDS JaCarta 1 etc. according to the device connection order
jaCarta Laser** | asepkcs.dll
eToken PRO72k(JAVA) | Aladdin Token & ВСС/ DigiFlow LLP. & Aladdin Token JC & ARDS JaCarta | Aladdin Token JC 0, Aladdin Token JC 1 etc. according to the device connection order
New algorithm for tokens* | Aladdin Token JC 0, Aladdin Token JC 1 etc. according to the device connection order
KAZTOKEN, version 1.4 | DigiFlow LLP. & Aladdin Token JC & ARDS JaCarta | DigiFlow LLP. KAZTOKEN 0, DigiFlow LLP. KAZTOKEN 1 etc. according to the device connection order
SafeNet eToken 5110 | DigiFlow LLP. & Aladdin Token JC & ARDS JaCarta | SafeNet Token JC 0, SafeNet Token JC 1 etc. according to the device connection order
New algorithm for tokens* | SafeNet Token JC 0, SafeNet Token JC 1 etc. according to the device connection order
*Plugin to work with ГОСТ-KZ algorithms. **The plugin is required to work with a thin client WYSE (key information is generated in the Laser-applet company Aladdin Rd). To generate keys using the plugin, you need to install PKI Client. JaCarta Laser plug-in only supports RSA keys (4096 bit below). ***If the "Safenet Authentication Client" SOFTWARE is installed on the user's computer, it is necessary to change the "storage device Parameter" in all profiles that specify "Aladdin Token JC 0" to "AKS ifdh 0"