CyberArk authentication is failing due to CyberArk error PDKTU004EIssue CyberArk authentication fails with error PDKTU004E during discovery or while testing credentials. For example: 2022-11-17 17:28:27 (061) Worker-Interactive:CommandPipeline-ff5538a81b9359901e20a8a8b04bcb9e SEVERE *** ERROR *** The specified credential 'CREDENTIAL' does not exist in the specified vault. Specific Error: PDKTU004E Failed to receive data (Reason=[PDKTU003E Connection has been gracefully closed (Rc=[-1])], Rc=[-1]) NOTE: The "specified credential" name will be unique to the name of the credentials that were specified during creation. The key part of the error is CyberArk error PDKTU004E. The secondary error PDKTU003E is informational. ReleaseAll ReleasesCauseCyberArk documentation notes that this issue can be caused by several different problems (see link in Additional Information section below). With regards to ServiceNow, this error is most commonly caused by having a mismatched CyberArk "javaPasswordSDK.jar" jar in the MID Server's "extlib" directory.ResolutionEnsure that the CyberArk credentials work on the Windows host itself ( How to test if the credentials are configured correctly on the CyberArk end? ).Note the size and date of the "javaPasswordSDK.jar" in the MID Server's "agent\extlib" folder versus the one found in the CyberArk folder which is normally located in the Application Identity Manager (AIM) installation directory at "<install_dir>\CyberArk\ApplicationPasswordSdk".Compare the size of the two jar files on the MID Server to the one that was imported to the MID Server during setup of the CyberArk credentials ( Import the CyberArk JAR file ).Sometimes there are multiple CyberArk jar files that have been imported from different versions of CyberArk. Either import the one from AIM folder on the MID Server or if it has already been imported, make it active.Stop the MID Server.Delete the jar file from the MID Server's "agent\extlib" folder just to make sure the directory is clean and that there are no file in use or file permission issues to prevent replacing the incorrect jar file.Restart the MID Server service and check the "agent\extlib" folder to see that the correct JAR was pushed out from the ServiceNow instance to the MID Server.Test the credentials again.Related LinksIf replacing the "javaPasswordSDK.jar" jar with the same one that is in use in the CyberArk client install does not resolve the issue, please refer to the CyberArk documentation for additional suggestions: PDKTU004E Failed to receive data