upstream/vault
1
0
Fork 0
mirror of https://github.com/hashicorp/vault.git synced 2026-02-03 20:40:45 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions 11

ServiceNow Update to Yokohama work around (#31168)

Browse source 
* ServiceNow Update to Yokohama work around

Confirmed Yokohama is compatible with HashiCorp Vault, there is a work around which is listed under the In the ServiceNow UI.

* Update website/content/docs/platform/servicenow/configuration.mdx

Agreed on the suggested modifications.

Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>

---------

Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>
This commit is contained in:
jkaufman-hc 2025-07-01 13:56:17 -06:00 committed by GitHub
parent fef422756e
commit 6fba65be8b
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 4 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
website/content/docs/platform/servicenow/configuration.mdx
View file

@ -99,6 +99,10 @@ In the ServiceNow UI:
1. Choose a type from the list.
1. Select "External credential store".
1. Provide a fully qualified collection name (FQCN):
- **Yokohama or newer**: in the **Credentials** section of the ServiceNow
webpage, select your credentials and click **ⓘ** for the "Credential
Storage Vault" mid server. Click **Open Record** to add the vault resolver
FQCN: `com.snc.discovery.CredentialResolver`
- **Xanadu (Q4-2024) or newer**: use `com.snc.discovery.CredentialResolver`
- **Versions prior to Xanadu (Q4-2024)**: leave blank or use "None"
1. Provide a meaningful name for the resolver.