Where is the Logic for Fetching Credentials from External Vaults in Discovery? (SNMPv3 Issue)

[Raj Abhishek]

Hi Community,

I’m trying to understand where the code or logic resides within ServiceNow Discovery that fetches credentials from an external credential vault.

Background:
I’m troubleshooting an issue with SNMP device classification. When using SNMP credentials stored in an external vault, Discovery returns the following error:
No enum constant com.snc.core_automation_common.credentials.SnmpV3SecurityProtocol.AuthProtocol.SHA1 at java.base/java.lang.Enum.valueOf(Enum.java:273) at com.snc.core_automation_common.credentials.SnmpV3SecurityProtocol$AuthProtocol.valueOf(SnmpV3SecurityProtocol.java:6)

However, when I create the same SNMP credential locally in ServiceNow, Discovery works as expected.

Additional Details:

• The external SNMP credential works for one specific IP, but fails for other network devices (routers, switches, etc.).
• Load balancers are discoverable using the external credential.
• SNMP Walk from the MID server with the same credentials/auth protocols is successful for all devices.

Question:
Given this behavior, I’d like to understand how Discovery retrieves SNMP credentials from the external vault. Is there documentation or code (such as scripts, MID server Script files) that details this process? I want to determine whether there’s a difference in how credentials are fetched or formatted between local and external sources that could explain this issue.

Any guidance or pointers to relevant documentation would be greatly appreciated.

Thank you!