Setup guide

Oracle Cloud Load Balancer setup guide for sslcertificates.io

This guide explains how to connect Oracle Cloud Load Balancer to sslcertificates.io, what credentials to prepare, and how to operate safely in Test (Let's Encrypt Staging) and Live (publicly trusted issuance) environments.

What this integration does

Oracle Cloud Load Balancer: Certificate bundle on load balancer listeners. Discovery enumerates accounts/subscriptions/projects and child resources so customers do not type ARNs by hand.

Category: Cloud & CDN. Public integration page: /integrations/oracle-lb.

Outcomes

Discover the Oracle Cloud Load Balancer resources that terminate TLS
Install a replacement certificate
Verify the public TLS endpoint
Keep the previous certificate for rollback

Prerequisites

Active Oracle Cloud Load Balancer account
API access
OCI load balancer cert APIs.

Authentication and credentials

Authentication mode in the catalog: cloud_identity.

Fields the connection form expects: Token / secret (optional); Role ARN (optional); Tenant ID (optional); Client ID (optional); Client secret (optional); Service account JSON (optional); Access key (optional); Secret key (optional)

Store secrets in a password manager while you paste them once into sslcertificates.io. Values are encrypted at rest and are not shown again after save. Prefer narrowly scoped credentials over admin passwords.

OCI load balancer cert APIs.

Permissions (least privilege)

OCI load balancer cert APIs.

Do not treat an accepted API write as live TLS. Verification is a handshake or provider status that names the certificate ID/ARN.

Connect in the workspace

Sign in to sslcertificates.io
Open Integrations
Choose Oracle Cloud Load Balancer
Enter the connection details
Test the connection
Select the resources you want to manage

After Test connection succeeds, run Discover so the platform lists zones, subscriptions, domains, or deploy targets you are allowed to see. Select only resources this organization should manage.

Test vs Live certificate environments

Test uses Let's Encrypt Staging as the CA directory. Staging certificates are not trusted by browsers; use them to prove DNS-01, HTTP-01, deploy scripts, and webhooks without consuming production rate limits.

Live uses Let's Encrypt Production (or a commercial CA you connect) for publicly trusted certificates. The integration connection is the same; only the API key environment and CA selection on the certificate order change.

Create separate API keys labeled Test and Live. Do not reuse a Live key in CI that hammers validation endpoints.

Deployment and verification

After issuance, deployment connectors install the leaf and chain (and private key when applicable), bind the certificate to the site or listener, reload or apply configuration where required, and optionally verify the public TLS handshake.

Treat HTTP 200 from a vendor API as incomplete success. Compare the SHA-256 fingerprint of the certificate served on port 443 to the leaf you expect. The platform may keep a .prev or rollback copy — use it if a bad deploy breaks HTTPS.

Capabilities referenced for this integration: discover, status, bind, tls_verify.

Rollback

If verification fails after deploy, restore the previous certificate using the integration rollback path or manual vendor UI, then open a ticket with the order id and X-Request-Id.

Discovery

Discovery runs only after authentication succeeds. The integration enumerates resources the credential may read — hosted zones, subscriptions, domains, clusters, or load balancers depending on Oracle Cloud Load Balancer. If discovery returns empty, the credential is usually too narrow or pointed at the wrong account or region.

Renewal and ongoing operation

When Oracle Cloud Load Balancer participates in deployment or DNS automation, renewals re-use the same connection. Watch webhook events such as certificate.renewal_failed and verify the external endpoint after every replacement. A renewed certificate in inventory is not proof HTTPS serves the new leaf.

Disconnect and credential rotation

Open Workspace → Integrations → Oracle Cloud Load Balancer → Disconnect to remove stored credentials from this organization. DNS integrations should delete only TXT records the platform created for ACME challenges. Rotate vendor tokens on a schedule; update the integration, run Test connection, and revoke the old credential at the vendor.

Troubleshooting

Symptom	Likely cause	What to do
Test connection fails immediately	Wrong host, region, or token	Re-copy credentials; confirm clock skew and TLS to the vendor API
Discovery is empty	Scoped IAM/token cannot list resources	Widen read permissions temporarily, discover, then tighten
Order stuck validating	DNS or HTTP challenge not public yet	Inspect the order challenges; wait for propagation; POST validate
Deploy reported success but HTTPS unchanged	Old cert still bound on the edge	Compare served SHA-256 to expected leaf; reload or bind again
`insufficient_scope` from sslcertificates.io API	API key missing abilities	Mint a key with integrations:write and certificates:write

Stable API error codes are documented at /docs/errors. Include X-Request-Id when contacting support.

Official vendor documentation

https://cloud.google.com/docs

Continue

Back to Oracle Cloud Load Balancer Create account