From 52d35cdf6518705df346a4c8d9ca410d6a317ef2 Mon Sep 17 00:00:00 2001
From: Adam Rowan <92474478+bear359@users.noreply.github.com>
Date: Thu, 13 Jun 2024 17:33:56 -0600
Subject: [PATCH] Update configuration.mdx (#27497)

Adding SNMPv3 fields to credential resolver documentation.
---
 .../docs/platform/servicenow/configuration.mdx | 18 +++++++++++++++++-
 1 file changed, 17 insertions(+), 1 deletion(-)

diff --git a/website/content/docs/platform/servicenow/configuration.mdx b/website/content/docs/platform/servicenow/configuration.mdx
index 155653f3d2..9d05a9f91a 100644
--- a/website/content/docs/platform/servicenow/configuration.mdx
+++ b/website/content/docs/platform/servicenow/configuration.mdx
@@ -60,7 +60,7 @@ resolver validates that a username and password are present for:
 * vmware
 * windows
 
-And the credential resolver expects the following types to specify at least
+The credential resolver expects the following types to specify at least
 a username and a private key:
 
 * api_key
@@ -70,6 +70,22 @@ a username and a private key:
 * sn_disco_certmgmt_certificate_ca
 * ssh_private_key
 
+For SNMPv3 credentials, the credential resolver can accept up to five values:
+
+* username
+* auth-protocol
+* auth-key
+* privacy-protocol
+* privacy-key
+
+Depending on the configuration of the SNMP endpoint, the username at least will always be required. See below for different SNMP endpoint configurations:
+
+Level         | Authentication | Encryption | What Happens
+--------------|----------------|------------|------------------------
+noAuthNoPriv  | Username       | None       | Username match for auth
+authNoPriv    | MD5 or SHA     | None       | Auth based on HMAC-MD5 or HMAC-SHA algorithms
+authPriv      | MD5 or SHA     | DES        | Auth based on HMAC-MD5 or HMAC-SHA algorithms; provides DES 56-bit encryption based on (CBC)-DES (DES-56) 
+
 ### Configuring the resolver to use a secret
 
 In the ServiceNow UI: