Delinea Secret Server Integration Fails – MID Server Credential Resolution Returns Username as Null

[khaires750]

Hi all,

We're facing an issue with Delinea Secret Server integration in our ServiceNow instance. Credential resolution via the MID Server is failing for both SSH and Windows credentials.

Setup:

1. Vault Provider: Delinea Secret Server
2. MID Server: Accesses Secret Server via browser, outbound traffic uses proxy
3. Credential Types: SSH and Windows
4. Credentials: Valid and present in Secret Server
5. Vault Config: Lookup by credential_id using standard Delinea connector

Issue:

Credential tests are failing with "username is null", leading to authentication failure.

SSH Error Log:
SSHSessionFactory: Authentication failed with error: Failed to authenticate with user: null

Windows Error Log:
PowerConsole: execute($env:SNC_username = "")

Resolver Debug Log:
Calling CredentialResolver for Credential(8888)... Problem resolving the Credential(null): Unable to fetch credential from Secret Server for id 8888

Troubleshooting Performed:

1. MID can access Secret Server via browser
2. Proxy is configured for outbound traffic
3. Verified lookup key and credential IDs
4. Tried search by name on MID
5. Verified credentials are valid outside ServiceNow
6. Vault config is active in instance

Questions:

1. Could the proxy be blocking API calls to Secret Server?
2. How can we confirm what the Delinea resolver is returning (especially username)?
3. Are there logs or settings to verify field mapping from Secret Server to ServiceNow?
4. Is there a way to enable debug logging of the API response from Delinea?

[CamC]

We're experiencing something similar.

I'll get the details and add them to this thread.

Thanks for flagging.