mirror of
https://github.com/hashicorp/vault.git
synced 2025-08-22 23:21:08 +02:00
0660ea6fac
* 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>
47 lines
2.4 KiB
Plaintext
47 lines
2.4 KiB
Plaintext
---
|
|
layout: docs
|
|
page_title: Vault ServiceNow Credential Resolver
|
|
description: >-
|
|
The Vault Credential Resolver allows ServiceNow MID servers to use Vault as an enterprise-grade external secret store.
|
|
---
|
|
|
|
> [!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.
|
|
|
|
# Vault Credential Resolver
|
|
|
|
ServiceNow® MID servers can use the Vault Credential Resolver to consume secrets
|
|
directly from Vault for the purpose of performing discovery. See
|
|
[installation](/vault/docs/platform/servicenow/installation) and
|
|
[configuration](/vault/docs/platform/servicenow/configuration) for help getting started
|
|
with the Vault Credential Resolver.
|
|
|
|
## Overview
|
|
|
|
ServiceNow uses MID servers deployed inside customer networks to perform
|
|
agent-less discovery of their infrastructure. As infrastructure such as databases
|
|
or servers are discovered, their attributes such as address and software versions
|
|
are stored in a database. Naturally, this process requires a wide array of
|
|
credentials. Customers can use ServiceNow's built-in credential storage, or install
|
|
an external credential resolver to take advantage of their existing enterprise-grade
|
|
secret storage solution.
|
|
|
|
[](/img/servicenow-vault-credential-resolver-diagram.png)
|
|
|
|
The Vault Credential Resolver is one such resolver. The MID server will not
|
|
store or cache any credentials marked as external, and will invoke the
|
|
credential resolver each time it requires credentials.
|
|
|
|
The Vault Credential Resolver is designed to communicate with a Vault Agent
|
|
service installed on the same machine as the MID server. Authentication is
|
|
handled between the Agent and Vault, and Vault Agent also handles caching and
|
|
renewing leased secrets to ensure the load on Vault is minimized.
|
|
|
|
### Features
|
|
|
|
The following features are supported by the Vault Credential Resolver:
|
|
|
|
- KV, Active Directory and AWS secret engines.
|
|
- Communication with Vault via Vault Agent.
|
|
- TLS communication with Vault Agent.
|