Certificate management
On BTP the certificates in question are the client and trust certificates a destination uses when it calls another system, kept with the destination in SAP Destination serviceSAP Destination serviceNamed, credentialed addresses of other systems, resolved at runtime — so an application holds no URL and no secret of its own, and the same code reaches a different system in every landscape.sap official, btp.
Overview
The Destination service uploads, generates, views and deletes certificates for destinations from JKS, PFX, PEM, CER, CRT and P12 files, and renews a generated certificate automatically near expiry when that option is set. SAP also publishes the BTP Trust Store, the root CA certificates BTP uses, for clients to update regularly.
Not covered: An uploaded certificate cannot be renewed automatically, so a client certificate issued outside BTP is replaced by hand before it expires.
The certificate a public domain is served with is held by SAP Custom Domain ServiceSAP Custom Domain ServiceExposes a BTP application publicly under the customer's own domain instead of the default subdomain, with the TLS/SSL certificate and TLS configuration that domain is served with.sap official, btp, which is SAP's own and sits beside the Destination service.
No community artifact is documented here.
Artifacts
Details
Coverage
For your agent
- Ref
capability:certificate-management- JSON
- /capabilities/certificate-management.json
- MCP
- Connecting an agent