The tunnel certificate object

⚠️

Preview — this feature is being built; the design below is the spec.

The tunnel_certificate object as the API returns it. Every field below appears in every response that returns this object; fields with no value are null rather than missing.

Example

{
  "id": "tcert_01JCE9K1M3P5R7T9V1X3",
  "type": "tunnel_certificate",
  "tunnel_id": "tnl_01JCE4G6J8L0N2Q4S6U8",
  "subject": "CN=erp-onprem-connector-1",
  "serial": "4A:91:0C:7E:22:5B",
  "fingerprint_sha256": "b2:7e:…:91",
  "not_before": "2026-11-05T10:00:00Z",
  "not_after": "2027-02-03T10:00:00Z",
  "status": "active",
  "certificate_pem": "-----BEGIN CERTIFICATE-----\nMIID…\n-----END CERTIFICATE-----",
  "chain_pem": "-----BEGIN CERTIFICATE-----\nMIIF…\n-----END CERTIFICATE-----"
}

Fields

Field	Type	Description
`id`	string	Unique id of this object.
`type`	string	The object type, always `tunnel_certificate`.
`tunnel_id`	string	See the endpoint pages below.
`subject`	string	See the endpoint pages below.
`serial`	string	See the endpoint pages below.
`fingerprint_sha256`	string	See the endpoint pages below.
`not_before`	string	See the endpoint pages below.
`not_after`	string	Certificates are valid for 90 days. Issue the next one before this date.
`status`	string	`active`, `expired` or `revoked`.
`certificate_pem`	string	Install next to the connector’s private key.
`chain_pem`	string	The issuing chain.

Returned by

tunnel user

Was this page helpful?