HashiCorp Vault Credential Resolver
An external credential resolver using HashiCorp Vault
Install Trend
View Install Data
| Date | Install Count | Change |
|---|---|---|
| 2026-09-09 | 0 | - |
| 134 days of no change | ||
| 2026-04-27 | 119 | -119 |
| 16 days of no change | ||
| 2026-04-10 | 120 | -1 |
| 1 days of no change | ||
| 2026-04-08 | 121 | -1 |
| 2026-04-07 | 125 | -4 |
| 2026-04-06 | 126 | -1 |
| 2026-04-05 | 129 | -3 |
| 2 days of no change | ||
| 2026-04-02 | 131 | -2 |
| 2026-04-01 | 132 | -1 |
| 2 days of no change | ||
| 2026-03-29 | 133 | -1 |
| 1 days of no change | ||
| 2026-03-27 | 134 | -1 |
| 2 days of no change | ||
| 2026-03-24 | 135 | -1 |
| 2026-03-23 | 136 | -1 |
| 21 days of no change | ||
| 2026-03-01 | 137 | -1 |
| 29 days of no change | ||
| 2026-01-30 | 140 | -3 |
| 2026-01-29 | 143 | -3 |
| 3 days of no change | ||
| 2026-01-25 | 144 | -1 |
| 2026-01-24 | 145 | -1 |
| 2026-01-23 | 146 | -1 |
| 3 days of no change | ||
| 2026-01-19 | 147 | -1 |
| 3 days of no change | ||
| 2026-01-15 | 149 | -2 |
| 1 days of no change | ||
| 2026-01-13 | 151 | -2 |
| 5 days of no change | ||
| 2026-01-07 | 154 | -3 |
| 6 days of no change | ||
| 2025-12-31 | 155 | -1 |
| 9 days of no change | ||
| 2025-12-21 | 156 | -1 |
| 5 days of no change | ||
| 2025-12-15 | 158 | -2 |
| 5 days of no change | ||
| 2025-12-09 | 159 | -1 |
| 6 days of no change | ||
| 2025-12-02 | 158 | +1 |
| 50 days of no change | ||
| 2025-10-12 | 157 | +1 |
| 13 days of no change | ||
| 2025-09-28 | 156 | +1 |
| 2025-09-27 | 155 | +1 |
| 9 days of no change | ||
| 2025-09-17 | 154 | +1 |
| 6 days of no change | ||
| 2025-09-10 | 153 | +1 |
| 24 days of no change | ||
| 2025-08-16 | 152 | +1 |
| 4 days of no change | ||
| 2025-08-11 | 151 | +1 |
| 3 days of no change | ||
| 2025-08-07 | 150 | +1 |
| 2025-08-06 | 149 | +1 |
| 7 days of no change | ||
| 2025-07-29 | 148 | +1 |
| 2025-07-28 | 147 | +1 |
| 2025-07-27 | 145 | +2 |
| 4 days of no change | ||
| 2025-07-22 | 144 | +1 |
| 5 days of no change | ||
| 2025-07-16 | 143 | +1 |
| 1 days of no change | ||
| 2025-07-14 | 142 | +1 |
| 72 days of no change | ||
| 2025-05-02 | 141 | +1 |
| 1 days of no change | ||
| 2025-04-30 | 138 | +3 |
| 2025-04-29 | 137 | +1 |
| 11 days of no change | ||
| 2025-04-17 | 135 | +2 |
| 6 days of no change | ||
| 2025-04-10 | 134 | +1 |
| 2025-04-09 | 133 | +1 |
| 22 days of no change | ||
| 2025-03-17 | 132 | +1 |
| 24 days of no change | ||
| 2025-02-20 | 131 | +1 |
| 20 days of no change | ||
| 2025-01-30 | 130 | +1 |
| 19 days of no change | ||
| 2025-01-10 | 129 | +1 |
| 71 days of no change | ||
| 2024-10-30 | 120 | +9 |
About
HashiCorp Vault is a tool for securely accessing secrets. A secret is anything that you want to tightly control access to, such as API keys, passwords, or certificates. Vault provides a unified interface to any secret, while providing tight access control and recording a detailed audit log.
A modern system requires access to a multitude of secrets: database credentials, API keys for external services, credentials for service-oriented architecture communication, etc. Understanding who is accessing what secrets is already very difficult and platform-specific. Adding on key rolling, secure storage, and detailed audit logs is almost impossible without a custom solution. This is where Vault steps in.
Key Features
ServiceNow® MID servers can use the Vault Credential Resolver to consume secrets directly from Vault for the purpose of performing discovery.
The following features are supported by the Vault Credential Resolver:
- KV (v1 & v2), Active Directory and AWS secret engines.
- Communication with Vault via Vault Agent.
- TLS communication with Vault Agent.