HP JetAdvantage Security Manager 10 Device E-LTU Manual de usuario descargar pdf (Pagina 19)

private key. Why select HP Security Manager as the CSR source? When HP Security Manager is

selected as the CSR source, stronger encryption algorithms and key lengths become available.

Key length choices are 1024, 2048, 4096 and 8192. Algorithm choices are SHA-1, SHA-256,

SHA-384 and SHA-512. When Device is selected, CSR strength is now limited by what the

device is capable of generating. When Best Possible is selected, Security Manager will choose

between Device and HP Security Manager to match the desired settings on a device by device

basis. Therefore, if a device cannot generate the desired CSR strength in the CRS, HP Security

Manager will automatically be used as the best possible choice for that device.

Note: Many HP device models can accept a stronger, more secure certificate than what they

can generate a request for.

2. Certificate Authority Type

The Security Manager Fleet Certificate Management solution supports Microsoft Standalone and

Enterprise Certificate Authorities or Symantec Certificate Authorties. As a point of reference,

Enterprise CAs are the most widely deployed and essentially dependent on Active Directory to

store and replicate certificate data, while a Standalone CA stores its certificate data in a shared

folder which can be accessed through a Web URL. The Certificate Authority Type setting allows

the administrator to appropriately select the CA implementation to be used for the Security

Manager Certificate Management solution. The settings that can be configured will change when

a Microsoft CA is selected vs. a Symantec CA.

3. Certificate profile OID

A Symantec creator is a cloud based PKI by Symantec whereby the user creates certificate

profiles on the Symantec cloud and specifies an OID in this Certificate profile OID field. A

certificate profile is similar to a template used by an Enterprise Microsoft Certificate Authority.

4. Certificate Authority Server

The hostname of the server hosting the Certificate Authority to be used by Security Manager is

entered here.

5. Certificate Authority Name

The actual name of the Certificate Authority hosted by the Certificate Authority server is entered

here. The Certificate Authority name can be found at the Certificate Authority management

console.

6. Template Name

When Enterprise is selected as the CA implementation of choice, a template name is required.

This is the name of the template created at the CA to be used in conjunction with the Security

Manager Certificate Signing Request. If the Standalone CA implementation is selected, the

template name field is not enabled because templates are not required by a standalone CA.

7. Organization (O)

This is part of the subject information. From a printing device perspective, subject information is

typically based on server and client trusted identity over the network. (For example, secure

printing or 802.1x mutual authentication). Subject settings include the Common Name (CN), 7-

Organization (O) 8-Organization Unit (OU), 9-City/Locality (L), 10-State or Province (S) and 11-

Country Name (C).

The Common Name (CN) identifies the fully qualified domain name associated with the

certificate. It is typically composed of the FQDN or IP address of the device. The certificate is

valid only if the request hostname matches the certificate common name. In the Security

Manager identity certificate policy settings, you will notice that the Common Name field is

non-existent. By default, Security Manager devices are resolved to a hostname when

1 2 ... 14 15 16 17 18 19 20 21 22 23 24 ... 30 31

Comentarios a estos manuales

Sin comentarios

HP JetAdvantage Security Manager 10 Device E-LTU Manual de usuario Pagina 19

Comentarios a estos manuales

Relacionado con productos y manuales para No HP JetAdvantage Security Manager 10 Device E-LTU