HP JetAdvantage Security Manager 10 Device E-LTU Uživatelský manuál stáhnout pdf (Strana 6)

Directory service. When you install an enterprise root CA, it uses Group Policy to propagate its

certificate to the Trusted Root Certification Authorities certificate store for all users and computers in

the domain. Enterprise Certificate Authorities require a certificate template and a CSR to generate a

certificate and are typically setup to automatically generate certificates from received requests.

Standalone Certificate Authorities are primarily intended to be used as Trusted Offline Root CAs in a

CA hierarchy. (ex. staging, etc.). Standalone Certificate Authorities do not require certificate

templates. Typically intermediate authorities that can be trusted back to root will be setup for

generating certificates on behalf of the root CA.

CREATING A CERTIFICATE REQUEST USING EWS

Anyone who has ever attempted to install an identity certificate (Jetdirect certificate) using EWS would

appreciate any other technique that can save time and effort. The image below demonstrates the

steps required to install just one Jetdirect certificate on a device using EWS. Imagine having to follow

these steps for 1000 devices one at a tine via EWS. Even in cases where all steps are performed

without error or issues, each device can take upwards of 15 minutes to complete even with a

streamlined technique for delivering requests to the CA and retrieving certificates in return. Some

steps are quite error prone and may require starting the entire process again. It is easy to see why

administrators who have to install identity certificates need an easier technique to do so for a fleet of

devices.

Step 1 above involves logging into EWS for a device via browser, selecting Networking,

Authorization, Certificates, selecting Configure under Jetdirect Certificate and filling out a form.

1 2 3 4 5 6 7 8 9 10 11 ... 30 31

Žádné komentáře

HP JetAdvantage Security Manager 10 Device E-LTU Uživatelský manuál Strana 6