CyberArk Credential issue

[VictorS46]

Experiancing error while running discovery schedules. Any insights com.snc.automation_common.integration.exceptions.UnknownException: Cannot invoke "String.equals(Object)" because "vaultProvider" is null

[Mohammed Faazi2]

Hi Victor,

There are few reasons after the Xanadu upgrades.

1. Check if you have upgraded your external credential store plugin with the new management plugin "External Credential Storage and Management Application". Its free and it includes your "External Credential Storage" Plugin.
2. Once done, Go back to your credentials tables where "Active = true and External Credential Store = True". Check for this field called 'Credential Storage Vault'.

3. No field entries matching with the above filter for Credential storage vault, should be left empty. Either you choose CyberArk, HashicorpVault or AzureKeyVault. 

4. Once you set, you should be able to discover as expected or use your integrations using the external credentials. 

P.s. Refer to respective vault configurations to verify/update your FQCN value for the chosen vaults.

Please mark my answers "helpful/solved", if the question is addressed

[akash_jadhav]

I am also facing same issue for one of our Mid Server. Did you find any resolution for the same?

[Mohammed Faazi2]

I did resolve by checking these said steps for vault provider issue. 

The other MID server issues would be identifying where the issue might have occurred. 

Issue between MID server and CyberArk - Check for MID server logs, seek if the request is placed to CyberArk and log step saying 'password retrieved successfully'. If not, then the issue is between MID server. 

If the MID is successful but failing to authenticate, try connecting the target via CyberArk to the target. If CyberArk fails, the credential might be actually failing.