Enable CyberArk Central Credential Provider (CCP) Integration in Zurich Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Problem After installing the "External Credential Storage and Management Application" (Store App) version 1.3.1 on a Zurich family release instance, customers cannot fetch credentials from CyberArk Central Credential Provider (CCP) vault because the "Lookup key" field is not visible in the discovery_credentials configuration form. When selecting "CyberArk CCP" as the "Credential storage vault" option, the "Lookup key" field remains hidden, preventing users from specifying the credential identifier needed for CCP integration. Root Cause The Zurich family release is missing a client-side script change that dynamically toggles the visibility of the "Lookup key" field based on the selected "Credential storage vault" value. This script is required to show the "Lookup key" field when "CyberArk CCP" is selected. The Australia family release includes this script by default, which is why the feature works correctly there. Solution ServiceNow has provided an Update Set that adds the missing client script change to the Instance. This Update Set enables the dynamic field visibility toggle for CyberArk CCP integration. Prerequisites Zurich family release instance"External Credential Storage and Management Application" (Store App) version 1.3.1 or later installedAdministrative access to apply Update Sets Resolution Steps Step 1: Download the Update Set Update Set: sys_remote_update_set_f58307026d713e10f87767a65204dd6e.xmlDownload the Update Set provided in this KB article. The Update Set file contains the client script change required for CyberArk CCP integration. Step 2: Import the Update Set Navigate to System Update Sets > Retrieved Update Sets in your Zurich instanceClick Import Update Set from XMLSelect the downloaded Update Set fileClick Upload Step 3: Preview the Update Set Open the imported Update SetClick Preview Update Set to review the changesClick Close when preview is complete Step 4: Commit the Update Set Open the Update SetClick Commit Update SetWait for the commit process to completeVerify the success message Step 5: Verify the Fix Navigate to the credential configuration form where you select "Credential storage vault"Select "CyberArk CCP" from the "Credential storage vault" dropdownVerify that the "Lookup key" field is now visibleThe field should remain hidden when other vault types are selected, except "CyberArk CCP" & "CyberArk" Limitations SNMPv3 credentials are not supported via CyberArk CCP in the Zurich family release. Customers cannot fetch SNMPv3 credential types from CyberArk vault using CCP. This limitation does not apply to the Australia family release. Additional Notes This Update Set is only required for Zurich family release instancesAustralia family release includes this functionality by defaultEnsure Store App version 1.3.1 is installed before applying this Update SetNo configuration changes are required after applying the Update Set