Skip to content

← All integrations

Cloud service

Uploads the certificate and chain to a third-party enrollment in Akamai CPS.

The appliance runs the integration and connects to Akamai CPS through CPS API over HTTPS on port 443. No service agent is installed on Akamai CPS.

What happens

  1. The appliance connects to Akamai CPS through CPS API on port 443.
  2. Issue from the pending CPS change’s CSR. The appliance matches the public key and uploads the certificate and intermediates; CPS retains the private key.
  3. The integration follows the change and acknowledges offered reviews unless automatic acknowledgement is disabled. The production certificate fingerprint in CPS confirms deployment.

Technical details

Connection
The integration runs on the appliance, which connects over HTTPS to CPS API, port 443. No service agent is installed.
What you need
Akamai Control Center > Identity and access > API clients: create a client with the Certificate Provisioning System API, READ-WRITE. From its .edgerc values, enter client_token, client_secret and access_token here; host is the address of the destination.
Actions
Discovery, Installation, Verification; no rollback action
Integrations
akamai-cps-api 2.0.0
Note
  • There is no rollback or removal action. After an accepted upload, resolve failures in CPS; the integration does not probe the public TLS listener. The certificate chain consists of the intermediate certificates that link the server certificate to a root certificate the browser trusts.

Next steps