What authentication does the CyberArk Conjur API use?

An API-key style Authorization header (the ApiKeyAuth scheme). Through Jentic, the key is stored in the encrypted vault and injected at execution time so it never appears in agent prompts or logs.

Can I store and retrieve a secret with this API?

Yes. POST /secrets stores a value and GET /secrets/{id} reads it back. This pair is the minimum surface for replacing hard-coded credentials with a Conjur lookup.

Can I create access policies through the API?

Yes. POST /policies accepts a Conjur policy definition and creates the corresponding resources, roles, and grants. GET /roles confirms the resulting roles exist.

What are the rate limits for the CyberArk Conjur API?

Conjur is typically self-hosted, so rate limits depend on the operator's deployment sizing rather than a vendor-imposed quota. Capacity-plan around concurrent workloads and back off on 5xx responses that signal overload.

How do I retrieve a Conjur secret through Jentic?

Run pip install jentic, search for 'retrieve a secret from Conjur', load the GET /secrets/{id} schema, and execute with the secret id. Jentic handles the API key so your code never holds it directly.

Can I limit what my agent is allowed to do with the CyberArk Conjur API?

Yes. Because you run Jentic One yourself, your own rules decide which Conjur operations the agent may call and which credential it uses. Since the secret id sits in the URL path (GET /secrets/{id}), you can pin the agent to reading one specific secret and exclude everything else, so writing values through POST /secrets or loading policies through POST /policies is not available unless you grant it. The Conjur API key is held by your instance and injected at execution time, so the agent never sees it.