[Cyberark EPM] Add Support for CyberArk Identity OAuth2 Authentication

[sharad-elastic]

Type of change

• Enhancement

Proposed commit message

cyberark_epm: add support for CyberArk Identity OAuth2 authentication

Add CyberArk Identity as a second authentication method for the 
EPM REST API using the OAuth2 client credentials flow, 
while keeping the existing EPM Logon authentication as the default.

For auth_type: identity, use the CEL OAuth2 client to authenticate 
against the CyberArk Identity token endpoint, skip the EPM Logon call and 
Basic Authorization header, and use epm_server_url as the EPM host.

Add configuration and documentation for Identity ID, Application ID, 
Client ID, Client Secret, and EPM Server URL, including guidance on 
locating these values in Identity Administration.

Add system test coverage for the Identity authentication flow, 
including a TLS-enabled mock token endpoint.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

• [ ]

How to test this PR locally

Related issues

• Closes Add CyberArk Identity (OAuth2) authentication to the CyberArk EPM integration #20230

Screenshots

[github-actions]

Elastic Docs Style Checker (Vale)

Summary: 3 warnings, 2 suggestions found

⚠️ Warnings (3): Fix when the suggestion improves clarity or correctness.

File	Line	Rule	Message
packages/cyberark_epm/_dev/build/docs/README.md	50	Elastic.MenuArrows	Use '→' to separate menu items, not '' or '='. Example: Select Manage index → Add lifecycle policy.
packages/cyberark_epm/_dev/build/docs/README.md	67	Elastic.DontUse	Don't use 'Please'. Choose a more precise or reader-focused term.
packages/cyberark_epm/manifest.yml	138	Elastic.MenuArrows	Use '→' to separate menu items, not '' or '='. Example: Select Manage index → Add lifecycle policy.

💡 Suggestions (2): Optional style improvements. Apply when helpful.

File	Line	Rule	Message
packages/cyberark_epm/_dev/build/docs/README.md	67	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
packages/cyberark_epm/_dev/build/docs/README.md	67	Elastic.Semicolons	Use semicolons sparingly. Consider splitting the sentence or using a comma or conjunction.

---

The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

[elastic-vault-github-plugin-prod]

✅ All changelog entries have the correct PR link.

[infra-vault-gh-plugin-prod]

💚 Build Succeeded

• Buildkite Build
• Commit: 7b33865

History

• 💔 Build #48949 failed c4058e5
• 💔 Build #48948 failed 7fb39a1