10.1 Certificate Application (New CA System)¶
IHEP CA(Chinese High Energy Physics Grid Computing Certification Authority) is an accredited member of the European Policy Management Authority for Grid Authentication in e-Science (EUGridPMA) and the Asia Pacific Grid Policy Management Authority for Grid Authentication in the Asia Pacific region. It is operated by the Computing Center of IHEP as part of the Large Hadron Collider Computing Grid (LCG) project, has been running at the IHEP Computing Center in Beijing since 2004, and issues X.509 certificates for Grid computing.
This section describes how to apply for, download, renew and revokeUser certificates,Robot certificatesandHost certificatesissued by the new IHEP PKI system (based on OpenXPKI), as well as EST automatic renewal for host certificates. Unless otherwise stated, the WebUI URL is:https://gridca.ihep.ac.cn/webui/ihepca/.
WebUI, EST and login must all use HTTPS; the public download URLs of CA certificates, CRLs and CP/CPS are also accessible over HTTP.
UI conventions
Button and menu names in this section follow the English WebUI.Continuesaves the current page and moves on to the next one, and normally does not submit anything;Submit-style buttons such asSubmit requestare what actually send the request to the system or the RA. Before submitting, check the certificate subject, SAN and requester information shown on the page.
The manual for the legacy CA (OpenCA,cagrid.ihep.ac.cn) is kept in10.4 Certificate Application (Legacy CA System)for historical reference only.
This chapter is organized by workflow stage:
- 10.1.1 Log in to the WebUI
- 10.1.2 Applying for Certificates(User / IHEP-2013 migration / Robot / Host)
- 10.1.3 Download and Use Certificates
- 10.1.4 View, Renew and Revoke
- 10.1.5 EST Auto Renewal and Central Management
Certificate Types and Application Methods¶
| Type | Purpose | Key generation & custody | Common application method |
|---|---|---|---|
| User Certificate | Grid user authentication, browser/CLI client authentication | Generated by the system, downloaded as PKCS#12 by the user | WebUI |
| Robot Certificate | Experiment tasks, pilots, service robots (non-human identity) | Generated by the system, downloaded as PKCS#12 by the responsible person | WebUI |
| Host Certificate | Host server authentication, also controlled client authentication | When applied for through the WebUI the CA generates the key and the PKCS#12 is downloaded and installed on the target host; with EST renewal and IHEP-2013 migration the target host generates the key and the CSR itself | WebUI first issue; EST auto renewal |
- The Subject of a user certificate contains the English name, short account, organization and unit.Do not put a Chinese name directly into the Subject.
- The Subject and SAN of a host certificate contain the host DNS names and the applicant's LDAP email;do not reuse a personal certificate private key as a host private key.
- Information in the certificate itself (Subject DN, SAN, Issuer, CRL URL, etc.) cannot be modified by users and should stay consistent across renewals; Requester, Email, Owner contact and Comment in the WebUI are system metadata used for review, search, notification and accountability.
- The WebUI certificate and the EST certificate of the same host follow two different issuance paths: the EST script generates the key and the CSR locally on the target host, so the private key from a WebUI
.p12must not be reused for it.
The overall application workflow is shown below (the flow is the same for User, Robot and Host certificates; the IHEP-2013 migration entry joins from the left):
Preparation¶
- Make sure your IHEP SSO account can log in normally (unified authentication:https://login.ihep.ac.cn).
- Users who do not yet have a unified authentication account should register with theemail address of their current institution(rather than an old one), so that the email bound to the account is valid and notifications can be received; the guarantor / in-institute contact should bethe person in charge of the experiment or an IHEP staff member you know.
- Make sure the email in LDAP is correct. It becomes the email SAN of your user or host certificate and is used for ownership and notifications.
- If you are applying for a host certificate, confirm all DNS names in advance; host names are lowercased into the certificate, and names added later require a new application or CA process.
- Install the trust chain: the IHEP computing platform's compute nodes and servers already have the new Root and Issuing CA public-key certificates and a CRL update mechanism deployed, so users normally do not need to install them; if you use the certificate on your own machine or an external Grid client/server, install those public-key certificates and the CRL update mechanism yourself.
FAQ¶
| Symptom | Check first |
|---|---|
| WebUI login fails | LDAP account/password, wrong client certificate selected in the browser, system time |
| Cannot find your certificate | UseHome → My Certificates; compare the login email with the certificate owner/email metadata |
| Request stuck in PENDING | Record the workflow ID inMy Workflowsand contact the RA; do not resubmit |
| No download-private-key Action | The private key may not be generated or kept by the CA (for example an EST-issued host certificate), or it may have been exported already; keys cannot be recovered |
| EST TLS failure | Check the full server TLS chain withcurlor the script; setCURL_CA_CERTcorrectly,never use-k |
| EST migration rejected | Old certificate validity, old CA CRL, key match, LDAP email and unchanged DNS/SAN |
| Browser shows no certificate chooser | Whether the browser store has the private key, a cached choice, or the wrong auth method |
| Host service fails after reload | Restore the previous matching cert/key pair from local backups, check service logs and permissions, then contact the site admin |
| Chain validation fails | Client installed the new Root and Issuing CA; public Issuing/Root CRL URLs reachable |
When contacting support, provide the certificate serial number or Subject, the WebUI workflow ID, the time (UTC), the full error text and relevant log excerpts;never provide private keys,.p12files, key passwords or LDAP passwords.
CA contact: Han Xiao,hanx@ihep.ac.cn, +86 010 88238602.
SeeFAQ.
有问题?输入后跳转到对话页继续交流