Overview

The SSL certificate of your Hosted instance is expiring. This article covers the renewal with a Certificate Signing Request (CSR) that we generate for you, and the installation of a certificate you already own. Cloud instances use certificates that Jive manages; they need no renewal request.

Before you start

• Allow at least four weeks for the whole renewal. It has three steps that run one after the other: we generate the CSR, you order the certificate from your certificate authority, and we install it. Each step can take several days.
• Publicly trusted certificates issued on or after March 15, 2026 are valid for at most 200 days, and from March 15, 2027 for at most 100 days (CA/Browser Forum ballot SC-081v3).

1. Request the CSR

Send us on the ticket:

• the Common Name (CN)
• every other hostname the certificate must cover, on Production and UAT; the current certificate's Subject Alternative Names list them
• whether the certificate must be a wildcard
• the Subject fields: Organization, Organizational Unit, Locality, State, Country, and an email address if you want one in the certificate

We generate the CSR with its private key and send you the CSR file to submit to your certificate authority. The private key stays with us.

2. Send us the issued certificate

Attach to the ticket the signed certificate, the intermediate certificate(s) and the root certificate, or a single PEM file with the whole chain. No private key is needed. We check the certificate against the CSR and the hostnames, install it, and confirm the new expiry date to you.

Using a certificate you already own

A certificate you own, such as a wildcard, can be installed if it covers every hostname your instance uses. We do not hold its private key, and a certificate can only be installed together with the key it was generated with, so send us the certificate, its private key, the intermediate certificate(s) and the root certificate. If your security policy does not allow sharing the key, request a CSR instead (step 1).