Output File; How Pins Are Stored In The Directory - Red Hat CERTIFICATE SYSTEM 7.3 - COMMAND-LINE Manual

Chapter 6. PIN Generator
dn:cn=user2, o=example.com
...
dn:cn=user3, o=example.com
PINs can also be provided for the DNs in plain-text format; these PINs are hashed according to the
command-line arguments.
dn:cn=user1, o=example.com
pin:pl229Ab
dn:cn=user2, o=example.com
pin:9j65dSf
...
dn:cn=user3, o=example.com
pin:3knAg60
NOTE
Hashed PINs cannot be provided to the tool.

6.2.2. Output File

The PIN Generator can capture the output to a text file specified by the output option.
The output contains a sequence of records in the following format:
dn: user_dn1
pin: generated_pin1
status: status1
dn: user_dn2
pin: generated_pin2
status: status2
...
dn: user_dn#
pin: generated_pin#
status: status#
where user_dn is a distinguished name matching the DN filter or listed in the input file. By default, the
delimiter is a semi-colon (;) or the character defined on the command line. generated_pin is a string of
characters of fixed or variable length, depending on the length parameters used. status is one of the
Table 6.2, "PIN Generator Status
values listed
The first line in each record is always the DN. The subsequent lines for pin and status are optional.
The record ends with a blank line, using the Unix end of line sequence, (\n).

6.2.3. How PINs Are Stored in the Directory

Each PIN is concatenated with the corresponding LDAP attribute named in the saltattribute
argument. If this argument is not specified, the DN is used. That string is hashed with the routine
26
".