CyberArk CCP + rConfig · Early accessrConfigpaloaltonetworks.com ↗

CyberArk is now Idira. rConfig works with your CCP either way.

CyberArk is now part of Palo Alto Networks and sold as Idira. The Central Credential Provider (CCP) kept its name and its API.

rConfig's key vault integration talks to that CCP API, so it works with the CyberArk CCP deployments you run today and with Idira.

STATUS · EARLY ACCESS

CyberArk CCP support is new in rConfig V8.4.2.

Early access. This integration is built from Palo Alto Networks' published API documentation and follows its documented request and response formats. Environments vary, so we’d welcome your feedback as you roll it out. If anything behaves differently in your deployment, contact rConfig support and we’ll work through it with you.

THE RENAME

The name changed. The CCP API did not.

  • CyberArk is now Idira, from Palo Alto Networks.
  • The Central Credential Provider kept its name.
  • The CCP REST API is the one rConfig calls.

rConfig asks CCP for a device account at connection time, with GET {CCP address}/AIMWebService/api/Accounts and your Application ID, Safe and Object. CCP kept that API through the rename, so the integration works with existing CyberArk CCP deployments and with Idira.

See how the Idira (CyberArk) integration works

WHAT YOU NEED

What rConfig needs from your CCP.

  • The CCP address.
  • An Application ID for rConfig.
  • A client certificate, if CCP uses mutual TLS.
  • A Safe and Object for each credential set.

Self-hosted PAM and Privilege Cloud deployments that expose CCP both work, with no agent on the rConfig server. Conjur, the agent-based Credential Provider and the SDKs are out of scope.

Palo Alto Networks, Idira and CyberArk are trademarks of their owners. This integration is not endorsed by Palo Alto Networks.

FAQ

CyberArk and rConfig: common questions

The short answers. The Idira (CyberArk) page has the full setup and FAQ.

Is CyberArk the same as Idira?

CyberArk is now part of Palo Alto Networks and sold as Idira. The Central Credential Provider (CCP) kept its name and API.

Does rConfig work with my existing CyberArk CCP?

Yes. rConfig uses the CCP REST API, so the integration works with existing CyberArk CCP deployments and with Idira.

Which part of CyberArk does rConfig use?

Only the Central Credential Provider REST API. Conjur, the agent-based Credential Provider and the SDKs are out of scope.

Which rConfig version do I need?

rConfig V8.4.2 or later, where the integration is in early access. Key vault integrations are included in V8 Pro Starter and every plan above it.

The full setup is on the Idira (CyberArk) page.

How rConfig connects to CCP, maps accounts to credential sets and reads device passwords at connection time, with the full FAQ and spec.

Read the documentation