Discovery Credentials
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-22-2024 05:35 AM
How does Credential storage valult work for cyberArk in discovery.?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-22-2024 05:57 AM - edited 05-22-2024 05:58 AM
Check this out : https://www.servicenow.com/community/developer-articles/cyberark-integration-with-servicenow/ta-p/23...
the ServiceNow platform supports the use of the CyberArk vault for external credential storage
The ServiceNow credential application integrates with the CyberArk credential storage. The MID Server integration with CyberArk vault enables orchestration and discovery to run without storing any credentials on the ServiceNow instance.
The instance maintains a unique identifier for each credential, the credential type (such as SSH, SNMP, or Windows), and any credential affinities. The MID Server obtains the credential identifier and IP address from the instance, and then uses the CyberArk vault to resolve these elements into a usable credential.
The CyberArk integration requires the external credential storage plugin, which is available by request.
The CyberArk integration supports these ServiceNow credential types:
- CIM
- JMS
- SNMP community
- SSH
- SSH private key (with key only)
- VMware
- Windows
Regards,
Pratiksha
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-22-2024 06:06 AM
Hi @sadhna ,
The JAR file will communicate with that credential storage system, the mid server will use a pointer, credential ID. The mid server retrieves the credential associated with that credential ID, uses it and returns it back to the external credential storage system. We do not store that credential on the instance nor do we send it to the instance.
☑️ Please mark responses as HELPFUL or ACCEPT SOLUTION to assist future users in finding the right solution....