OpenAPI spec for CyberArk Conjur secrets management and policy-based authorization automation via API
CyberArk Conjur is an open-source secrets management platform for storing, controlling, and auditing access to secrets used by applications, containers, and automation tools. It provides authentication, policy-based authorization, and secure secrets retrieval across a range of authenticator types (API key, LDAP, OIDC, Kubernetes, Azure, GCP, IAM, JWT).
This project provides OpenAPI specs for automating against Conjur's REST API via an Integration Model. Conjur's own API is already a narrow, single-purpose secrets-management surface; the -latest spec additionally trims a handful of generic diagnostic/introspection endpoints — see OpenAPIs below.
| Asset | Description |
|---|---|
| OpenAPIs/ | Conjur REST API OpenAPI spec — -latest plus the full dated version |
| Requirement | Version |
|---|---|
| Itential Platform | 6.x |
| CyberArk Conjur | 5.3.2 (see OpenAPIs below for exact spec version available) |
| Conjur Integration Model | Required to build automation against the OpenAPI spec |
Import the OpenAPI spec from OpenAPIs/ as an Integration Model in Admin > Integrations, then create an integration pointing at your Conjur instance.
Authentication uses HTTP Basic auth with a Conjur username and password (users) or API key (hosts and users):
Authorization: Basic <base64(username:password_or_api_key)> Conjur also exposes dedicated authenticator endpoints (/authn, /authn-ldap, /authn-oidc, /authn-k8s, /authn-azure, /authn-gcp, /authn-iam, /authn-jwt) that exchange credentials for a short-lived Conjur access token, which can then be used for subsequent calls. See the spec's /authn/{account}/login and /authn/{account}/{login}/authenticate operations for details.
The instance's authentication/server properties should look like this once configured:
{
"authentication": {
"basicAuth": {
"username": "<your-username>",
"password": "<your-password>"
}
},
"server": {
"protocol": "https",
"host": "<your-host>",
"base_path": ""
}
} | Spec | Version | Operations | Description |
|---|---|---|---|
conjur-latest.json | latest (curated) | 34 | Trimmed to 34 of 38 upstream operations — see breakdown below |
conjur-5.3.2.json | 5.3.2 | 38 | Full spec for Conjur Open Source 5.3.2. |
conjur-latest.jsonTrimmed to 34 of 38 upstream operations (x-vendor-api-version: 5.3.2). Conjur's API is already a narrow, single-purpose secrets-management surface, but the upstream spec mixes in a small "status" group of generic diagnostic/introspection endpoints alongside the real authentication/secrets/policy/role automation surface. Excludes:
GET /authenticators — lists which authenticator types are installed/configured/enabled on the server (a static server-capability listing, not a resource you create/read/update/delete)GET /authn-gcp/{account}/status and GET /{authenticator}/{service_id}/{account}/status — "is this authenticator service configured properly" diagnostic/health checks, not status of an action you triggered via this APIGET /whoami — self-introspection endpoint that reports the calling client's identity/IP/user-agent, not a business resourceOperations included, by category:
service_id)conjur-5.3.2.jsonFull, unmodified vendor spec for Conjur Open Source 5.3.2 (38 operations) — the vendor's complete API surface, preserved as-is. See conjur-latest.json above for the curated subset if you just need common CRUD automation.