From 6fba65be8bd3d9fe193be76ecc086a14aebe8a07 Mon Sep 17 00:00:00 2001 From: jkaufman-hc Date: Tue, 1 Jul 2025 13:56:17 -0600 Subject: [PATCH] ServiceNow Update to Yokohama work around (#31168) * 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> --- website/content/docs/platform/servicenow/configuration.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/website/content/docs/platform/servicenow/configuration.mdx b/website/content/docs/platform/servicenow/configuration.mdx index 69bef274ad..e6233e64e9 100644 --- a/website/content/docs/platform/servicenow/configuration.mdx +++ b/website/content/docs/platform/servicenow/configuration.mdx @@ -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.