Provision certificates to Oracle Cloud Load Balancer¶
Preview feature
This feature is available in Preview and isn't yet generally available (GA). Functionality and behavior can change before GA.
Provision a certificate from Certificate Manager - SaaS to an Oracle Cloud load balancer. Oracle Cloud Infrastructure (OCI) doesn't let you change a certificate bundle after it's uploaded, so to renew a certificate, Certificate Manager - SaaS uploads it to the load balancer as a new certificate bundle, moves every listener that used the old bundle to the new one, and then deletes the old bundle.
Before you begin¶
- An Oracle Cloud Load Balancer machine that you created and whose status is Verified.
- The certificate to provision in the Certificate Manager - SaaS inventory, with its private key.
- The System Administrator or PKI Administrator role, or the Resource Owner role and membership in the machine's owning team.
- A load balancer that already exists in the region you configured for the machine.
- To replace a certificate that's in use, an HTTPS or SSL listener that terminates Transport Layer Security (TLS) with a load balancer certificate bundle. Listeners that use a certificate from the OCI Certificates service aren't supported.
To provision a certificate to Oracle Cloud Load Balancer¶
- Sign in to Certificate Manager - SaaS.
- Click Installations > Machines.
- Click the more options button at the end of the machine's row, and then select Provision.
-
In Search a certificate by name, expiration or fingerprint, enter part of the certificate's name, expiration date, or fingerprint, and then select the certificate from the results. Confirm that it's the right certificate by checking Subject DN, Validity, and Certificate SHA1 Fingerprint.
The rest of the Provision a certificate dialog appears after you select a certificate.
-
Under Certificate Information, in Load Balancer OCID, enter the Oracle Cloud identifier (OCID) of the load balancer. It starts with
ocid1.loadbalancer.. - (Optional) In Load Balancer Name, enter the display name of the load balancer. After provisioning, Certificate Manager - SaaS replaces this value with the load balancer's display name from OCI. This name isn't part of the installation's identity, so renaming the load balancer in OCI doesn't create a new installation.
-
Leave Certificate Bundle Name empty.
Certificate Manager - SaaS generates a new, unique name for every certificate it uploads and replaces any value you enter. The name is the certificate's common name in lowercase, with any character other than a letter, digit, hyphen, or underscore replaced by an underscore, capped at 64 characters, and followed by a hyphen and the first 12 characters of the certificate's SHA-256 fingerprint. If the certificate has no common name, Certificate Manager - SaaS uses its first DNS subject alternative name, or
certif it has none. For example, a certificate forwww.example.comis uploaded aswww_example_com-3f9a1c07b2e4. -
Under Installation Endpoint, in Listener Name, enter the name of a listener that serves the certificate you want to replace.
Certificate Manager - SaaS moves this listener and every other listener that uses the same certificate bundle to the new certificate.
Note
If you leave Listener Name empty or enter
<unbound>, Certificate Manager - SaaS uploads the certificate without moving any listener, and the previous certificate bundle stays on the load balancer. Discovery uses<unbound>for a certificate bundle that no listener uses. -
(Optional) To save the installation without pushing the certificate now, disable Push certificate on save.
- Click Save. To save and then provision another certificate, click Save & New.
After you save, Certificate Manager - SaaS uploads the certificate as a new certificate bundle and moves each listener that used the old bundle to it, one listener at a time. Each listener keeps its other settings, such as its protocols, cipher suite, and hostnames. When no listener or backend set uses the old bundle anymore, Certificate Manager - SaaS deletes it. OCI applies each change as a work request, and Certificate Manager - SaaS waits for each one to finish before it starts the next. An installation appears on the machine's Installations tab. To provision on a schedule instead of right away, set up a machine provisioning schedule.
Note
- Certificate Manager - SaaS doesn't change backend sets. If a backend set uses the old certificate bundle, the old bundle stays on the load balancer. To remove it, move the backend set to the new bundle in OCI, and then delete the old bundle.
- If provisioning fails after every listener has moved to the new certificate but before the old bundle is deleted, pushing the certificate again doesn't delete the old bundle. Delete it in OCI.