Ana içeriğe geç

Keys & Secrets API

API Sections

JWKs (JSON Web Keys)

Keystores

Keys (Crypto Keys)

Certificates

Package or file?

Two different jobs, two different endpoints. The Export / Import endpoints produce an Apinizer package — that is how an object moves between Apinizer installations, with its description, environments and settings intact. The Export / Import File endpoints hand over the material itself — a PEM, a .jks/.p12/.pfx, a JWKS document — which is what a JVM truststore, a web server or a relying party actually consumes. Certificates have always worked this way; keys, keystores and JWKs now do too.

Authentication

All endpoints require authentication using a Personal API Access Token.

Permissions

GET Operations (List/Get Certificate/Key/Keystore/JWK)

  • User must have SECRETS + VIEW permission in the project
  • If the asset category does not exist, user must have at least one permission in the project

POST/PUT/DELETE Operations (Create/Update/Delete Certificate/Key/Keystore/JWK)

  • User must have SECRETS + MANAGE permission in the project
  • For deployment operations (when deploying certificates to environments), user must also have SECRETS + DEPLOY_UNDEPLOY permission

Permission Requirements

OperationRequired Permission
List/Get Certificate/Key/Keystore/JWKSECRETS + VIEW (or any permission if category doesn't exist)
Create/Update/Delete Certificate/Key/Keystore/JWKSECRETS + MANAGE
Deploy Certificate to EnvironmentSECRETS + DEPLOY_UNDEPLOY
Export CertificateSECRETS + EXPORT_IMPORT
Import Certificate / Truststore fileSECRETS + EXPORT_IMPORT
Export/Import KeystoreSECRETS + EXPORT_IMPORT
Export/Import KeySECRETS + EXPORT_IMPORT
Export/Import raw file (Key / Keystore / JWK)SECRETS + EXPORT_IMPORT