- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
10-06-2025 06:10 PM
Hi all,
I went through some of the documents with respect to SNOW integration and could not get info on the below
1) To validate if the ‘Username’ validation can be updated to ‘Assigned to’ for CHG and INC, instead of ‘Requested by’ or ‘Caller’.
2) Online examples show the API call from CyberArk is using basic authentication. We cannot enable API access using basic auth without appropriate risks being raised and approved. Is there any additional auth is permitted like OAUTH2 or Mutual Auth etc?
Documents referenced:
https://community.cyberark.com/s/article/CyberArk-Integration-with-ServiceNow-Ticketing-System
Regards,
Ferro
10-06-2025 10:51 PM
Hi @Froz Abdul Wahab Ameer Ahamed
You are right. In my understanding also it’s not with supported the native OOTB CyberArk DLL.
The component that handles the ticket validation which is a DLL file that makes the REST API call to ServiceNow is not customizable. The validation logic is hardcoded to check the
Requested By CHG or INC.
Please engage CyberArk counterpart and you can request to their Plugin development team to customize the module.
The self-hosted OOTB Ticketing Integration only supports Basic Authentication.
Again, please check with the Plugin development team if authentication method can be changed in a custom module.
Hope it helps !
10-06-2025 10:56 PM
1) To validate if the ‘Username’ validation can be updated to ‘Assigned to’ for CHG and INC, instead of ‘Requested by’ or ‘Caller’.
In case of change ticket, its validate if username requesting the connection is also having change ticket requested by him.
in case of incident ticket, its validate if username requesting the connection is also matching with assigned to filed of the ticket used by him.
2) Online examples show the API call from CyberArk is using basic authentication. We cannot enable API access using basic auth without appropriate risks being raised and approved. Is there any additional auth is permitted like OAUTH2 or Mutual Auth etc?
The API authentication done using the JWT and there is no flexibility for changing it as of now.
You can develop your own code to fullfill required business requirement
10-06-2025 10:56 PM
1) To validate if the ‘Username’ validation can be updated to ‘Assigned to’ for CHG and INC, instead of ‘Requested by’ or ‘Caller’.
In case of change ticket, its validate if username requesting the connection is also having change ticket requested by him.
in case of incident ticket, its validate if username requesting the connection is also matching with assigned to filed of the ticket used by him.
2) Online examples show the API call from CyberArk is using basic authentication. We cannot enable API access using basic auth without appropriate risks being raised and approved. Is there any additional auth is permitted like OAUTH2 or Mutual Auth etc?
The API authentication done using the JWT and there is no flexibility for changing it as of now.
You can develop your own code to fullfill required business requirement
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

