Unable to get CyberArk credentials

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-20-2020 01:20 PM
We are setting up Discovery and using CyberArk in order to pass credentials. I finished setting up the MID server and followed the guide to configure the CyberArk integration, but when I test the credentials I keep getting Authentication Failed. When looking in the logs, it appears it's passing the username for the Safe as an object. I think this is the reason it keeps failing. Has anyone run into this before and know how to fix it?
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-10-2023 08:43 PM
Hi Ashutosh,
I am currently working on SNMP v3 type of devices to discover using cyberArc. For SNMP v3 credential, there are 2 fields "Credential Id" and "Privacy Credential Id". What value to be filled in "Privacy Credential ID".
Which attribute in cyberArc to be filled in?
is there any relation between "Credential Id" and "Privacy Credential Id" in cyberArc?
Even in Servicenow Docs not full details provided. Please assist me on this.
Regards,
Nagarjun S
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-12-2023 10:36 AM
Nagarjun,
We are facing the same issue, did you ever figure this out?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-11-2022 05:27 AM
We are in a similar situation in which the CyberArk APPAudit log is saying the password is successfully fetched but ServiceNow is reporting Credential Not Found.
We have another issue that will crop up once we figure out how to get ServiceNow to consume the fetched credential and use it. The Credential ID for each SSH device is of the format "Prepended_text_"<hostname>"Appended Text". IP Addresses are NOT stored in CyberArk. Therefore, we need to be able to use a variable for the hostname in the Credential ID field of the Credential record.
Before suggesting to use the FQDN, please know that I tried it just to see what got passed and the result was no FQDN.