External Credential Resolver Debugging - Support and Troubleshooting

External Credential Resolver Debugging External Credential Resolver Debugging: External credential resolver resolves credential from CyberArk password vault or other external credential storage vault. We need to follow certain steps to work through this which is documented here . Some common errors and resolutions in below table

Error message in mid server agent log Potential problem Resolution Problem with client's CredentialResolver: unable to resolve the external credential API resolve() method, has the Jar file been added to the MID Server? External CredentialResolver jar is not uploaded or jar is not created in recommended format Need to upload external credential jar Mid Server -> Jar Files Create new jar file entry and attach custom external credential jar SEVERE *** ERROR *** Problem with client's CredentialResolver: java.lang.ClassNotFoundException: com.snc.discovery.CredentialResolver External CredentialResolver jar is not uploaded or jar is not created in recommended format Need to upload external credential jar Mid Server -> Jar Files Create new jar file entry and attach custom external credential jar CyberArk Specific The required jar file, , was not found, please verify it has been uploaded to the instance or refer to the CyberArk integration documents on the ServiceNow wiki. java.lang.NoClassDefFoundError: javapasswordsdk/exceptions/PSDKException JavaPasswordSDK.jar is not uploaded to mid server Need to upload JavaPasswordSDK.jar to instance Mid Server -> Jar Files Create new jar file entry and attach JavaPasswordSDK.jar and save CyberArk Specific

The safe name must not be null or empty. Either enter the name of the safe in the MID config.xml file or specify the Credential ID in the format SAFENAME:CREDID in the discovery credential form

Safe name and safe folder is not provided in credential id or config.xml

Need to review credential id or config.xml for safe folder and safe name parameter.