Receiving the following error when trying to use the Credential Path option for Password value in AD connector .
ERROR:
We have detected an error from the managed system.
Error Received:
java.lang.RuntimeException: java.io.FileNotFoundException: /opt/sailpoint/ccg/lib/custom/xxxx.identitynow.com.pfx (No such file or directory)
I have followed the document and I have configured my CCP (cyberark) in my SailPoint ISC tenant alongside my company’s CyberArk team. I have followed all the pre-requisites. and created credential provider and mapped in the source.
We have tested the CyberArk credentials are successfully retrieved using rest API call. but for some reason the VA is not recognising the certificate.
I am unable to manually copy the files on the location highlighted in error as CCG is not allowing to create new folder on VA.
Hi @PushparajBendigoBank are both CCP and AD source associated with the same virtual appliance cluster?
And does the ‘Certificate File Name’ value in connection settings page exactly match the pfx file name that is uploaded in the base configuration page?
That error is pretty telling — the VA is looking for the .pfx at /opt/sailpoint/ccg/lib/custom/ but it’s not there. The cert file doesn’t get placed there automatically; it has to be uploaded through ISC itself, not manually dropped on the VA filesystem (and yeah, you can’t SSH in and create folders there, that’s by design).
A few things worth checking:
1. Did you upload the cert through ISC admin, not directly to the VA?
Go to Admin > Credential Provider > your CyberArk config > upload the .pfx there. That’s what actually pushes it to the right path on the VA.
2. Filename match
What Chirag pointed out is important — the “Certificate File Name” field in the connection settings has to match the filename you uploaded exactly, including case. Even a minor mismatch throws this error.
3. Same VA cluster
CCP source and your AD source need to be on the same VA cluster, otherwise the cert is on a different node and the AD connector can’t reach it.
4. VA restart after upload
We ran into a case where the cert was uploaded correctly but the VA needed a restart before it actually showed up on the filesystem. Worth trying if everything else looks right.
The REST API working independently just means CyberArk’s side is fine — the issue is purely the VA not having the cert file at the path it expects