mirror of
https://github.com/hashicorp/vault.git
synced 2025-08-22 23:21:08 +02:00
* Update README Let contributors know that docs will now be located in UDR * Add comments to each mdx doc Comment has been added to all mdx docs that are not partials * chore: added changelog changelog check failure * wip: removed changelog * Fix content errors * Doc spacing * Update website/content/docs/deploy/kubernetes/vso/helm.mdx Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com> --------- Co-authored-by: jonathanfrappier <92055993+jonathanfrappier@users.noreply.github.com> Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>
36 lines
1.9 KiB
Plaintext
36 lines
1.9 KiB
Plaintext
---
|
|
layout: docs
|
|
page_title: Troubleshoot the Vault ServiceNow Credential Resolver
|
|
description: Troubleshooting tips for the Vault ServiceNow Credential Resolver.
|
|
---
|
|
|
|
> [!IMPORTANT]
|
|
> **Documentation Update:** Product documentation, which were located in this repository under `/website`, are now located in [`hashicorp/web-unified-docs`](https://github.com/hashicorp/web-unified-docs), colocated with all other product documentation. Contributions to this content should be done in the `web-unified-docs` repo, and not this one. Changes made to `/website` content in this repo will not be reflected on the developer.hashicorp.com website.
|
|
|
|
# Troubleshoot the Vault ServiceNow Credential Resolver
|
|
|
|
## Check the logs
|
|
|
|
Check the [log files] inside `logs/` in the agent installation folder for logs and
|
|
errors. The resolver logs a line for each credential ID that it successfully
|
|
queries, and also logs the fields that the credentials were extracted from.
|
|
|
|
If a particular credential ID is failing, search for that ID in the logs, and
|
|
check that it is successfully queried and that the credentials were extracted
|
|
from the fields you expected.
|
|
|
|
You will also find any exceptions that the resolver throws in the logs, including
|
|
if it didn't find the minimum set of required fields as specified in
|
|
[configuration](/vault/docs/platform/servicenow/configuration#creating-a-secret-in-vault),
|
|
or if it couldn't communicate with Vault.
|
|
|
|
[log files]: https://docs.servicenow.com/bundle/quebec-servicenow-platform/page/product/mid-server/reference/r_MIDServerTroubleshooting.html
|
|
|
|
## Use the test credential feature
|
|
|
|
When creating or configuring a credential in the ServiceNow UI, you should be
|
|
able to click "Test credential" to perform a quick targeted test. Select the
|
|
MID server that should query Vault, and select a target that the credential
|
|
should work for to check that everything works as expected. If it doesn't, check
|
|
the logs for errors and debug information as detailed above.
|