External Credential test fails: Invalid Target Specified

Not applicable

We have setup External Credentials to use CyberArk and have verified all communication ports between the MID server and our Cyberark instance are open.  We have followed all the documentation steps and are at the point of creating the credential record with the Credential ID we setup in the CyberArk safe but yet when we use that credential to connect to a known server that we can connect directly without the external credential store we get the following failure:

Invalid target specified

We have MID server debugging in place but on the mid server the logs do not show any information about this.

What can we do to figure out how to move past this failure?

9 REPLIES 9

@swarup.devalekar@gmail thanks for the response, but what is the relationship between form view and the operation of sending 'pings' to the target IP? I don't see any - could you please explain? I'm getting an "Invalid target specified" message after clicking the 'TEST credential' UI action. How changing the form view can impact this?

Did you try to telnet from MID server to Target IP on the port 22/135/161

chuckm
Giga Guru

Pavlo, have you validated the Credential ID is formatted properly to reference the credential in the CyberArk Safe?

I posted a detailed example of using the <safe>:<credential ID> format in the Credential ID field in the following community article:

ServiceNow Integration with CyberArk:How to specify credential ID in ServiceNow when multiple host n...

P-Rudenko-SN
ServiceNow Employee
ServiceNow Employee

Finally figured out the reason of the issue, might be useful for others.

The root cause was that after the MID server upgrade, the configuration file 'config.xml' has been replaced with the default one, which did remove the lines that enabled the connectivity between MID and cyberark. We have now put the required lines back, so the connectivity between MID and cyberark is restored.

Hi Pauvlo,

 

could you please confirm what those lines are in the config.xml. 

 

Thanks!