Skip to Content
Browse documentation

Create an SSL Certificate Request in UAPP

Complete every UAPP CSR field, choose RSA or ECDSA keys, add SAN names and review optional email delivery before generation.

Open SSL/TLS → Certificate Requests and choose the create action.

Request fields

FieldRequired value
Private Key TypeRSA 4096 (initial selection), RSA 2048, ECDSA P-521, P-384 or P-256. Choose a type accepted by the authority and intended clients.
Email deliveryOff initially; enables optional delivery of generated material.
Delivery Email AddressRequired when email delivery is enabled; must be a valid email address.
Primary DomainRequired; choose an account-owned primary, alias, addon or subdomain offered by the form.
CA Contact EmailRequired valid email address.
OrganizationRequired organization name.
Organizational UnitRequired department/unit name in this form.
City or LocalityRequired locality.
State or ProvinceRequired state/province.
CountryRequired; choose the country from the supplied list.
Additional SAN DomainsOptional; comma-separated or newline-separated DNS names.

DNS names are normalized, including internationalized names, and duplicate SAN entries are removed. Enter DNS names rather than URLs, paths or IP addresses. Wildcard syntax is accepted for certificate identifiers; this does not prove a particular issuance/validation workflow supports the wildcard.

The primary domain is ownership-checked. Additional SAN names are parsed as certificate names; actual authority validation is still necessary.

Generate

  1. Verify the domain and requested names with your authority.
  2. Complete the identity and contact fields.
  3. Choose the key type and delivery preference.
  4. Select the create/review action.
  5. Check the primary domain and key type in the confirmation and confirm generation.
  6. Read the result and return to Certificate Requests.

Email delivery includes private-key material

The delivery path sends the CSR, private key and generated certificate material. Leave delivery off when that channel is unsuitable. A successful CSR creation message does not independently confirm email delivery.

Generation creates request/key artifacts; it does not obtain a publicly trusted certificate or complete installation. Preserve existing request material before generating again for the same domain because storage is organized by domain, not as a versioned request history.

Submit the CSR to the authority and keep its matching key for certificate installation.