401 Unauthorized Error in CyberArk Integration via Credential Alias
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hi everyone,
I am working on integrating ServiceNow with CyberArk using a Credential Alias (External Credential Storage).
I have configured the credential in CyberArk and linked it to a Credential Alias in ServiceNow. The credential is referenced in the REST message used by a flow action.
However, when testing the integration, I am consistently getting the 401 Unauthorized error
Here’s what has been done so far:
• Verified with CyberArk that the Document ID is valid and configured correctly.
• When tested the connection that is using Linux credentials, it worked successfully.
• The issue only occurs for Windows credentials using CyberArk.
• Created and linked the Credential Alias correctly in ServiceNow.
• Confirmed that the ext.cred.safe_name parameter is configured in the MID Server’s config.xml.
Despite these checks, the 401 error persists on both DEV and UAT environments.
Are there any specific configurations required for Windows-based connections compared to Linux when connecting the credentials from cyberArk using the external cred option. and is there a way to enable detailed MID Server debug logs for external credential resolution to identify the root cause?
Any guidance would be appreciated!
#Discovery #Integration
Thanks