User guide

9: Services
SecureLinx Spider/SpiderDuo User Guide 84
Figure 9-9 Certificate Signing Request Page
2. Modify the following fields.
3. Click Create to initiate the Certificate Signing Request generation. Download the CSR by
clicking Download. The Download button displays when a certificate is created. Send the
saved CSR to a CA for certification.
4. Click Upload to upload the certificate from the client computer to the Spider. The Spider now
has its own certificate used for identifying itself to its clients.
Table 9-10 SSL Server Certificate Management
Field Description
Common name The network name of the Spider once it is installed in the user’s network
(usually the fully qualified domain name). It is identical to the name that is
used to access the Spider with a web browser without the prefix http://. In
case the name given here and the actual network name differ, the browser
will pop up a security warning when the Spider is accessed using HTTPS.
Organizational unit This field specifies to the department within an organization to which the
Spider belongs.
Organization The name of the organization to which the Spider 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., US for the United States).
Email The email address of a contact person responsible for the Spider and its
security.
Challenge password/
Confirm Challenge
password
Certain 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 four characters.
Key length (bits) Select the key length from the drop-down menu.