BeyondTrust Password Safe Integration with ServiceNow Discovery Failing: Empty MID Server Response

[harshbhushan]

Hi Community,

I am currently stuck trying to set up the BeyondTrust Credential Storage (Password Safe) integration with ServiceNow Discovery. I followed the official BeyondTrust documentation, but every credential test fails with an authentication error.

Both vendor supports are pointing fingers at each other: ServiceNow Now Support states it is a third-party app issue, while BeyondTrust claims the issue lies on the ServiceNow side.

The Error:

When testing the credential, the MID server logs show the following error:

"Cannot process argument because the value of argument "userName" is not valid. Change the value of the "userName" argument and run the operation again."

What I've Discovered So Far:

• According to the BeyondTrust Documentation, the Credential storage vault field should be set to 'BeyondTrust Password Safe' & for testing we can set it to defaults to 'NONE'.
• Even if I manually configure it, it still fails with the same username error.
• During debugging, we noticed that the error triggers because nothing is being returned to the MID server. The MID server attempts to resolve the credential, but the payload comes back empty, leading to the invalid username exception.

My Questions for the Community:

1. Has anyone successfully deployed this specific integration recently and encountered this empty return/username error?
2. Is there a specific JAR file, MID server script include, or property that needs to be updated manually to make the "BeyondTrust Password Safe" option register correctly in the External Credential Storage configuration except the steps in documentation?
3. Are there any hidden network, API account permissions, or certificate requirements on the BeyondTrust side that cause it to silently fail and return an empty response instead of a descriptive error?

Any guidance, troubleshooting steps, or workarounds would be greatly appreciated!

Thanks in advance!