Lindy P16-IP Section, IP Access Configuration & Operation, Common name, Organizational unit

Models: P16-IP

1 77
Download 77 pages 10.92 Kb
Page 60
Image 60
Common name

Section 4

IP Access Configuration & Operation

 

 

 

After completing these three steps, the P16-IP has its own certificate that is used to identify it to its clients.

Note: If you destroy the CSR on the P16-IP there is no way to get it back! In case you deleted it by mistake, you have to repeat the three steps as described previously.

Common name

This is the network name of the P16-IP once it is installed in the user©s network It is identical to the name that is used to access the P16-IP with a web browser (without the “ http:// ” prefix). In case the name given here and the actual network name differ, the browser will pop up a security warning when the P16-IP is accessed using HTTPS.

Organizational unit

This field is used for specifying to which department within an organization the P16-IP belongs.

Organization

The name of the organization to which the P16-IP belongs.

Locality/City

The city where the organization is located.

State/Province

The state or province where the organization is located.

Country (ISO code)

The country where the organization is located. This is the two-letter ISO code, e.g. DE for Germany, or US for the USA.

Challenge Password

Some certification authorities require a challenge password to authorize later changes on the certificate (e.g. revocation of the certificate). The minimal length of this password is 4 characters.

59

Page 60
Image 60
Lindy P16-IP Section, IP Access Configuration & Operation, Common name, Organizational unit, Locality/City, State/Province