10.1.2.4 Host Certificate¶
A host certificate should be requested by someone with administrative responsibility for the host; the applicant's LDAP email is written into the SAN and stored as owner/requester metadata. The procedure is identical to a user certificate (see10.1.2.1) except for theEdit Subjectpage, where you enter the host names. A host certificate needs theprimary DNS name, all additional DNS names, the host purpose and the responsible person;do notenter IP addresses, URLs, ports,https://prefixes, wildcards like*.ihep.ac.cn, or a comma-separated list of names into a single hostname field:

- Hostname: must be theprimary FQDNof the host, e.g.
host01.ihep.ac.cn; do not enter the short namehost01. - Additional hostname: other DNS names may be added; each field takesonecomplete FQDN only, no wildcards; add multiple names one by one with the page control.
- DNS names are issued in lowercase, so confirm DNS resolution and site responsibility before submitting.
- The email SAN always comes from the logged-in user's LDAP email;do not enter someone else's email to bypass review.
- The
Commentshould describe the service purpose, the site and the ticket, e.g.DIRAC Storage Element, IHEP CC, ticket #12345.
The remaining steps (confirming the information, setting the private key password, submission, RA review) are exactly the same as for a user certificate. Once issued, open the certificate inMy Certificates, clickDownload private key/keystore (PKCS12/PKCS8/Java)in theActionarea and choosePKCS12; see10.1.3 Download and Use Certificates. The WebUI always generates an RSA 4096 private key encrypted with AES-256; there is no key type or length choice, and no CSR upload.
Install the WebUI-issued host certificate on the target host¶
- Transfer the downloaded
.p12to the target host through a controlled channel; avoid email, public cloud drives or shared temporary directories. Create the key directory and restrict permissions:
Export the end-entity certificate and private key (theExport Password, i.e. the export password set when downloading the
.p12, will be requested):Verify that the certificate and key match, and check the DNS/email SAN:
test"$(sudoopensslx509-in/etc/grid-security/hostcert.pem-noout-modulus|opensslsha256)"=\"$(sudoopensslrsa-in/etc/grid-security/hostkey.pem-noout-modulus|opensslsha256)"\&&echo'certificate and key match'sudoopensslx509-in/etc/grid-security/hostcert.pem-noout\-subject-issuer-dates-extsubjectAltName-extextendedKeyUsageIf the service runs under a dedicated account (e.g.
dirac), set a controlled owner, group and permissions only when the service truly needs to read the key;the private key must never be world-readable.- Verify the service configuration, reload the service, then delete
/root/host01.p12. Keep a securely protected offline backup; do not keep multiple plaintext keys on the host.
Do not mix
This procedure applies only to WebUI-issued Host certificates. The EST auto-renewal in10.1.5and the IHEP-2013 Host migration still generate a new private key and CSR on the target host; the encrypted private key exported from a WebUI.p12must not be fed to the EST scripts.
FAQ¶
SeeFAQ.
有问题?输入后跳转到对话页继续交流