[ZBXNEXT-9077] CyberArk Integration custom endpoint Created: 2024 Mar 12  Updated: 2024 Aug 10  Resolved: 2024 Jun 07

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Server (S)
Affects Version/s: 6.4.12, 7.0 (plan)
Fix Version/s: 7.0.0rc1, 7.0 (plan)

Type: New Feature Request Priority: Minor
Reporter: Ilja Fedotjevs Assignee: Vladislavs Sokurenko
Resolution: Fixed Votes: 1
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Attachments: File Re Zabbix CyberArk integration.msg    
Issue Links:
Duplicate
is duplicated by ZBXNEXT-7737 Zabbix integration with Vault Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
ZBXNEXT-9104 Frontend changes to CyberArk configur... Specification change (Sub-task) Closed Dmitrijs Fofanovs  
Epic Link: Zabbix 7.0
Sprint: Prev.Sprint, S24-W14/15, S24-W16/17, S24-W18/19
Story Points: 1

 Description   

Hello,

The Cyberark integration currently points to the url :

https://<cyberark vault server>:<cyberark vault port>/AIMWebService/api/Accounts?<vault path>

It seems like the path that is configured only the default and there can be variations to it with different restrictions etc.

Our internal team has informed us that the they’ll be using the following to create a more secure version of the endpoint that will be the standard going forward:

https://<cyberark vault server>:<cyberark vault port>/AIMWebServiceSecure/api/Accounts?<vault path>

I see that the path is currently hardcoded to be AIMWebService only. Can this be made configurable?

The default could remain AIMWebService but one more configuration parameter could define the vault endpoint if required or there could be an alternate configuration that allows us to define the whole URL instead of supplying it in parts.

The way it is currently, we’d have to update it in the code and recompile.



 Comments   
Comment by Dmitrijs Fofanovs [ 2024 May 03 ]

Available in versions:

Comment by Marianna Zvaigzne [ 2024 Jun 03 ]

Documentation (7.0) updated:

Generated at Thu Apr 24 08:33:13 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.