SNI Certificate
Configure SNI Certificate to receive renewed certificates automatically.
1. Overview
A Kong - SNI Certificate node deploys certificates to this configured target.
2. Configuration
Select this platform and deployment position, then supply the following parameters.
| Field | Required | Description |
|---|---|---|
| API URL | Yes | https://kong.example.com |
| Kong Admin Token | No | |
| Existing SNI | Yes | |
| Verify TLS Certificate | Yes | Yes (recommended) / No (self-signed server certificate); default: true |
3. Deployment and renewal
- Use the Kong Gateway Admin API. Select an existing SNI certificate; renewals preserve its settings. Do not expose an unauthenticated Admin API publicly.
Associate the certificate with the node and enable automatic deployment on renewal. Certificate replacement uses the same configured target on every run.
The endpoint must use HTTPS and be reachable from the CertOne deployment service. TLS certificate verification is enabled by default. Disable verification only when the target has a self-signed certificate and its address is trusted.
A certificate can be shared by several SNIs. The new certificate must cover every associated SNI; deployment is rejected before upload if it would break another hostname. Reading the certificate and its SNI list is required in addition to updating it.
4. Verification
Automated protocol tests cover request construction, failure handling and credential redaction. This integration has not been tested against a live account or device in this change. A successful configuration check verifies connectivity and read access; the first deployment also verifies write permissions.