content large_stringlengths 3 20.5k | url large_stringlengths 54 193 | branch large_stringclasses 4
values | source large_stringclasses 42
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
This is an idempotent operation. Vault will not return an error when deleting a policy that does not exist. ## Associating policies Vault can automatically associate a set of policies to a token based on an authorization. This configuration varies significantly between authentication backends. For simplicity, this exam... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/policies.mdx | main | vault | [
0.01499308180063963,
0.025118006393313408,
-0.09435488283634186,
-0.04793350398540497,
0.0332828052341938,
-0.030716951936483383,
0.0760793685913086,
-0.05625615268945694,
0.07298731803894043,
0.010580281727015972,
-0.011588189750909805,
-0.0020108267199248075,
0.09890403598546982,
0.00039... | 0.021695 |
existing plugin | | [sys/raw:path](/vault/api-docs/system/raw) | GET, POST, DELETE | Used to access the raw underlying store in Vault | | [sys/raw:prefix](/vault/api-docs/system/raw#list-raw) | GET, LIST | Returns a list keys for a given path prefix | | [sys/remount](/vault/api-docs/system/remount) | POST | Moves an al... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/policies.mdx | main | vault | [
-0.03800390288233757,
-0.05615466460585594,
-0.10825374722480774,
0.005754867102950811,
-0.015881964936852455,
-0.09379837661981583,
-0.10138434171676636,
0.004568160977214575,
0.0014181133592501283,
0.03400934115052223,
0.0796804428100586,
0.04436320438981056,
0.08985715359449387,
-0.0094... | 0.009766 |
# Mount migration Vault supports moving secrets and auth mounts, both within and across namespaces. The operation is supported by API endpoints and a CLI helper around them. ## Why There can be several reasons for wanting to migrate mounts. In Vault Community Edition, the use cases could be for renaming mounts to align... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/mount-migration.mdx | main | vault | [
-0.012540606781840324,
-0.06584253162145615,
-0.01638805866241455,
-0.016731131821870804,
0.053637947887182236,
-0.08904429525136948,
-0.05747545510530472,
-0.04187550023198128,
0.07224387675523758,
-0.018898332491517067,
0.0463605672121048,
0.017115361988544464,
0.032106418162584305,
0.01... | 0.02305 |
updated to point to the new location of the engine, assuming that the policy is in the target namespace or a parent of the target namespace, or updated to remove the original mount path if not. Any policies associated with roles on a moved auth mount need to be inspected to see if they still refer to valid paths after ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/mount-migration.mdx | main | vault | [
-0.023774661123752594,
-0.03733847662806511,
0.002566014649346471,
-0.011806578375399113,
0.015832265838980675,
-0.0757223516702652,
-0.03729020804166794,
-0.03494180738925934,
0.012688246555626392,
-0.02472219429910183,
0.05014284700155258,
-0.01077210996299982,
0.0476958267390728,
0.0148... | -0.029206 |
# Duration string format Vault uses a unique duration string format as part of its configuration and APIs. This format is used throughout Vault wherever durations are provided. For example, telemetry configuration contains various options using this format, such as `usage\_gauge\_period`, which is the interval of colle... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/duration-format.mdx | main | vault | [
0.0036416309885680676,
0.08611392229795456,
-0.06177555024623871,
-0.036043930798769,
-0.066741444170475,
-0.05486390367150307,
-0.02284814976155758,
0.04809398576617241,
0.08598427474498749,
-0.07262199372053146,
0.03449239954352379,
-0.04828513786196709,
0.022738242521882057,
0.028456306... | 0.086498 |
# "Dev" server mode You can start Vault as a server in "dev" mode like so: `vault server -dev`. This dev-mode server requires no further setup, and your local `vault` CLI will be authenticated to talk to it. This makes it easy to experiment with Vault or start a Vault instance for development. Every feature of Vault is... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/dev-server.mdx | main | vault | [
0.03344973176717758,
-0.014698408544063568,
-0.06658314913511276,
-0.012191105633974075,
-0.03276976943016052,
-0.08407901972532272,
-0.07052507251501083,
0.002016083337366581,
0.026614144444465637,
-0.0018089822260662913,
0.004527293145656586,
0.0172751285135746,
0.07656756788492203,
0.02... | -0.01114 |
# Filter expressions in Vault @include 'alerts/enterprise-only.mdx' Filter expressions use matching operators and selector values to parse out important or relevant information. In some situations, you can use filter expressions to control how Vault processes results. ## Filter expression syntax Basic filter expression... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/filtering.mdx | main | vault | [
-0.03242174908518791,
0.11753331124782562,
-0.031004436314105988,
-0.058912694454193115,
0.05102953687310219,
-0.09717531502246857,
0.04275006055831909,
-0.04833599179983139,
0.056392550468444824,
-0.08654172718524933,
-0.026394525542855263,
-0.030491940677165985,
0.07095380127429962,
0.00... | 0.0505 |
pre-production environments to ensure correctness. Ideally you should [codify your management of Vault](/vault/tutorials/operations/codify-mgmt-vault-terraform) using tools such as [Terraform](https://www.terraform.io/), to prevent accidentally enabling an audit device in a production environment with untested/incorrec... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/filtering.mdx | main | vault | [
0.07230276614427567,
0.04982055723667145,
-0.013923962600529194,
0.007953240536153316,
0.022352218627929688,
-0.10457593202590942,
-0.06311207264661789,
-0.06378081440925598,
0.03504718095064163,
0.03170614317059517,
0.029155077412724495,
-0.007505166810005903,
0.028764652088284492,
0.0380... | -0.001052 |
# Production hardening You can use the best practices in this document to harden Vault when planning your production deployment. These recommendations follow the [Vault security model](/vault/docs/internals/security), and focus on defense in depth. You should follow the \*\*baseline recommendations\*\* if at all possib... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/production-hardening.mdx | main | vault | [
0.03442515432834625,
0.03880375996232033,
-0.04972854256629944,
-0.059160590171813965,
-0.031017066910862923,
-0.061925604939460754,
-0.007585612125694752,
0.04804437980055809,
-0.051285505294799805,
0.021147025749087334,
0.03507310897111893,
0.04076420143246651,
0.0656396821141243,
0.0310... | -0.021714 |
when no longer needed. - \*\*Configure user lockout\*\*. Vault provides a [user lockout](/vault/docs/concepts/user-lockout) function for the [approle](/vault/docs/auth/approle), [ldap](/vault/docs/auth/ldap) and [userpass](/vault/docs/auth/userpass) auth methods. \*\*Vault enables user lockout by default\*\*. Verify th... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/production-hardening.mdx | main | vault | [
0.0033679865300655365,
0.04912080988287926,
-0.06976796686649323,
-0.027537109330296516,
0.05424487963318825,
-0.0017602337757125497,
-0.01518826000392437,
-0.034501560032367706,
0.03322599083185196,
0.004546495620161295,
0.03065255470573902,
0.0646267831325531,
0.025765204802155495,
0.004... | 0.014889 |
malicious Vault plugins. These plugin issues can harm the security posture of your Vault deployment. - \*\*Be aware of non-deterministic configuration file merging\*\*. Vault's configuration file merging is non-deterministic, and inconsistencies in settings between files can lead to inconsistencies in Vault settings. E... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/production-hardening.mdx | main | vault | [
0.0034845897462219,
0.05569811910390854,
-0.08535312861204147,
-0.032807011157274246,
-0.0066075511276721954,
-0.052253324538469315,
-0.03477112203836441,
0.01623830571770668,
0.053048424422740936,
-0.02243983745574951,
0.027916835620999336,
0.03749144449830055,
0.06285262852907181,
0.0208... | -0.018343 |
\*\*Adjust user limits\*\*. It is possible that your Linux distribution enforces strict process user limits (`ulimits`). Consider a review of `ulimits` for maximum amount of open files, connections, etc. before going into production. You might need to increase the default values to avoid errors about too many open file... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/production-hardening.mdx | main | vault | [
0.06782368570566177,
0.006791862193495035,
-0.06984107941389084,
-0.013622335158288479,
-0.00965282041579485,
-0.06275984644889832,
-0.04529157653450966,
0.10256222635507584,
-0.012666369788348675,
-0.007901156321167946,
0.011136743240058422,
0.10357629507780075,
0.00468421308323741,
-0.07... | 0.061922 |
# Certificate counting @include '../partials/alerts/enterprise-only.mdx' Vault Enterprise clusters running v1.21 and later maintain a count of every certificate issued across all mounts of the built-in PKI secrets engine. Vault does not deduplicate certificate counts. For example, if you request two certificates with t... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/certificate-counts.mdx | main | vault | [
0.053044434636831284,
0.024665415287017822,
-0.04290398955345154,
0.020082412287592888,
-0.0076071457006037235,
-0.07980763167142868,
-0.05360721796751022,
0.006446016486734152,
0.108098603785038,
-0.0838470309972763,
-0.01921328343451023,
-0.019172418862581253,
0.12137698382139206,
0.0245... | -0.051623 |
# Tune server performance Vault is a high-performance secrets management and data protection solution capable of handling enterprise-scale workloads. As you scale your usage and adopt broader use cases, you can tune Vault, its underlying operating system, and storage for optimal performance. These guidelines and best p... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/tune-server-performance.mdx | main | vault | [
0.07043860852718353,
0.06681592762470245,
-0.07714100927114487,
-0.03475078567862511,
-0.039567578583955765,
-0.07094530761241913,
-0.052375923842191696,
0.037020809948444366,
-0.06544771045446396,
-0.037642184644937515,
-0.06060640513896942,
0.073244608938694,
0.054264284670352936,
-0.027... | 0.00216 |
at the physical system or virtual machine level are also listed here for your reference. | Component | Tools | Notes | | ----------- | ------------------------------------ | --------------------------------------------------------------------------------------------------------- | | \*\*CPU\*\* | dstat, htop, lscpu, sa... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/tune-server-performance.mdx | main | vault | [
-0.0752200111746788,
-0.020089825615286827,
-0.1907709836959839,
0.021997587755322456,
-0.023423010483384132,
-0.11968719214200974,
-0.01015070267021656,
0.0946887657046318,
-0.06218157708644867,
-0.00825312826782465,
0.0227039884775877,
-0.0022587671410292387,
0.01237670611590147,
-0.0651... | 0.258185 |
and for representing socket connections established to other network hosts. The value of maximum open files allowed to the Vault process is a critical user limit that you should appropriately tune for ideal performance. \*\*How to measure usage?\*\* To inspect the current maximum open files values for the vault process... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/tune-server-performance.mdx | main | vault | [
0.09348421543836594,
-0.022547028958797455,
-0.13825088739395142,
-0.049308355897665024,
-0.01442740485072136,
-0.08803050965070724,
-0.043753497302532196,
0.07453510910272598,
0.049961965531110764,
0.011768050491809845,
-0.03259972482919693,
0.05053071677684784,
0.017051516100764275,
-0.0... | 0.039417 |
that the kernel enforces and that user programs like Vault can't exceed. Note that this value is dynamically set at boot time and varies depending on the physical computer system characteristics, such as available physical memory. To check the current system-wide maximum open files value for a given system, read it fro... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/tune-server-performance.mdx | main | vault | [
0.04190925508737564,
-0.003148972988128662,
-0.09520228207111359,
-0.06124400347471237,
0.00590502517297864,
-0.09049554169178009,
-0.06106261536478996,
0.135732963681221,
0.021418679505586624,
0.023695621639490128,
-0.016110220924019814,
0.08894088119268417,
0.030392847955226898,
0.007400... | -0.004757 |
interrupts by the network interface, etc. This behavior may not represent a large toll on the CPU in terms of real CPU utilization, but it can impair I/O. Each time a goroutine blocks for I/O (or gets preempted due to an interrupt) it can take longer each time before that goroutine is back in service. You should keep t... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/tune-server-performance.mdx | main | vault | [
0.07212572544813156,
0.03127456083893776,
-0.04450139030814171,
0.02681824006140232,
-0.03197115659713745,
-0.12454263120889664,
0.011544793844223022,
-0.0008281345362775028,
0.026567114517092705,
-0.03073064237833023,
0.007204901892691851,
0.08993236720561981,
-0.04781613498926163,
-0.027... | 0.028542 |
value of \*\*http\_read\_header\_timeout\*\* is 0, Vault uses the value of \*\*http\_read\_timeout\*\*. If both values are 0, there is no timeout. Default value: \*\*10s\*\* (10 seconds) #### http\_read\_timeout You can use the [http\_read\_timeout](/vault/docs/configuration/listener/tcp#http\_read\_timeout) parameter ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/tune-server-performance.mdx | main | vault | [
0.040979884564876556,
0.11248070746660233,
-0.07621005922555923,
-0.010804716497659683,
-0.06248258426785469,
-0.09734290093183517,
-0.08684336394071579,
-0.0017751050181686878,
0.07245389372110367,
-0.005732327233999968,
-0.021382439881563187,
0.003809507703408599,
0.02112201601266861,
-0... | -0.029469 |
by default. Read the [Performance Standby Nodes](/vault/tutorials/enterprise/performance-standbys) tutorial to learn more. While there are no tunable parameters available for performance standby functionality, some use cases can require that they be entirely deactivate. If necessary, you can use the [disable\_performan... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/tune-server-performance.mdx | main | vault | [
0.052906353026628494,
0.0019113749731332064,
-0.09966310858726501,
0.0068390220403671265,
-0.02205333113670349,
-0.043297234922647476,
-0.058988746255636215,
-0.03019609861075878,
0.02318681590259075,
0.0036492871586233377,
-0.04985007643699646,
0.11157210916280746,
0.040188033133745193,
-... | 0.05293 |
servers, you can then increase the `logshipper\_buffer\_size` value. You can adjust the `logshipper\_buffer\_length` value to handle anticipated increases in namespace usage. For example, if your deployment uses several hundred namespaces, but your plans are to soon expand to 3000 namespaces, then you should increase `... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/tune-server-performance.mdx | main | vault | [
0.060161933302879333,
-0.034594323486089706,
-0.020906755700707436,
-0.0417548269033432,
-0.0644516870379448,
-0.10844758152961731,
-0.057014502584934235,
0.004271689802408218,
0.017655299976468086,
-0.011237137950956821,
-0.039662543684244156,
0.03039873018860817,
0.05396163463592529,
0.0... | -0.018953 |
a CRL, you should define your roles to use the [no\_store](/vault/api-docs/secret/pki#no\_store) parameter. Vault cannot list or revoke certificates generated from roles that define the `no\_store` parameter. ### ACLs in policies If your goal is to optimize Vault performance as much as possible, you should analyze your... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/tune-server-performance.mdx | main | vault | [
0.030296778306365013,
0.1160227432847023,
-0.0672004222869873,
-0.014537372626364231,
-0.004685404244810343,
-0.06098291277885437,
0.013634026981890202,
-0.002516516949981451,
0.036604996770620346,
-0.01920151896774769,
0.011817815713584423,
-0.01105516403913498,
0.09097520262002945,
0.045... | -0.066227 |
request | Write new token to the Token Store Write new lease to the Lease Store | | Revoke token (or token expiration) | Delete token Delete token lease Delete all child tokens and leases | [Batch tokens](/vault/docs/concepts/tokens#batch-tokens) are encrypted blobs that carry enough information for Vault to use them f... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/tune-server-performance.mdx | main | vault | [
-0.025654029101133347,
0.04252922162413597,
-0.038042813539505005,
0.005576422903686762,
-0.06334478408098221,
-0.013937772251665592,
0.009363299235701561,
0.013482239097356796,
0.04930051788687706,
-0.011587407439947128,
0.04942142963409424,
0.04498382657766342,
0.05374438315629959,
0.009... | 0.025834 |
for storage, most of the disk I/O work falls on Consul servers, and Vault itself has much lower disk I/O usage in comparison. Consul keeps its working set in memory. As a general rule of thumb, the Consul server should have physical memory equal to about 3x the working data set size of the key/value store containing Va... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/tune-server-performance.mdx | main | vault | [
0.05588987469673157,
0.0210395697504282,
-0.06830935180187225,
0.003708224045112729,
-0.008146945387125015,
-0.14341561496257782,
-0.06363093852996826,
0.11035498976707458,
0.05376565828919411,
0.03838937729597092,
0.01664416491985321,
0.07820242643356323,
0.04553016647696495,
0.0067639341... | 0.050007 |
specifies the maximum number of parallel requests Vault can make to Consul. The default value is \*\*128\*\*. This value is not typically increased to increase performance, rather it is most often called upon to reduce the load on an overwhelmed Consul cluster by dialing down the default value. #### consistency\_mode V... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/tune-server-performance.mdx | main | vault | [
-0.002854025922715664,
-0.02487916499376297,
-0.08442063629627228,
-0.01124092098325491,
-0.06888888031244278,
-0.10044398903846741,
-0.08897082507610321,
0.03034987300634384,
0.06871305406093597,
0.013564441353082657,
0.028509128838777542,
0.0686507523059845,
0.027520177885890007,
0.00197... | 0.02787 |
the Integrated Storage to scale key Raft algorithm timing parameters. The default value is \*\*0\*\*. Tuning this affects the time it takes Vault to detect leader failures and to perform leader elections, at the expense of requiring more network and CPU resources for better performance. By default, Vault will use a low... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/tune-server-performance.mdx | main | vault | [
0.03509993106126785,
0.02891213819384575,
-0.09008150547742844,
-0.04929843917489052,
-0.028145698830485344,
-0.10701049864292145,
-0.08374105393886566,
0.04953733831644058,
0.04481731727719307,
0.011161038652062416,
0.015100816264748573,
0.04444288834929466,
0.028622720390558243,
-0.00069... | -0.01165 |
Linux profiling with performance counters](https://perf.wiki.kernel.org/) - [The Go Memory Model](https://golang.org/ref/mem) - [Package runtime](https://golang.org/pkg/runtime/) - [Goroutines](https://golang.org/doc/effective\_go.html?h=goroutine#goroutines) - [vault.expire.num\_leases metric](/vault/docs/internals/te... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/tune-server-performance.mdx | main | vault | [
-0.013919311575591564,
0.03907660022377968,
-0.12033718824386597,
0.0036558581050485373,
-0.016293654218316078,
-0.06930868327617645,
-0.013281373307108879,
0.07958138734102249,
0.0030779012013226748,
-0.06889783591032028,
0.06814247369766235,
0.0003747433074750006,
0.02767326682806015,
0.... | 0.119818 |
# Seal/Unseal When you start a Vault server, it starts in a sealed state. In this state, Vault can access the physical storage, but it cannot decrypt any of the data on it. Unsealing is the process of obtaining the plaintext root key that is necessary to read the decryption key. Prior to unsealing, the only possible Va... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/seal.mdx | main | vault | [
0.024106355383992195,
0.007828710600733757,
-0.03454197943210602,
0.005499676335602999,
0.012870647944509983,
-0.04540535807609558,
-0.045728184282779694,
-0.014812245033681393,
0.07931685447692871,
-0.027554523199796677,
-0.017030779272317886,
0.09843210130929947,
0.02312907576560974,
-0.... | -0.002851 |
or service and prompts it to decrypt the root key from storage.  There are certain Vault operations besides unsealing that require a quorum of users to perform, for example, generating a root token. When you use a Shamir seal, you must provide the unseal keys to authorize these... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/seal.mdx | main | vault | [
-0.044499196112155914,
0.03626979514956474,
-0.033491309732198715,
-0.023954175412654877,
-0.0012838318943977356,
-0.05887223407626152,
-0.050931718200445175,
0.024523615837097168,
0.06841016560792923,
-0.013846011832356453,
0.007864389568567276,
0.10198494791984558,
0.056611090898513794,
... | 0.027037 |
Refer to [Configuration](/vault/docs/configuration/seal/pkcs11) for more details. ### Rekeying #### Unseal key You can rekey Vault's unseal keys using a `vault operator rekey` operation from the CLI or the matching API calls. Vault authorizes the rekey operation when you meet the threshold of recovery keys. After rekey... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/seal.mdx | main | vault | [
-0.007518438156694174,
0.014292229898273945,
-0.03234363719820976,
-0.018985595554113388,
-0.06739811599254608,
0.010161819867789745,
-0.01185991894453764,
0.001696584396995604,
0.008434655144810677,
-0.027572156861424446,
0.0019260073313489556,
0.026040544733405113,
0.04642607271671295,
-... | -0.106526 |
seal block and add the new auto seal block. Now, bring the standby node back up and run the unseal command on each key, by supplying the `-migrate` flag. - Supply Shamir unseal keys if the old seal was Shamir, which is migrated as the recovery keys for the auto seal. - Supply recovery keys if the old seal is one of aut... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/seal.mdx | main | vault | [
-0.013877077028155327,
0.019430754706263542,
-0.013139517977833748,
0.012838616967201233,
-0.024103185161948204,
-0.0034124564845114946,
-0.041658997535705566,
0.034372009336948395,
-0.03612366318702698,
0.02495471015572548,
0.01737689971923828,
0.007711754180490971,
0.0672651082277298,
-0... | 0.03376 |
recovery keys, Vault migrates the recovery keys that it will use as unseal keys. #### Migration from auto unseal to auto unseal Migration between the same auto unseal types is supported in Vault 1.6.0 and higher. For these pre-1.5.1 steps, you can only migrate from one type of auto unseal to a different type, for examp... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/seal.mdx | main | vault | [
-0.007295576389878988,
-0.02219359017908573,
-0.009967799298465252,
0.009406623430550098,
0.010740501806139946,
-0.003228878602385521,
-0.03743555769324303,
-0.02263505756855011,
0.014499668031930923,
-0.020955219864845276,
0.05049842596054077,
0.018321283161640167,
0.06542298942804337,
-0... | -0.032864 |
cannot include Shamir seals in a seal HA setup. Auto seals support seal wrap, so the loss of the auto seal does not necessarily leave Vault in a fully available state. However, Shamir seals do not support seal wrap. ### Use and configuration Refer to the [configuration](/vault/docs/configuration/seal/seal-ha) section f... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/seal.mdx | main | vault | [
0.011788167990744114,
0.0547197088599205,
-0.011276377364993095,
0.010538812726736069,
0.016543325036764145,
-0.038902826607227325,
-0.03635622188448906,
-0.0155991455540061,
-0.02311628684401512,
-0.03857250511646271,
0.0090347770601511,
0.023153971880674362,
0.038635581731796265,
0.01173... | -0.08323 |
# OIDC provider This document provides conceptual information about the Vault \*\*OpenID Connect (OIDC) identity provider\*\* feature. This feature enables client applications that speak the OIDC protocol to leverage Vault's source of [identity](/vault/docs/concepts/identity) and wide range of [authentication methods](... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/oidc-provider.mdx | main | vault | [
-0.06719042360782623,
0.012877403758466244,
-0.06424790620803833,
0.01984519511461258,
0.02393524907529354,
-0.08143166452646255,
0.040383659303188324,
0.0038545874413102865,
0.09791357070207596,
-0.10035837441682816,
-0.025285886600613594,
0.06479381024837494,
0.040791045874357224,
-0.011... | 0.062943 |
of | | `identity.entity.groups.names` | The names of the groups the entity is a member of | | `identity.entity.metadata` | Metadata associated with the entity | | `identity.entity.metadata.` | Metadata associated with the entity for the given key | | `identity.entity.aliases..id` | Entity alias ID for the given mount |... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/oidc-provider.mdx | main | vault | [
-0.040337152779102325,
0.02983466535806656,
-0.011635446920990944,
0.000017907512301462702,
0.040852759033441544,
-0.040105581283569336,
0.04268348589539528,
0.07370079308748245,
0.04009711369872093,
-0.016931332647800446,
0.053788911551237106,
-0.10009749978780746,
0.07849247008562088,
-0... | 0.031464 |
the OAuth 2.0 [client type](https://datatracker.ietf.org/doc/html/rfc6749#section-2.1) based on its ability to maintain confidentiality of credentials. The following sections detail the differences between confidential and public clients in Vault. ##### Confidential Confidential clients are capable of maintaining the c... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/oidc-provider.mdx | main | vault | [
-0.04989364370703697,
0.05530153959989548,
-0.09597250819206238,
-0.02094084955751896,
-0.003912749234586954,
-0.07929790019989014,
-0.009482219815254211,
0.041340526193380356,
0.09374003112316132,
-0.05297928303480148,
0.0004377836303319782,
0.02809893526136875,
0.07542398571968079,
-0.04... | -0.018628 |
are published in a JSON Web Key Set [(JWKS)](https://datatracker.ietf.org/doc/html/rfc7517) format. The keyset for an individual provider contains the keys referenced by all clients via the `allowed\_client\_ids` configuration parameter. A `Cache-Control` header to set based on responses, allowing clients to refresh th... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/oidc-provider.mdx | main | vault | [
-0.0410887710750103,
0.0762881338596344,
-0.0815667062997818,
0.013100177980959415,
0.0007149213342927396,
-0.06743486225605011,
-0.005376143846660852,
-0.051342375576496124,
0.07349281013011932,
-0.02672324702143669,
0.03332512825727463,
0.11189030855894089,
0.08060696721076965,
-0.012165... | -0.008555 |
# Using PGP, GnuPG, and keybase Vault has the ability to integrate with OpenPGP-compatible programs like GnuPG and services like Keybase.io to provide an additional layer of security when performing certain operations. This page details the various PGP integrations, their use, and operation. Keybase.io support is avail... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/pgp-gpg-keybase.mdx | main | vault | [
-0.04892287030816078,
-0.01468691136687994,
0.0022270027548074722,
0.0001817519951146096,
-0.020846577361226082,
-0.04386391118168831,
-0.0475991815328598,
0.02467011660337448,
0.02373066544532776,
-0.0021579954773187637,
-0.03191822022199631,
0.09832236915826797,
0.03746824711561203,
-0.0... | -0.021964 |
```shell-session $ echo "wcBMA37..." | base64 --decode | keybase pgp decrypt ``` And replace `wcBMA37...` with the encrypted key. You will be prompted to enter your Keybase passphrase. The output will be the plain-text unseal key. ``` 6ecb46277133e04b29bd0b1b05e60722dab7cdc684a0d3ee2de50ce4c38a357101 ``` This is your u... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/pgp-gpg-keybase.mdx | main | vault | [
0.009543733671307564,
0.05964602157473564,
-0.0838274136185646,
-0.016274362802505493,
-0.04837894067168236,
0.06246929243206978,
0.023925838991999626,
0.029543742537498474,
0.03746524825692177,
-0.004543190356343985,
-0.06532887369394302,
-0.013658173382282257,
-0.010399993509054184,
-0.0... | -0.031214 |
# Cloud access management Modern access management must be as dynamic as the infrastructure, people, and systems it serves. Traditionally, you use an IP address as the unit of security control; you use the IP as a unit of identity and manage around that, including traditional privileged access management (PAM). As you ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/cloud-access-management.mdx | main | vault | [
-0.02575790137052536,
0.03051059879362583,
-0.0424414724111557,
-0.05322229117155075,
0.003951219841837883,
-0.030972033739089966,
0.06800317019224167,
-0.025031832978129387,
0.08523622900247574,
0.024508384987711906,
-0.0034937693271785975,
0.07597661018371582,
0.01159803755581379,
-0.002... | 0.152589 |
gated using identity through trusted identity providers rather than outmoded identifiers like IP addresses (the traditional approach). The National Institute for Standards and Technology (NIST) recommends shifting to identity-based segmentation instead of network segmentation, as workloads, users, data, and credentials... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/cloud-access-management.mdx | main | vault | [
-0.012285606935620308,
0.05181083455681801,
-0.0398365780711174,
-0.02821170724928379,
-0.07862777262926102,
-0.05834219977259636,
0.04696842283010483,
0.00959633756428957,
0.10695043206214905,
-0.013318016193807125,
0.005219734273850918,
0.0016477849567309022,
0.02185961790382862,
0.01817... | 0.180153 |
credentials One of the basic principles of data security is the principle of least privilege, which reduces risk by allowing only specific privileges for specific purposes. However, standing privileges easily violate this principle — account privileges are always available, even when not needed — providing a perpetuall... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/cloud-access-management.mdx | main | vault | [
-0.04262109845876694,
0.07022463530302048,
-0.05942503362894058,
0.014396019279956818,
-0.045511920005083084,
-0.003709499491378665,
0.040939465165138245,
0.018025202676653862,
0.06627565622329712,
-0.0185734611004591,
-0.026043767109513283,
0.02476789429783821,
0.05383332446217537,
-0.000... | 0.059974 |
of the HashiCorp suite of tools for managing identity-based access for modern, dynamic infrastructure. Boundary allows a single workflow to facilitate interactive human sessions for privileged and non-privileged accounts while providing a local development experience. It leverages Vault's identity brokering and dynamic... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/cloud-access-management.mdx | main | vault | [
-0.005388529505580664,
0.014257458038628101,
-0.05359094217419624,
-0.07725222408771515,
0.028794268146157265,
-0.06736401468515396,
0.06856891512870789,
-0.022041892632842064,
0.03231315314769745,
0.003430539509281516,
-0.03854524716734886,
-0.043492984026670456,
0.005679192487150431,
0.0... | 0.173036 |
# Identity This document contains conceptual information about \*\*Identity\*\* along with an overview of the various terminologies and their concepts. The idea of Identity is to maintain the clients who are recognized by Vault. As such, Vault provides an identity management solution through the \*\*Identity secrets en... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/identity.mdx | main | vault | [
-0.06534865498542786,
-0.008958101272583008,
-0.04138131067156792,
-0.015956511721014977,
-0.020754342898726463,
-0.03426821529865265,
0.10847774893045425,
0.0002696834853850305,
0.09076689928770065,
-0.07198566943407059,
-0.004806708078831434,
-0.015145917423069477,
0.11135438829660416,
-... | 0.105742 |
the policies on the entity are only a means to grant \_additional\_ capabilities and not a replacement for the policies on the token. To know the full set of capabilities of the token with an associated entity identifier, the policies on the token should be taken into account. ~> \*\*NOTE:\*\* Be careful in granting pe... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/identity.mdx | main | vault | [
-0.049433816224336624,
0.02845131792128086,
0.026635292917490005,
-0.03034709207713604,
-0.00438667181879282,
-0.0351114384829998,
0.09861592948436737,
0.0319669172167778,
0.10168367624282837,
-0.01617131009697914,
-0.0040207370184361935,
-0.018474305048584938,
0.08577073365449905,
0.00733... | 0.014212 |
beforehand and assign policies to them, so that when users login, the desired capabilities to the tokens via entities are already assigned. But if that's not done, upon a successful user login from any of the authentication backends, Vault will create a new entity and assign an alias against the login that was successf... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/identity.mdx | main | vault | [
-0.07258721441030502,
0.016597164794802666,
-0.013060279190540314,
-0.000018084725525113754,
0.005583598278462887,
-0.059735141694545746,
0.11241961270570755,
-0.031736504286527634,
0.1337566077709198,
-0.021983997896313667,
0.006384755950421095,
-0.012449999339878559,
0.05740731209516525,
... | 0.058529 |
# User lockout @include 'user-lockout.mdx' ## Precedence The precedence for user lockout configuration is as follows: Configuration for an auth mount using tune >> Configuration for an auth method in config file >> Configuration for "all" auth methods in config file >> Default values. The precedence for user lockout di... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/user-lockout.mdx | main | vault | [
0.03809630870819092,
0.04583685100078583,
-0.08253687620162964,
-0.07455749064683914,
-0.02428760752081871,
0.02096756361424923,
0.021922742947936058,
-0.052578289061784744,
-0.01020321249961853,
-0.02899601124227047,
0.012597688473761082,
0.04738352447748184,
0.0859651193022728,
-0.024860... | -0.019499 |
# Namespace lock and unlock Vault makes the API available (unlocked) by default for all namespaces. In this state, Vault can respond to all API/CLI ('API' from here on out) requests as normal. A Vault administrator can lock the API for particular namespaces. In this state, Vault blocks all but a selected few API endpoi... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/namespace-api-lock.mdx | main | vault | [
-0.06660116463899612,
-0.015382876619696617,
-0.01012498326599598,
-0.05295538157224655,
0.037036921828985214,
-0.026066621765494347,
-0.011248208582401276,
-0.0797617956995964,
0.10644903033971786,
-0.027685144916176796,
0.03354605287313461,
0.03156282752752304,
0.03389490395784378,
-0.01... | 0.027041 |
same error will return if a request is made in a descendant of `nsA`. ## How does this work with replication? API Lock status is replicated to all clusters, and observed at all nodes. | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/namespace-api-lock.mdx | main | vault | [
-0.05690738931298256,
-0.06912103295326233,
-0.026804717257618904,
-0.00939188152551651,
0.012661652639508247,
-0.060045912861824036,
-0.021260783076286316,
-0.11597690731287003,
0.028339890763163567,
0.09466533362865448,
0.05143003165721893,
0.025223806500434875,
0.08728081732988358,
-0.0... | 0.11627 |
# Storage As described on our [Architecture](/vault/docs/internals/architecture) page, Vault's storage backend is untrusted storage used purely to keep encrypted information. ## Supported storage backends @include 'ent-supported-storage.mdx' Many other options for storage are available with community support for Vault ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/storage.mdx | main | vault | [
0.0014534874353557825,
0.011706911958754063,
-0.05913789942860603,
-0.012428658083081245,
0.027178671211004257,
-0.028724316507577896,
0.002855780767276883,
0.04356364533305168,
0.0025647878646850586,
0.0037020312156528234,
-0.012094195000827312,
0.0598127618432045,
0.12705372273921967,
-0... | -0.051596 |
Replication](/vault/docs/enterprise/replication#performance-replication-and-disaster-recovery-dr-replication), you should plan to take backups of the active node on each of your clusters. ### Configuration In addition to backing up Vault's encrypted data via the storage backend, you may also wish to save the server con... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/storage.mdx | main | vault | [
0.04781649634242058,
-0.019105473533272743,
-0.04849131032824516,
0.008172751404345036,
0.045591894537210464,
-0.011546676978468895,
-0.05442199110984802,
-0.02214602194726467,
0.020921798422932625,
-0.012490014545619488,
-0.005188792012631893,
0.07231774181127548,
0.09123051166534424,
-0.... | -0.018601 |
# Resource quotas Every single interaction with Vault, whether to put secrets into the key/value store or to generate new pairs of database credentials for the MySQL database, needs to go through Vault’s API. One side effect of the API driven model is that applications and users can misbehave by overwhelming system res... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/resource-quotas.mdx | main | vault | [
-0.00031897943699732423,
0.023368684574961662,
-0.05420960485935211,
-0.014814881607890129,
-0.03975045680999756,
-0.051340509206056595,
-0.0338052399456501,
0.010620352812111378,
0.12541578710079193,
0.00439813919365406,
-0.03942982107400894,
0.022580355405807495,
0.1377919763326645,
0.04... | 0.021743 |
Vault operators can override the set of paths that are exempt from all rate limit resource quotas by updating the `rate\_limit\_exempt\_paths` configuration field. - `sys/generate-recovery-token/attempt` - `sys/generate-recovery-token/update` - `sys/generate-root/attempt` - `sys/generate-root/update` - `sys/health` - `... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/resource-quotas.mdx | main | vault | [
0.019160714000463486,
-0.008807796984910965,
-0.06598620116710663,
-0.007412957958877087,
-0.03518310561776161,
-0.08695676177740097,
-0.06262006610631943,
0.010622875764966011,
0.058783553540706635,
-0.0181733388453722,
-0.020129986107349396,
-0.01474185474216938,
0.10121607035398483,
0.0... | -0.025716 |
# High availability mode (HA) Vault supports a multi-server mode for high availability. This mode protects against outages by running multiple Vault servers. High availability mode is automatically enabled when using a data store that supports it. You can tell if a data store supports high availability mode ("HA") by s... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/ha.mdx | main | vault | [
0.04364491254091263,
-0.001320668845437467,
-0.06393986195325851,
0.028454788029193878,
0.019638121128082275,
-0.022296441718935966,
-0.06070331111550331,
-0.009457885287702084,
0.022384630516171455,
-0.004712439142167568,
-0.008724279701709747,
0.116355299949646,
0.0391116738319397,
-0.07... | 0.059218 |
configuration parameters, although some can be automatically determined. ## Client redirection If `X-Vault-No-Request-Forwarding` header in the request is set to a non-empty value, the standby nodes will redirect the client using a `307` status code to the \_active node's\_ redirect address. This is also the fallback m... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/ha.mdx | main | vault | [
0.025304559618234634,
0.030253669247031212,
-0.08274345844984055,
0.00007324921170948073,
-0.020304057747125626,
-0.01276490930467844,
-0.04286454990506172,
0.013745387084782124,
-0.005296047776937485,
-0.013762800954282284,
-0.0049761938862502575,
0.03203053027391434,
0.06566928327083588,
... | -0.014982 |
a host name or IP address that a standby can use to reach one of that node's [`cluster\_address`](/vault/docs/configuration#cluster\_address) values set in the [`listener`](/vault/docs/configuration/listener) blocks, including port. (Note that this will always be forced to `https` since only TLS connections are used be... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/ha.mdx | main | vault | [
-0.006241719704121351,
0.020663442090153694,
-0.08349215984344482,
-0.029282689094543457,
-0.005949660204350948,
-0.049695879220962524,
-0.10209298878908157,
-0.0140756294131279,
-0.0007485434180125594,
-0.01714329607784748,
0.01151229813694954,
0.0551273338496685,
0.0478639118373394,
-0.0... | 0.072015 |
# Response wrapping \_Note\_: Some of this information relies on features of response-wrapping tokens introduced in Vault 0.8 and may not be available in earlier releases. ## Overview In many Vault deployments, clients can access Vault directly and consume returned secrets. In other situations, it may make sense to or ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/response-wrapping.mdx | main | vault | [
-0.08475177735090256,
0.09472658485174179,
-0.02130073308944702,
0.058473773300647736,
-0.004853610880672932,
-0.09085134416818619,
-0.004169287160038948,
0.020519312471151352,
0.072585828602314,
-0.009881217032670975,
0.0003183831868227571,
0.05361682176589966,
0.02569451555609703,
0.0102... | 0.023941 |
the response-wrapping token or gain knowledge of the token ID inside. Vault currently does not provide signed response-wrapping tokens, as it provides little extra protection. If you are being pointed to the correct Vault server, token validation is performed by interacting with the server itself; a signed token does n... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/response-wrapping.mdx | main | vault | [
-0.03702079504728317,
0.059341076761484146,
0.007788090966641903,
-0.009343624114990234,
-0.013334119692444801,
-0.09835771471261978,
-0.0061757550574839115,
-0.01604013331234455,
0.06991460174322128,
0.007200263906270266,
0.017077729105949402,
0.0973547101020813,
0.046931762248277664,
0.0... | -0.053557 |
response is generated, with the token ID, TTL, and path stored in the new response's wrap information object 5. The new response is returned to the caller Note that policies can control minimum/maximum wrapping TTLs; see the [policies concepts page](/vault/docs/concepts/policies) for more information. ## Response-Wrapp... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/response-wrapping.mdx | main | vault | [
-0.052743684500455856,
0.05010963976383209,
0.012751330621540546,
0.022733310237526894,
0.022167077288031578,
-0.10030565410852432,
-0.0031088734976947308,
-0.020928766578435898,
0.09522596746683121,
-0.011166948825120926,
0.011176184751093388,
0.04568411037325859,
0.023569256067276,
0.003... | 0.052285 |
# Integrated storage Vault supports a number of storage options for the durable storage of Vault's information. As of Vault 1.4 an Integrated Storage option is offered. This storage backend does not rely on any third party systems, implements high availability semantics, supports Enterprise Replication features, and pr... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/integrated-storage/index.mdx | main | vault | [
-0.0070006451569497585,
0.009788434021174908,
-0.08184376358985901,
0.00705754617229104,
-0.02892110124230385,
-0.0942046046257019,
-0.04985221475362778,
0.011813548393547535,
0.017600663006305695,
-0.029019353911280632,
0.014897347427904606,
0.08486457169055939,
0.11612220108509064,
-0.02... | 0.06326 |
} retry\_join { leader\_api\_addr = "https://node2.vault.local:8200" } } ``` Note, in each [`retry\_join`](/vault/docs/configuration/storage/raft#retry\_join-stanza) stanza, you may provide a single [`leader\_api\_addr`](/vault/docs/configuration/storage/raft#leader\_api\_addr) or [`auto\_join`](/vault/docs/configurati... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/integrated-storage/index.mdx | main | vault | [
-0.009674517437815666,
0.032060205936431885,
-0.022262929007411003,
0.01436497364193201,
0.019240792840719223,
-0.07694870978593826,
-0.029142828658223152,
-0.04267086461186409,
0.025969844311475754,
-0.041258376091718674,
0.037476878613233566,
0.004195652436465025,
0.06949114054441452,
0.... | -0.040917 |
the IPs aren't knowable in advance, the TLS certificates used to secure the Vault API port don't contain these IPs in their IP SANs. ### Vault networking recap Before we explore solutions to this problem, let's recapitulate how Vault nodes speak to one another. Vault exposes two TCP ports: [the API port](/vault/docs/co... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/integrated-storage/index.mdx | main | vault | [
0.01658611372113228,
0.04086751118302345,
-0.0444750152528286,
0.02409375086426735,
0.005537181627005339,
-0.050041958689689636,
-0.06439226865768433,
-0.04190006107091904,
0.05649925395846367,
-0.018095800653100014,
-0.0238175168633461,
0.008799441158771515,
0.0862748920917511,
-0.0025529... | 0.006001 |
assigned from a small subnet, e.g. a `/28`, it becomes practical to put all the IPs that exist in that subnet into the IP SANs of the TLS certificate the nodes will share. The drawback here is that the cluster may someday outgrow the CIDR and changing it may be a pain. For similar reasons this solution may be impractic... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/integrated-storage/index.mdx | main | vault | [
-0.046511560678482056,
0.057772014290094376,
-0.03766722232103348,
0.021388571709394455,
-0.024370554834604263,
-0.035041023045778275,
-0.008766967803239822,
-0.022187981754541397,
-0.0030496097169816494,
-0.033143069595098495,
-0.04039034992456436,
-0.023077048361301422,
0.10661765187978745... | -0.044286 |
where no other option is available to recover a lost server. Make sure you don't have any automated processes that will put the peers file in place on a periodic basis. To begin, stop all remaining servers. The next step is to go to the [configured data path](/vault/docs/configuration/storage/raft/#path) of each Vault ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/integrated-storage/index.mdx | main | vault | [
-0.002135641174390912,
0.028122425079345703,
-0.040779516100883484,
0.05470603331923485,
0.054924432188272476,
-0.013914995826780796,
-0.09758051484823227,
-0.028959879651665688,
0.025051027536392212,
0.001608130056411028,
0.023454925045371056,
0.04664245992898941,
0.06891679018735886,
-0.... | -0.060877 |
# Migration checklist The purpose of this checklist is not to walk you through the storage migration steps. This content provides a quick self-check whether it is your best interest to migrate your Vault storage from an external system to Integrated Storage. ## Who should use this checklist? Integrated Storage is a rec... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/integrated-storage/migration-checklist.mdx | main | vault | [
0.05441872403025627,
-0.018018795177340508,
-0.06886739283800125,
-0.05839079990983009,
0.03498320281505585,
-0.09919825941324234,
-0.0510440431535244,
0.0780387818813324,
-0.015887271612882614,
0.02166423201560974,
0.019430335611104965,
0.001362004317343235,
0.049244266003370285,
0.022346... | 0.035661 |
CPU | Memory | Disk | Typical Cloud Instance Types | | ----- | -------- | ------------ | ------ | ------------------------------------------ | | Small | 2 core | 8-16 GB RAM | 100 GB | \*\*AWS:\*\* m5.large, m5.xlarge | | | | | | \*\*Azure:\*\* Standard\_D2\_v3, Standard\_D4\_v3 | | | | | | \*\*GCE:\*\* n2-standard-2, ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/integrated-storage/migration-checklist.mdx | main | vault | [
0.05439875274896622,
0.012560675852000713,
-0.0357302688062191,
0.005067519843578339,
0.03138720616698265,
-0.04708046838641167,
-0.011496659368276596,
-0.017703566700220108,
0.020662475377321243,
0.13985773921012878,
0.0031026569195091724,
-0.04175756499171257,
0.046956080943346024,
-0.06... | 0.062256 |
[ ] Do you currently rely heavily on using Consul to inspect Vault data? ## Tutorials If you are ready to migrate the current storage backend to Integrated Storage, refer to the [Storage Migration Tutorial - Consul to Integrated Storage](/vault/tutorials/raft/raft-migration). To deploy a new cluster with Integrated Sto... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/integrated-storage/migration-checklist.mdx | main | vault | [
0.050507623702287674,
-0.010614525526762009,
-0.11806828528642654,
-0.020001117140054703,
0.008591740392148495,
-0.11734623461961746,
-0.07917053997516632,
0.04490221291780472,
-0.061369918286800385,
0.024594781920313835,
0.05545346066355705,
-0.00005038196832174435,
0.03908116742968559,
-... | 0.025337 |
# Migrate Consul storage to Integrated Storage This guidance provides steps to migrate Vault server storage from Consul to Integrated Storage. Integrated Storage requires \*\*Vault 1.4\*\* or later. Before continuing with this guidance, be sure to read the [Migration checklist](/vault/docs/concepts/integrated-storage/m... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/integrated-storage/migrate-consul-storage.mdx | main | vault | [
0.04556315019726753,
-0.040547020733356476,
-0.04816323518753052,
-0.07169412821531296,
-0.016047988086938858,
-0.0696263238787651,
-0.07937159389257431,
0.03793399780988693,
-0.02906176634132862,
0.044700078666210175,
0.01129176001995802,
0.027927417308092117,
0.04192056134343147,
-0.0020... | -0.023477 |
to perform the migration. ```shell-session $ vault operator migrate -config=migrate.hcl ``` Refer to the Vault command documentation on [operator migrate](/vault/docs/commands/operator/migrate#migrating-to-integrated-raft-storage) for more information. 1. You can start the Vault server using the new server configuratio... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/integrated-storage/migrate-consul-storage.mdx | main | vault | [
0.04664495214819908,
-0.02333872765302658,
-0.0733196884393692,
-0.004028978757560253,
-0.011073699221014977,
-0.061513494700193405,
-0.054720666259527206,
-0.021483223885297775,
-0.031140955165028572,
-0.02539282664656639,
0.022745830938220024,
-0.0273459330201149,
0.10870562493801117,
-0... | -0.057569 |
# Autopilot Autopilot enables automated workflows for managing Raft clusters. The current feature set includes 3 main features: Server Stabilization, Dead Server Cleanup and State API. These three features were introduced in Vault 1.7. The Enterprise feature set includes 2 main features: Automated Upgrades and Redundan... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/integrated-storage/autopilot.mdx | main | vault | [
0.0007494766032323241,
-0.006604932714253664,
-0.02358228713274002,
0.006193156819790602,
0.05088219791650772,
-0.09757396578788757,
-0.019863810390233994,
-0.031860191375017166,
-0.03189407289028168,
0.02846142277121544,
-0.008909408003091812,
0.0617254413664341,
0.03422404080629349,
-0.0... | 0.122818 |
clusters have their own autopilot configurations, managed independently of their primary. The [Autopilot API](/vault/api-docs/system/storage/raftautopilot) uses DR operation tokens for authorization when executed against a DR secondary cluster. ## Tutorial Refer to the following tutorials to learn more. - [Integrated S... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/integrated-storage/autopilot.mdx | main | vault | [
-0.005320623982697725,
0.008983375504612923,
-0.06474672257900238,
-0.01873001828789711,
-0.000909576890990138,
-0.10182047635316849,
-0.03586302697658539,
0.0783817395567894,
-0.014749497175216675,
0.020311007276177406,
0.012234664522111416,
0.021835636347532272,
0.058696310967206955,
0.0... | 0.121425 |
# Client count calculation Vault provides usage telemetry for the number of clients based on the number of unique entity assignments within a Vault cluster over a given billing period: - Standard entity assignments based on authentication method for active entities. - Constructed entity assignments for active non-entit... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/client-count/counting.mdx | main | vault | [
-0.004756430629640818,
-0.004747997969388962,
-0.07051508873701096,
0.02739708311855793,
-0.03365108743309975,
-0.037695638835430145,
-0.014465519227087498,
-0.007668340113013983,
0.09942782670259476,
-0.02698323130607605,
0.006250882055610418,
0.021881110966205597,
0.1328316032886505,
-0.... | 0.043437 |
becomes increasingly imprecise as: - the difference between `BP` and `CM` increases - the value of `CM` approaches zero. - the number of months in the billing period increase. The maximum observed error rate (`ER = (FOUND\_NEW\_CLIENTS / EXPECTED\_NEW\_CLIENTS)`) was 30% for 10,000 clients or less, with an error rate o... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/client-count/counting.mdx | main | vault | [
-0.01637064665555954,
-0.0016802987083792686,
-0.04755554348230362,
0.06686834990978241,
0.012286270968616009,
-0.07639622688293457,
-0.02918853797018528,
0.06769264489412308,
0.02560904435813427,
0.08014331012964249,
0.000549876713193953,
-0.07824614644050598,
0.07615881413221359,
-0.0433... | 0.062364 |
# Monitor client usage in Vault Client calculation and sizing can be complex to compute when you have multiple namespaces and auth mounts. The \*\*Vault Client Usage\*\* dashboard in the Vault GUI provides the information where you can filter the data by namespace and/or auth mounts. You can also use Vault CLI or API t... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/client-count/client-usage.mdx | main | vault | [
0.10218263417482376,
0.03371091187000275,
-0.0763288289308548,
-0.008460521697998047,
-0.06024419888854027,
-0.047682907432317734,
0.021446427330374718,
0.013263377360999584,
0.02662472240626812,
-0.04644859954714775,
-0.02728288061916828,
-0.05485611408948898,
0.08302675932645798,
0.02846... | -0.079266 |
Enterprise, under the \*\*Change billing period\*\*, select \*\*Billing start date\*\* to query the data for a different billing period.  For Vault Community, under the \*\*Client counting period\*\*, select \*\*Edit\*\* to... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/client-count/client-usage.mdx | main | vault | [
0.0014257333241403103,
0.01977020688354969,
-0.025010550394654274,
0.03444909676909447,
-0.020246567204594612,
-0.03863953799009323,
-0.03664931282401085,
-0.03772740066051483,
0.03904212266206741,
-0.050312794744968414,
-0.015621660277247429,
-0.02878948487341404,
0.01516477856785059,
0.0... | -0.041008 |
[Activity export API](/vault/api-docs/system/internal-counters#activity-export) to export activity log. | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/client-count/client-usage.mdx | main | vault | [
0.05919113755226135,
-0.03823144733905792,
-0.0941649004817009,
-0.005537770688533783,
0.020589541643857956,
-0.013436525128781796,
-0.0066160643473267555,
-0.00524585135281086,
0.05740944668650627,
0.005379185080528259,
-0.025564834475517273,
-0.002103187143802643,
0.03853803873062134,
0.... | 0.03844 |
# Clients and entities Anything that connects and authenticates to Vault to accomplish a task is a \*\*client\*\*. For example, a user logging into a cluster to manage policies or a machine-based system (application or cloud service) requesting a database token are both considered clients.  with allowable entity aliases and assigning all t... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/client-count/index.mdx | main | vault | [
0.005731543526053429,
-0.004493242129683495,
-0.05490770936012268,
-0.028413213789463043,
-0.03655695915222168,
-0.09501533955335617,
0.006216533947736025,
0.023537389934062958,
0.09139623492956161,
-0.03876204043626785,
0.022667940706014633,
-0.010386042296886444,
0.08975952863693237,
0.0... | 0.027273 |
# Client count FAQ | Definitions | | ----------------------- | | [What is a client?](#what-is-a-client) | | [What is the difference between an entity client, non-entity client, certificate client, and secret sync client?](#eclient-vs-neclient) | | Computing client count | | ----------------------- | | [Can I compute cl... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/client-count/faq.mdx | main | vault | [
-0.04997456446290016,
-0.012184547260403633,
0.01137879304587841,
-0.03407660871744156,
-0.01494284626096487,
-0.010655843652784824,
-0.01447679940611124,
-0.047293320298194885,
0.05555560812354088,
-0.043475355952978134,
0.05259639024734497,
-0.03530583158135414,
0.11819169670343399,
-0.0... | -0.018766 |
Vault Enterprise includes features for [Adaptive Overload Protection](/vault/docs/concepts/adaptive-overload-protection). When some server resource is at capacity, Vault Enterprise may reject some HTTP client requests to preserve the Vault server's ability to remain stable and available. This document described conside... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/adaptive-overload-protection/vault-server-temporarily-overloaded.mdx | main | vault | [
-0.02011657878756523,
0.05899824574589729,
-0.029465267434716225,
-0.03309593349695206,
-0.03612016513943672,
-0.11573994159698486,
-0.07097866386175156,
-0.03782835602760315,
0.02843121625483036,
0.0065854196436703205,
-0.02383044734597206,
0.08276674151420593,
0.043255142867565155,
-0.00... | -0.027141 |
# Adaptive overload protection @include 'alerts/enterprise-only.mdx' Adaptive overload protection refers to a set of features in Vault Enterprise that prevent client requests from overwhelming different server resources leading to poor availability. ## Preventing overload Vault currently supports one type of adaptive o... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/adaptive-overload-protection/index.mdx | main | vault | [
0.0013631351757794619,
0.04019565507769585,
0.008650706149637699,
0.023051682859659195,
0.03652888536453247,
-0.09493739902973175,
-0.02224596217274666,
-0.0006885358016006649,
0.008699063211679459,
0.00241208728402853,
-0.07498674094676971,
0.125523179769516,
0.06118861958384514,
-0.06176... | 0.135535 |
storage. Adaptive overload protection is not available for Consul and other storage backends. To disable the feature use the [`adaptive\_overload\_protection` configuration stanza](/vault/docs/configuration/adaptive-overload-protection). ### Metrics Operators may wish to monitor metrics related to the write overload pr... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/concepts/adaptive-overload-protection/index.mdx | main | vault | [
-0.03034290485084057,
0.019242169335484505,
-0.07225130498409271,
0.051444511860609055,
-0.018038036301732063,
-0.10610517114400864,
-0.07129988074302673,
0.018785417079925537,
-0.005553597118705511,
0.08908708393573761,
-0.009228846989572048,
0.07777246832847595,
0.042251817882061005,
-0.... | -0.010318 |
# path-help The `path-help` command retrieves API help for paths. All endpoints in Vault provide built-in help in markdown format. This includes system paths, secret engines, and auth methods. The help system is the easiest way to learn how to use the various systems in Vault, and also allows you to discover new paths.... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/path-help.mdx | main | vault | [
0.0036694335285574198,
0.030477700755000114,
-0.060145244002342224,
0.02125292830169201,
0.04836336523294449,
-0.009101656265556812,
-0.06918331980705261,
0.033613938838243484,
0.04736688360571861,
-0.06558683514595032,
0.011193286627531052,
0.01396419107913971,
0.017766980454325676,
-0.00... | 0.005687 |
# unwrap The `unwrap` command unwraps a wrapped secret from Vault by the given token. The result is the same as the "vault read" operation on the non-wrapped secret. If no token is given, the data in the currently authenticated token is unwrapped. ## Examples Unwrap the data in the cubbyhole secrets engine for a token:... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/unwrap.mdx | main | vault | [
-0.018884900957345963,
0.08933877944946289,
-0.06643112003803253,
0.06652635335922241,
0.03360065072774887,
-0.050971630960702896,
0.009213431738317013,
0.022785965353250504,
-0.0140846511349082,
-0.0255154836922884,
0.017733275890350342,
-0.047778692096471786,
-0.0010667581809684634,
0.00... | 0.058963 |
# debug The `debug` command starts a process that monitors a Vault server, probing information about it for a certain duration. Gathering information about the state of the Vault cluster often requires the operator to access all necessary information via various API calls and terminal commands. The `debug` command aims... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/debug.mdx | main | vault | [
-0.0040731425397098064,
0.0003751554759219289,
-0.042048998177051544,
0.027843093499541283,
0.039598722010850906,
-0.12867532670497894,
0.01534150168299675,
-0.0020731401164084673,
0.04374769702553749,
-0.013617333024740219,
0.034446973353624344,
0.007956850342452526,
0.010038181208074093,
... | 0.146196 |
├── goroutine.prof │ ├── heap.prof │ ├── profile.prof │ └── trace.out ├── 2019-10-15T21-46-19Z │ ├── goroutine.prof │ ├── heap.prof │ ├── profile.prof │ └── trace.out ├── 2019-10-15T21-46-49Z │ ├── goroutine.prof │ └── heap.prof ├── config.json ├── host\_info.json ├── index.json ├── metrics.json ├── replication\_status... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/debug.mdx | main | vault | [
0.05624513700604439,
0.062004078179597855,
-0.09315400570631027,
-0.015547393821179867,
0.015897540375590324,
-0.08598645031452179,
-0.025134671479463577,
0.03168490529060364,
-0.004944296088069677,
0.020198209211230278,
0.05912395566701889,
-0.05053795874118805,
0.018012575805187225,
0.03... | 0.019883 |
# events Use the `events` command to get a real-time display of [event notifications](/vault/docs/concepts/events) generated by Vault and to subscribe to Vault event notifications. Note that the `events subscribe` runs indefinitly and will not exit on its own unless it encounters an unexpected error. Similar to `tail -... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/events.mdx | main | vault | [
0.08865760266780853,
0.036311376839876175,
-0.028359245508909225,
-0.045678429305553436,
0.03195090964436531,
-0.053183600306510925,
-0.0035187029279768467,
0.01631356030702591,
0.09769260883331299,
-0.020416967570781708,
-0.050626907497644424,
-0.11576049774885178,
-0.005948883015662432,
... | 0.024878 |
statements that exclude specific operations. For example: ``` data\_path == secret/data/foo and operation != write ``` | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/events.mdx | main | vault | [
-0.012428853660821915,
0.0751594603061676,
-0.025556784123182297,
0.05072381719946861,
-0.05582338571548462,
-0.06736501306295395,
0.03288770839571953,
-0.0025568122509866953,
0.010326847434043884,
0.03573333099484444,
0.08028702437877655,
0.022898320108652115,
0.048949092626571655,
-0.063... | 0.110313 |
# Use a custom token helper A \*\*token helper\*\* is a program or script that saves, retrieves, or erases a saved authentication token. By default, the Vault CLI includes a token helper that caches tokens from any enabled authentication backend in a `~/.vault-token` file. You can customize the caching behavior with a ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/token-helper.mdx | main | vault | [
-0.002531706588342786,
0.03298892825841904,
-0.07360700517892838,
-0.03012951835989952,
-0.04823857918381691,
-0.02823527716100216,
0.02194708026945591,
0.026818273589015007,
0.041764870285987854,
-0.02147357165813446,
0.00207133567892015,
-0.00556650897487998,
0.07779687643051147,
-0.0099... | 0.017357 |
JSON=$( jq \ --arg key "${KEY}" \ --arg token "${TOKEN}" \ 'del(.[$key])' ${TOKEN\_FILE} ) ;; \*) # change to stderr for real code write\_error "Error: Provide a valid command: get, store, or erase." exit 101 esac # Update the JSON file and return success echo $JSON | jq "." > ${TOKEN\_FILE} exit 0 ``` ```powershell <#... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/token-helper.mdx | main | vault | [
0.006303397472947836,
0.037200845777988434,
-0.05681898444890976,
-0.004708732943981886,
-0.06357283145189285,
-0.023363737389445305,
0.011176126077771187,
-0.001759156584739685,
0.08144465833902359,
0.050707533955574036,
0.04996929690241814,
0.038490138947963715,
0.03922179341316223,
-0.0... | -0.020655 |
# recover @include 'alerts/enterprise-only.mdx' The `recover` command pulls data at the specified path from a loaded snapshot and restores it to the cluster, overwriting newer data on the same path. @include 'recover/deletedmounts.mdx' ## Examples Recover the KV version 1 secret at the path `my-secret` from the loaded ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/recover.mdx | main | vault | [
-0.01701636239886284,
0.049799904227256775,
-0.008185893297195435,
-0.009629354812204838,
0.09010808914899826,
-0.0010563649702817202,
-0.01584135740995407,
-0.006504860706627369,
0.06372479349374771,
-0.013045238330960274,
0.06272232532501221,
-0.012922128662467003,
0.09059067070484161,
-... | -0.038104 |
# Vault CLI The Vault CLI is a static binary that wraps the Vault API. While every CLI command maps directly to one or more APIs internally, not every endpoint is exposed publicly and not every API endpoint has a corresponding CLI command. ## Usage ```shell-session $ vault [subcommand(s)] [flag(s)] [command-argument(s)... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/index.mdx | main | vault | [
0.040952540934085846,
0.04104046896100044,
-0.062006209045648575,
-0.056560151278972626,
0.014793938025832176,
-0.06454905867576599,
-0.029259203001856804,
-0.00952973123639822,
0.04728887230157852,
-0.02893487922847271,
0.018222006037831306,
-0.053190335631370544,
0.05846158415079117,
0.0... | -0.024764 |
write /auth/ldap/groups/admin policies="admin,default" ``` You can use `read`, `write`, `delete`, or `list` with the relevant paths for any valid API endpoint, but some plugins are central to the functionality of Vault and have dedicated CLI commands: - [`vault kv`](/vault/docs/commands/kv) - [`vault transit`](/vault/d... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/index.mdx | main | vault | [
0.048024147748947144,
-0.022104322910308838,
-0.06973382830619812,
-0.026875386014580727,
-0.024123569950461388,
-0.01313137635588646,
-0.0016486956737935543,
-0.023680806159973145,
-0.005463925190269947,
-0.03549688309431076,
0.016136806458234787,
-0.029642630368471146,
0.057541150599718094... | -0.009179 |
# server The `server` command starts a Vault server that responds to API requests. By default, Vault will start in a "sealed" state. The Vault cluster must be initialized before use, usually by the `vault operator init` command. Each Vault server must also be unsealed using the `vault operator unseal` command or the AP... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/server.mdx | main | vault | [
0.040958330035209656,
0.00926199834793806,
-0.10387907177209854,
0.009274877607822418,
-0.03803323954343796,
-0.052645694464445114,
-0.07809829711914062,
-0.017869306728243828,
0.027673810720443726,
-0.026150019839406013,
0.028227010741829872,
0.016045494005084038,
0.05990349128842354,
-0.... | 0.006438 |
not generate profiles when `pprof-dump-dir` is unset. Use `pprof-dump-dir` temporarily during debugging sessions. Do not use `pprof-dump-dir` in regular production processes. - `VAULT\_ALLOW\_PENDING\_REMOVAL\_MOUNTS` `(bool: false)` - (environment variable) Allow Vault to be started with builtin engines which have the... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/server.mdx | main | vault | [
0.01347089372575283,
0.018617980182170868,
-0.020509211346507072,
-0.023295821622014046,
0.024515151977539062,
-0.0919065997004509,
-0.06200452521443367,
0.01687910594046116,
-0.03760385513305664,
-0.041025783866643906,
0.07446788251399994,
0.020833268761634827,
0.04337325692176819,
0.0058... | -0.159088 |
# login The `login` command authenticates users or machines to Vault using the provided arguments. A successful authentication results in a Vault token - conceptually similar to a session token on a website. By default, this token is cached on the local machine for future requests. The `-method` flag allows using other... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/login.mdx | main | vault | [
0.05161508545279503,
0.022776631638407707,
-0.0976923257112503,
-0.02581953816115856,
-0.021145982667803764,
-0.056336138397455215,
-0.006804247386753559,
-0.003617254551500082,
-0.02060619741678238,
-0.05269553139805794,
0.04234705865383148,
0.03651595488190651,
0.04032474756240845,
0.022... | -0.005816 |
ideal for piping to other processes. - `-format` `(string: "table")` - Print the output in the given format. Valid formats are "table", "json", or "yaml". This can also be specified via the `VAULT\_FORMAT` environment variable. ### Command options - `-method` `(string "token")` - Type of authentication to use such as "... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/login.mdx | main | vault | [
0.021921461448073387,
0.005183389876037836,
-0.13024601340293884,
-0.00013805212802253664,
-0.0371781624853611,
-0.042435985058546066,
0.013567741960287094,
0.089851014316082,
-0.00812313612550497,
-0.003084206720814109,
0.033839426934719086,
-0.04456885904073715,
0.06042532995343208,
0.01... | -0.014036 |
# write The `write` command writes data to Vault at the given path (wrapper command for HTTP PUT or POST). The data can be credentials, secrets, configuration, or arbitrary data. The specific behavior of the `write` command is determined at the thing mounted at the path. Data is specified as "\*\*key=value\*\*" pairs o... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/write.mdx | main | vault | [
-0.002770619932562113,
0.020848054438829422,
-0.06748531013727188,
0.039754245430231094,
-0.11203011125326157,
-0.07871022075414658,
-0.04397083818912506,
0.03399212658405304,
0.07445748150348663,
-0.02143719792366028,
-0.035551767796278,
0.05728316307067871,
0.09350459277629852,
-0.049635... | 0.029115 |
# delete The `delete` command deletes secrets and configuration from Vault at the given path (wrapper command for HTTP DELETE). The behavior of "delete" is delegated to the backend corresponding to the given path. ## Examples Remove data in the static secrets engine: ```shell-session $ vault delete secret/my-secret ```... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/delete.mdx | main | vault | [
0.019590390846133232,
0.04014240950345993,
-0.05111798644065857,
0.020039616152644157,
0.026293210685253143,
-0.03838403522968292,
-0.004285147413611412,
-0.10206907987594604,
0.06520768254995346,
0.034780409187078476,
0.03899259492754936,
0.0024683645460754633,
0.08645407855510712,
-0.019... | -0.027015 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.