mirrors/vault
1
0
Fork 0
mirror of https://github.com/hashicorp/vault.git synced 2026-05-05 12:26:34 +02:00
Code Issues Projects Releases Wiki Activity

Update configuration.mdx (#27497)

Browse Source 
Adding SNMPv3 fields to credential resolver documentation.
This commit is contained in:
Adam Rowan 2024-06-13 17:33:56 -06:00 committed by GitHub
parent 99f685743e
commit 52d35cdf65
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 17 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
website/content/docs/platform/servicenow/configuration.mdx
View File

@ -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: