CyberArk Connection Fails Due to External Configuration Issue<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Issue The integration with CyberArk fails even though the configuration inside ServiceNow appears correct. Symptoms Discovery or credential tests fail when attempting to use the CyberArk credential. The instance reports authentication or retrieval errors, but no issues are found in the ServiceNow configuration. Admin users confirm that the credential record, target, and settings appear properly configured. Facts CyberArk integrations depend on configurations maintained outside of ServiceNow. If the external CyberArk setup is incorrect or incomplete, ServiceNow cannot retrieve or use the credential even when the internal setup is correct. This scenario produces integration failures that cannot be resolved from within the platform. Release Observed across all supported releases using CyberArk as an external vault source. Cause The root cause is an external configuration mismatch within CyberArk. Common examples include incorrect policies, account placement, permission issues, or missing access rights required for ServiceNow to retrieve the password. Because the issue is external, ServiceNow displays the symptoms but cannot correct the source of the problem. Resolution Work with the CyberArk team to review the account configuration, policy placement, and access rules. Confirm that the ServiceNow application or integration user has the correct rights to retrieve the credential. After CyberArk corrects the configuration, retest the credential from ServiceNow. The connection succeeds once the external configuration is aligned properly.