A CA certificate (Certificate Authority certificate) is a digitally signed X.509 credential issued by a trusted Certificate Authority. It serves two primary purposes:

  1. Root of Trust
    The CA certificate represents the “root” or “intermediate” authority that vouches for the authenticity of all certificates it issues. Clients (browsers, operating systems, applications) include CA certificates in their trust stores so they can validate any server or client certificate chained back to that CA.
  2. Signature Anchor
    Each end‑entity certificate (for a website, device, or user) bears a digital signature created by the CA’s private key. Verifying that signature against the public key in the CA certificate ensures the certificate hasn’t been tampered with and was indeed issued by the trusted authority.

How to Request an SSL/TLS CA Certificate from eMudhra
Requesting an SSL/TLS certificate from eMudhra’s CA is a streamlined, API‑driven process designed for both self‑service and enterprise workflows. Below is a step‑by‑step guide:

  1. Prepare Your Certificate Signing Request (CSR)
    • Generate a Key Pair: On your server or in your HSM, create a new private key (RSA or ECC) and corresponding CSR.
    • Populate CSR Fields: Include your fully qualified domain name (FQDN) in the Common Name (CN) or Subject Alternative Name (SAN) fields, together with organization details (O, OU, L, ST, C) as required for OV/EV validation.
  2. Log In to the eMudhra Developer Portal
    • Access Account: Navigate to the eMudhra PKI Portal and authenticate using your corporate credentials or API token.
    • Navigate to Certificate Services: Select “SSL/TLS Certificates” from the menu to open the issuance dashboard.
  3. Choose Certificate Profile & Validity
    • Select Validation Level: Pick Domain‑Validated (DV), Organization‑Validated (OV), or Extended‑Validation (EV) based on your security requirements.
    • Define Validity Period: Choose your term (1, 2, or 3 years) and any additional add‑ons (wildcard, SANs).
  4. Submit CSR & Payment
    • Upload CSR: Paste the PEM‑encoded CSR into the portal form or reference it via API.
    • Review Order: Confirm domain names, validity term, and organizational information.
    • Complete Payment: Pay via credit card, bank transfer, or invoice (for enterprise accounts).
  5. Undergo Validation
    • Automated Domain Check: For DV certificates, eMudhra sends a verification email or prompts you to create a DNS record.
    • Manual Organization Audit: For OV/EV, provide business documents (e.g., incorporation certificate, address proof) through a secure upload widget.
  6. Download & Deploy Certificate
    • Retrieve Certificate Bundle: Once issued, download the server certificate, any intermediate CA certificates, and the root bundle in PEM or PKCS#7 format.
    • Install on Your Server: Configure your web server, load balancer, or appliance with the certificate chain and private key.
    • Validate Installation: Use online SSL checkers or the eMudhra portal’s health‑check tool to verify correct installation and chain integrity.

Tips for a Smooth Request

  • Use API for Automation: Integrate with eMudhra’s RESTful API to programmatically request, renew, and revoke certificates as part of your CI/CD pipeline.
  • Leverage HSM Integration: Generate and store private keys within FIPS‑certified HSMs to prevent key exposure. eMudhra’s CA can directly ingest keys from supported HSMs.
  • Enable Auto‑Renewal: Configure Certificate Lifecycle Management policies to trigger renewal requests automatically before expiry, avoiding any service interruption.

By understanding what a CA certificate is and following eMudhra’s guided request process, organizations can rapidly secure their web applications and APIs with trusted SSL/TLS credentials—backed by enterprise‑grade validation, automation, and HSM‑level key protection.