content large_stringlengths 3 20.5k | url large_stringlengths 53 192 ⌀ | branch large_stringclasses 4
values | source large_stringclasses 51
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
# Key rotation Vault stores different encryption keys for different purposes. Vault uses key rotation to periodically change the keys according to a configured limit or in response to a potential leak or compromised service. ## Relevant key definitions There are four keys involved in key rotation: - \*\*internal encryp... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/rotation.mdx | main | vault | [
-0.008791753090918064,
-0.01889348216354847,
-0.03306673839688301,
-0.0428042970597744,
0.000761375471483916,
-0.013744378462433815,
-0.04098321497440338,
-0.013148808851838112,
0.08231694996356964,
0.007147969678044319,
0.04426842927932739,
0.13199734687805176,
0.07563968002796173,
-0.073... | 0.008017 |
# Integrated Raft storage Vault supports several options for durable information storage. Each backend offers pros, cons, advantages, and trade-offs. For example, some backends support high availability while others provide a more robust backup and restoration process. Integrated storage is a "built-in" storage option ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/integrated-storage.mdx | main | vault | [
-0.04738479480147362,
0.03885013610124588,
-0.05792025849223137,
-0.02630223147571087,
0.023614734411239624,
-0.13351702690124512,
-0.042723655700683594,
0.024459971114993095,
0.026162998750805855,
0.04232803359627724,
0.001133879297412932,
0.12841974198818207,
0.034613292664289474,
-0.020... | 0.138162 |
state machine to maintain the cluster state. Vault uses [BoltDB](https://github.com/etcd-io/bbolt) or WAL Raft as the deterministic finite state machine and blocks writes until they are both committed \*\*and\*\* applied. ### Compacting logs To avoid unbounded growth in the replicated logs, Raft saves the current state... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/integrated-storage.mdx | main | vault | [
-0.04066907614469528,
-0.0011295137228444219,
0.005235438700765371,
0.028083456680178642,
0.059597790241241455,
-0.09980719536542892,
-0.046152181923389435,
-0.03770331293344498,
0.06149519979953766,
0.04173442721366882,
-0.026747064664959908,
0.12048713862895966,
0.018311064690351486,
-0.... | 0.082768 |
periods (heartbeat timeout, election timeout, leader lease timeout) scale according to the [`performance\_multiplier`](/vault/docs/configuration/storage/raft#performance-multiplier) setting in your Vault configuration. By default, the `performance\_multiplier` is 5, which translates to the following timeout values: Tim... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/integrated-storage.mdx | main | vault | [
-0.014417222701013088,
-0.01688612625002861,
-0.0591580905020237,
0.03158574178814888,
-0.008269553072750568,
-0.07960314303636551,
-0.10914541035890579,
0.024330398067831993,
0.0665513277053833,
-0.03483853489160538,
-0.021359894424676895,
0.09933743625879288,
0.02246774174273014,
-0.0559... | 0.043794 |
replicating data received from the leader. While the node is in the initial synchronization state, it cannot vote, but \*\*is\*\* counted for the purposes of quorum. If multiple nodes join the cluster simultaneously (or within a small enough window) the cluster may exceed the expected failure tolerance, quorum may be l... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/integrated-storage.mdx | main | vault | [
-0.0002268471143906936,
-0.02934904769062996,
-0.005521262064576149,
0.0032290939707309008,
-0.006508268415927887,
-0.026202799752354622,
-0.07760953158140182,
-0.02100970596075058,
0.010941384360194206,
0.04280446469783783,
0.0022132049780339003,
-0.030097398906946182,
0.09699049592018127,
... | 0.024455 |
3 | 3 | 2 | 1 | 5 5 | 2 | 3 | 2 | 6 [consensus protocol]: https://en.wikipedia.org/wiki/Consensus\_(computer\_science) [consistency]: https://en.wikipedia.org/wiki/CAP\_theorem ["Raft: In search of an Understandable Consensus Algorithm"]: https://raft.github.io/raft.pdf [paxos]: https://en.wikipedia.org/wiki/Paxos\_%28... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/integrated-storage.mdx | main | vault | [
-0.0909334346652031,
-0.03477241098880768,
-0.08396389335393906,
-0.04443294182419777,
-0.01181190088391304,
-0.07879215478897095,
-0.02891373448073864,
0.010237093083560467,
-0.024720683693885803,
0.040475405752658844,
-0.0019402349134907126,
0.07528991252183914,
0.014402556233108044,
-0.... | 0.194896 |
# Architecture Vault is an intricate system with numerous distinct components. This page details the system architecture and hopes to assist Vault users and developers to build a mental model while understanding the theory of operation. ~> \*\*Note:\*\* This page covers the technical details of Vault. The descriptions ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/architecture.mdx | main | vault | [
-0.043619588017463684,
0.06860683113336563,
-0.06700056791305542,
0.0023512039333581924,
0.03315739333629608,
-0.078183613717556,
0.031490929424762726,
0.015510727651417255,
0.10493982583284378,
-0.034857913851737976,
0.013957582414150238,
0.048490747809410095,
0.07566896826028824,
-0.0459... | 0.140265 |
operators, while applications may use public/private keys or tokens to authenticate. An authentication request that flows through the core and into an auth method determines if the request is valid and returns a list of associated policies. Policies are just a named ACL rule. For example, the "root" policy is built-in ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/architecture.mdx | main | vault | [
-0.010309646837413311,
-0.00557099049910903,
-0.08654908835887909,
-0.06993761658668518,
-0.003260574070736766,
-0.04195430129766464,
0.06071515008807182,
-0.005764591507613659,
0.09455716609954834,
0.0209322739392519,
0.014714893884956837,
0.09999416023492813,
0.051479313522577286,
0.0070... | 0.100241 |
# High availability Vault can run in a high availability (HA) mode to protect against outages by running multiple Vault servers. # Design overview The primary design goal for making Vault Highly Available (HA) is to minimize downtime without affecting horizontal scalability. Vault is bound by the IO limits of the stora... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/high-availability.mdx | main | vault | [
0.012133004143834114,
0.024412984028458595,
-0.05392825976014137,
0.005645571276545525,
-0.019357740879058838,
-0.03481418639421463,
-0.026138359680771828,
-0.00451182434335351,
0.03837518393993378,
0.006792192813009024,
-0.0064257667399942875,
0.11563501507043839,
0.07089279592037201,
-0.... | 0.049764 |
2.5 seconds. When the active node changes, standby nodes update their forwarding connection and open a connection to the new active node. The connection will fail until the new active node starts accepting connections from other nodes in the cluster, so standby nodes retry the connection every 5 seconds as a heartbeat,... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/high-availability.mdx | main | vault | [
-0.006239302456378937,
0.041137486696243286,
-0.05834607407450676,
0.06412158906459808,
-0.01515598502010107,
-0.07981466501951218,
-0.07746648788452148,
-0.015136654488742352,
-0.0013550147414207458,
-0.017053423449397087,
-0.013906882144510746,
0.08272401988506317,
0.03596561402082443,
-... | 0.081385 |
# Security model Due to the nature of Vault and the confidentiality of data it manages, the Vault security model is very critical. The overall goal of Vault's security model is to provide [confidentiality, integrity, availability, accountability, authentication](https://en.wikipedia.org/wiki/Information\_security). Thi... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/security.mdx | main | vault | [
0.03493088111281395,
0.008662124164402485,
-0.05817529559135437,
-0.00594769511371851,
-0.010547051206231117,
-0.013429868966341019,
-0.013510888442397118,
-0.005900662858039141,
0.12136632949113846,
-0.00286009069532156,
0.008913015946745872,
0.07241639494895935,
0.11373873800039291,
-0.0... | 0.024193 |
privilege associated with this client. - Protecting against Vault administrators supplying vulnerable or malicious configuration data. Any data provided as configuration values to Vault's administrative endpoints (e.g. [secret engines](/vault/docs/secrets) configurations), or Vault's configuration files should be valid... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/security.mdx | main | vault | [
0.0017241154564544559,
0.05704920366406441,
-0.06165299192070961,
-0.03660529479384422,
-0.03691021725535393,
-0.05410066246986389,
0.007175268139690161,
0.013497214764356613,
0.11956801265478134,
-0.04389820992946625,
-0.03567584604024887,
0.07638347893953323,
0.07838812470436096,
0.01910... | 0.032712 |
multiple policies are associated with a client), the highest access level permitted is used. For example, if the "engineering" policy permits read/update access to the "eng/" path, and the "ops" policy permits read access to the "ops/" path, then the user gets the union of those. Policy is matched using the most specif... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/security.mdx | main | vault | [
-0.0004884686204604805,
-0.0196261964738369,
-0.06977084279060364,
-0.07675089687108994,
-0.03988370671868324,
-0.07002781331539154,
0.020848233252763748,
0.020930586382746696,
0.059105031192302704,
-0.002553342841565609,
-0.03144357353448868,
0.10333080589771271,
0.06399740278720856,
0.01... | 0.055287 |
# Replication (Vault enterprise) Vault Enterprise 0.7 adds support for multi-datacenter replication. Before using this feature, it is useful to understand the intended use cases, design goals, and high level architecture. Replication is based on a primary/secondary (1:N) model with asynchronous replication, focusing on... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/replication.mdx | main | vault | [
-0.015040348283946514,
-0.021577801555395126,
-0.03566845878958702,
-0.03682917729020119,
-0.009043218567967415,
-0.07322615385055542,
-0.079749196767807,
-0.013620350509881973,
0.0321853831410408,
0.004892755765467882,
-0.03541160374879837,
0.07765384763479233,
0.10966058820486069,
-0.029... | 0.088707 |
there is full network connectivity. If a secondary is down or unable to communicate with the primary, writes are not blocked on the primary and reads are still serviced on the secondary. This ensures the availability of Vault. When the secondary is initialized or recovers from degraded connectivity it will automaticall... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/replication.mdx | main | vault | [
0.0017999437404796481,
0.034328266978263855,
-0.019408566877245903,
0.004524364601820707,
-0.02052084356546402,
-0.036587685346603394,
-0.06535983085632324,
0.001131936558522284,
0.07565174251794815,
-0.024521885439753532,
-0.05013427883386612,
0.12805339694023132,
0.046759139746427536,
-0... | 0.073282 |
cluster is promoted. Vault uses the merkle index as the source of truth, allowing the WAL streams to be completely distinct and unsynchronized. This simplifies administration of Vault Replication for operators. ## Addressing ### Cluster addresses on the primary When a cluster is enabled as replication primary, it persi... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/replication.mdx | main | vault | [
0.008540041744709015,
-0.029722150415182114,
-0.07242347300052643,
0.0700608491897583,
0.07645808905363083,
-0.038578059524297714,
-0.06233077868819237,
-0.058349788188934326,
0.05771859735250473,
-0.03354994207620621,
-0.01865413226187229,
0.09359575808048248,
0.038330983370542526,
-0.060... | 0.109853 |
target addresses the resolver gives to gRPC for regular RPCs to the primary. # Caveats ~> \*\*Mismatched Cluster Versions\*\*: It is not safe to replicate from a newer version of Vault to an older version. When upgrading replicated clusters, ensure that upstream clusters are always on older version of Vault than downst... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/replication.mdx | main | vault | [
-0.027092348784208298,
-0.04295269772410393,
-0.020689651370048523,
0.0035618769470602274,
-0.0034073530696332455,
-0.09262818098068237,
-0.08863822370767593,
-0.030575154349207878,
0.06660959124565125,
-0.02048959583044052,
-0.005098076071590185,
0.07609280198812485,
0.05110539123415947,
... | 0.021354 |
# Vault limits and maximums Vault imposes fixed upper limits on the size of certain fields and objects, and configurable limits on others. Vault also has upper bounds that are a consequence of its underlying storage. This page attempts to collect these limits, to assist in planning Vault deployments. In some cases, the... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/limits.mdx | main | vault | [
0.002495433436706662,
0.03319612517952919,
-0.06873367726802826,
-0.049017876386642456,
0.025728408247232437,
-0.09282533824443817,
-0.10810525715351105,
0.07325231283903122,
0.016569582745432854,
-0.0052789016626775265,
-0.03333976864814758,
0.08423765003681183,
0.11204352974891663,
0.009... | -0.035608 |
for entities and groups. The number is slightly less than the amount that fits in one shard, to reflect the fact that the first shard to fill up will start inducing failures. This maximum will decrease if each entity has a large amount of metadata, or if each group has a large number of members. | | Consul default (512... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/limits.mdx | main | vault | [
0.024898819625377655,
-0.04399564117193222,
-0.06619258224964142,
-0.058696504682302475,
-0.08689077943563461,
-0.07899125665426254,
0.02147987298667431,
0.08666633069515228,
0.07509281486272812,
0.05642326921224594,
0.0005357885966077447,
-0.04408443346619606,
0.11265523731708527,
-0.0153... | 0.081283 |
of a secret | slightly less than one storage entry (512 KiB or 1024 KiB) | | Number of versions of a secret | default 10; configurable per-secret or per-mount | | Maximum number of versions (not checked when configured) | at least 24,000 | Each version of a secret must fit in a single storage entry; the key-value pairs... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/limits.mdx | main | vault | [
0.04642973840236664,
-0.0004906861577183008,
-0.04216323047876358,
-0.02615204267203808,
-0.01380628626793623,
-0.04054814949631691,
-0.07920237630605698,
0.029795527458190918,
0.0013481893111020327,
-0.03629812225699425,
0.008019921369850636,
0.021210797131061554,
0.05518743395805359,
-0.... | -0.025267 |
up to active node capability | ### Lease limits A systemwide [maximum TTL](/vault/docs/configuration#max\_lease\_ttl), and a [maximum TTL per mount point](/vault/api-docs/system/mounts#max\_lease\_ttl-1) can be configured. Although no technical maximum exists, high lease counts can cause degradation in system performan... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/limits.mdx | main | vault | [
-0.009767992421984673,
0.008483474142849445,
-0.053719744086265564,
0.027599649503827095,
-0.03867044672369957,
-0.06203769892454147,
-0.07167337834835052,
0.017161449417471886,
0.028556590899825096,
0.0013589853188022971,
0.007681350223720074,
0.06566563993692398,
0.08402229100465775,
0.0... | 0.054778 |
# Recommended patterns Help keep your Vault environments operating effectively by implementing the following best practice so you avoid common anti-patterns. | Description | Applicable Vault edition | |--- |--- | | [Adjust the default lease time](#adjust-the-default-lease-time) | All | | [Use identity entities for accu... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/recommended-patterns.mdx | main | vault | [
0.04455782100558281,
0.04914214089512825,
-0.015073965303599834,
-0.0500994548201561,
0.0005979873822070658,
-0.05557352304458618,
-0.03607528284192085,
-0.009054778143763542,
-0.04222431406378746,
-0.024515531957149506,
0.03933640196919441,
0.003683473914861679,
0.049963220953941345,
0.01... | 0.087926 |
primary cluster data. The DR cluster does not service reads or writes but you can promote it to replace the primary cluster when needed. - [Disaster recovery replication setup](/vault/tutorials/day-one-raft/disaster-recovery) - [Disaster recovery (DR) replication](/vault/docs/enterprise/replication#disaster-recovery-dr... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/recommended-patterns.mdx | main | vault | [
-0.014941045083105564,
0.01631605066359043,
-0.039990026503801346,
-0.014250443316996098,
0.0006682659732177854,
-0.07748033851385117,
-0.08914335072040558,
0.02459753304719925,
0.021911218762397766,
0.010250061750411987,
-0.007507677655667067,
0.11634467542171478,
0.06540095806121826,
-0.... | 0.081535 |
and performance issues. This could lead to downtime or degradation in your production Vault environment. ## Rotate audit device logs Audit devices in Vault maintain a detailed log of every client request and server response. If you allow the logs for audit devices to run perpetually without rotating you may face a bloc... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/recommended-patterns.mdx | main | vault | [
0.00040591080323792994,
0.03939013555645943,
-0.06541146337985992,
0.002454737201333046,
0.07272761315107346,
-0.10839247703552246,
-0.02113635092973709,
-0.035658031702041626,
0.041576530784368515,
0.028958195820450783,
0.03946538642048836,
0.06889812648296356,
0.051738191395998,
0.026875... | 0.059476 |
rekey](/vault/docs/commands/operator/rekey) \*\*Anti-pattern issue:\*\* If several stakeholders leave the organization, you risk not having the required key shares to meet the unseal quorum, which could result in the loss of the ability to unseal Vault. | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/recommended-patterns.mdx | main | vault | [
-0.02755054086446762,
0.03872096911072731,
-0.02174740470945835,
-0.022621560841798782,
-0.10093844681978226,
0.0017072664340958,
-0.015287806279957294,
-0.052436862140893936,
0.043665967881679535,
0.00544928340241313,
0.006698387674987316,
-0.013935570605099201,
0.04981612414121628,
-0.00... | 0.068269 |
# Telemetry The Vault server process collects various runtime metrics about the performance of different libraries and subsystems. These metrics are aggregated on a 10-second interval and retained for one minute in memory. High-cardinality metrics, like `vault.secret.kv.count`, report every 10 minutes or at an interval... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/telemetry/index.mdx | main | vault | [
0.0488353967666626,
0.019651934504508972,
-0.06075548008084297,
-0.04312395676970482,
-0.028111480176448822,
-0.08485215157270432,
-0.03930962085723877,
0.043057166039943695,
0.04387354850769043,
-0.05764659866690636,
-0.023349853232502937,
0.009853680618107319,
0.038565028458833694,
0.000... | 0.01275 |
# Key metrics for common health checks This document covers common Vault monitoring patterns. It is important to have operational and usage insight into a running Vault cluster to understand performance, assist with proactive incident response, and understand business workloads and use cases. This document consists of ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/telemetry/key-metrics.mdx | main | vault | [
0.0044173672795295715,
-0.011127258650958538,
-0.09314974397420883,
-0.014927249401807785,
0.02579260803759098,
-0.038701605051755905,
-0.01123969815671444,
-0.017388584092259407,
0.04132119566202164,
-0.014447829686105251,
-0.006219728384166956,
0.028277363628149033,
0.0679464191198349,
-... | 0.111118 |
in the number of tokens issued (`vault.token.creation`) it's crucial to investigate the cause of this issue immediately. When a client sends a request to Vault, it typically needs to go through an authentication process to verify its identity and obtain the necessary permissions. This authentication process involves va... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/telemetry/key-metrics.mdx | main | vault | [
0.045368678867816925,
-0.013499351218342781,
-0.0468515045940876,
0.05803876370191574,
-0.011718164198100567,
-0.14881932735443115,
-0.07316415011882782,
0.002210992621257901,
0.06775522977113724,
0.0028057601302862167,
-0.03398184850811958,
0.006914549972862005,
0.00797997321933508,
0.008... | -0.041699 |
client. When the client employs this token, Vault decrypts the stored metadata and fulfills the request. Unlike service tokens, batch tokens do not retain client information or get replicated across clusters. This characteristic alleviates the burden on the storage backend and leads to improved cluster performance. To ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/telemetry/key-metrics.mdx | main | vault | [
0.0015925865154713392,
-0.00479367608204484,
-0.03847750648856163,
0.053624045103788376,
0.0012153323041275144,
-0.054710861295461655,
-0.021630417555570602,
-0.014540676027536392,
0.11049434542655945,
-0.01818491332232952,
-0.0005631198291666806,
0.07156197726726532,
0.060103483498096466,
... | 0.097584 |
before it expires, or request a new one. #### Alerting Monitoring the timely completion of revocation (`vault.expire.revoke`) and renewal (`vault.expire.renew-token`) operations is crucial for ensuring the validity and accessibility of secrets. Some long-running applications may require a token to be renewed instead of... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/telemetry/key-metrics.mdx | main | vault | [
-0.018618715927004814,
0.02457825280725956,
0.0016186092980206013,
0.03306322172284126,
-0.006023932248353958,
-0.0957389622926712,
-0.052006255835294724,
-0.022801561281085014,
0.1267881840467453,
0.010723532177507877,
0.014881130307912827,
0.15029175579547882,
0.020749500021338463,
-0.01... | 0.01507 |
encounter a pair of errors from the audit and core modules for each failed log response. If you receive an error message containing "write: message too long," it suggests that the entries that Vault is trying to write to the syslog audit device exceed the size of the syslog host's socket send buffer. In such cases, it'... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/telemetry/key-metrics.mdx | main | vault | [
0.11240370571613312,
0.008873325772583485,
-0.025146543979644775,
-0.002890193136408925,
0.04145290330052376,
-0.11747761070728302,
-0.019662795588374138,
-0.01681487262248993,
0.0492633618414402,
0.026383182033896446,
0.0014130191411823034,
0.01657572016119957,
0.004249347373843193,
0.040... | -0.007042 |
your Vault clusters allows you to gauge their workload. A sudden decrease in traffic going in or out might indicate communication problems between Vault and its clients or dependencies. Conversely, if you observe an unexpected surge in network activity, it could be a sign of a denial of service (DoS) attack. Knowing th... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/telemetry/key-metrics.mdx | main | vault | [
0.07279723137617111,
0.032966192811727524,
-0.02519330382347107,
0.018033213913440704,
0.013075006194412708,
-0.08233216404914856,
-0.030874427407979965,
-0.021453876048326492,
0.07710473984479904,
-0.007664540782570839,
-0.04698251187801361,
-0.004316095262765884,
0.0660673975944519,
0.03... | -0.000864 |
and secondary clusters are losing synchronization, you can compare the last Write-Ahead Log (WAL) index on both clusters. It's important to detect discrepancies between them because if the secondary clusters are significantly behind the primary and the primary cluster becomes unavailable, any requests made to Vault wil... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/telemetry/key-metrics.mdx | main | vault | [
0.05504509434103966,
-0.05712541192770004,
-0.0443839468061924,
0.07446516305208206,
0.06484343111515045,
-0.07418615370988846,
-0.11565360426902771,
-0.03843633085489273,
0.04296283796429634,
0.011702073737978935,
0.014971096999943256,
0.030632076784968376,
0.04602683335542679,
-0.0708544... | -0.057755 |
# Enable Vault telemetry gathering Collect telemetry data from your Vault installation. ## Before you start - \*\*You must have Vault 1.14 or later installed and running\*\*. - \*\*You must have access to your [Vault configuration](/vault/docs/configuration) file\*\*. ## Step 1: Choose an aggregation agent @include 'te... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/telemetry/enable-telemetry.mdx | main | vault | [
0.0749620720744133,
0.03674507141113281,
-0.06857017427682877,
-0.040714118629693985,
-0.004787431564182043,
-0.08365806192159653,
-0.00563839403912425,
-0.016875265166163445,
0.04861079528927803,
0.0360039584338665,
0.014926858246326447,
-0.022704197093844414,
0.05617670342326164,
-0.0010... | 0.004011 |
# Database telemetry Database telemetry provides general information about configured secrets engines and databases. ## Secrets database metrics @include 'telemetry-metrics/secretsdb-intro.mdx' @include 'telemetry-metrics/database/close.mdx' @include 'telemetry-metrics/database/close/error.mdx' @include 'telemetry-metr... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/telemetry/metrics/database.mdx | main | vault | [
-0.009056957438588142,
-0.00944134034216404,
-0.06565569341182709,
-0.038494326174259186,
-0.06512651592493057,
-0.052931468933820724,
0.05368782579898834,
0.03823250159621239,
-0.04778871685266495,
0.0010397315490990877,
0.027777351438999176,
-0.04880508780479431,
0.09132052958011627,
-0.... | 0.044875 |
# Audit log telemetry Audit log telemetry provides information on the health of your configured audit devices. ## Default metrics @include 'telemetry-metrics/vault/audit/log\_request\_failure.mdx' @include 'telemetry-metrics/vault/audit/log\_request.mdx' @include 'telemetry-metrics/vault/audit/log\_response\_failure.md... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/telemetry/metrics/audit.mdx | main | vault | [
0.03662790730595589,
0.049385592341423035,
-0.028234092518687248,
-0.04840230941772461,
0.03321278467774391,
-0.06657639145851135,
0.06299068033695221,
0.008017891086637974,
0.009698941372334957,
-0.01915399171411991,
0.04974128678441048,
-0.07279597967863083,
0.0543188601732254,
0.0179198... | -0.003926 |
# All Vault telemetry metrics For completeness, we provide a full list of available metrics below in alphabetic order by name. ## Full metric list @include 'telemetry-metrics/database/close.mdx' @include 'telemetry-metrics/database/close/error.mdx' @include 'telemetry-metrics/database/createuser.mdx' @include 'telemetr... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/telemetry/metrics/all.mdx | main | vault | [
0.034389134496450424,
-0.0029758561868220568,
-0.02986943908035755,
-0.07977866381406784,
-0.08243432641029358,
-0.06146153062582016,
0.019117265939712524,
0.017744677141308784,
0.021118996664881706,
-0.012439628131687641,
0.02770964428782463,
-0.01436523161828518,
0.07768270373344421,
0.0... | -0.028115 |
'telemetry-metrics/vault/raft/replication/appendentries/log.mdx' @include 'telemetry-metrics/vault/raft/replication/appendentries/rpc.mdx' @include 'telemetry-metrics/vault/raft/replication/heartbeat.mdx' @include 'telemetry-metrics/vault/raft/replication/installsnapshot.mdx' @include 'telemetry-metrics/vault/raft/rest... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/telemetry/metrics/all.mdx | main | vault | [
0.011184709146618843,
0.0030837475787848234,
-0.03195824474096298,
-0.04285748675465584,
0.015364812687039375,
-0.05362924560904503,
0.02540200762450695,
0.006121404469013214,
-0.025163788348436356,
-0.01130132656544447,
0.07564976066350937,
-0.03423289954662323,
0.06928392499685287,
0.032... | -0.052542 |
# Availability telemetry Availability telemetry provides information about standby and active nodes in your Vault instance. Enterprise installations also include [replication](/vault/docs/enterprise/replication) metrics. ## Default metrics @include 'telemetry-metrics/vault/ha/rpc/client/echo.mdx' @include 'telemetry-me... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/telemetry/metrics/availability.mdx | main | vault | [
0.05849740654230118,
0.017969820648431778,
-0.06032581254839897,
-0.021299030631780624,
-0.003922757226973772,
-0.037043798714876175,
-0.02360893040895462,
0.022790217772126198,
0.0008902975241653621,
-0.015355703420937061,
0.021148724481463432,
-0.01794164627790451,
0.07402089238166809,
-... | 0.032385 |
# Telemetry metrics overview ## Metric types Vault provides three types of telemetry metrics: - \*\*Counter metrics\*\* increment when an event occurs. Counters are cumulative and reset at the end of reporting intervals. - \*\*Gauge metrics\*\* provide measurements of current values. - \*\*Summary metrics\*\* provide o... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/telemetry/metrics/index.mdx | main | vault | [
-0.01201431080698967,
0.0066863372921943665,
-0.07614246010780334,
-0.02640984207391739,
-0.04750923067331314,
-0.029903637245297432,
0.018491331487894058,
0.0318501740694046,
0.1165691390633583,
-0.071945920586586,
0.017622249200940132,
-0.047830723226070404,
0.015016921795904636,
0.01163... | 0.11647 |
# Secrets Sync telemetry Secrets Sync telemetry provides general information about configured sync resources and usage. ## Default metrics @include 'telemetry-metrics/vault/secrets-sync/destinations.mdx' @include 'telemetry-metrics/vault/secrets-sync/associations.mdx' @include 'telemetry-metrics/vault/secrets-sync/reco... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/telemetry/metrics/secrets-sync.mdx | main | vault | [
0.004862526431679726,
-0.007199828512966633,
-0.03413422033190727,
-0.02841612882912159,
-0.015752222388982773,
-0.02834307961165905,
0.01762424409389496,
-0.026904013007879257,
0.006086091510951519,
-0.042013417929410934,
0.017806455492973328,
0.0031183466780930758,
0.06945347785949707,
-... | 0.044774 |
# Authentication telemetry Authentication telemetry provides information on authentication-related objects and operations. ## Identity metrics @include 'telemetry-metrics/vault/identity/entity/active/monthly.mdx' @include 'telemetry-metrics/vault/identity/entity/active/partial\_month.mdx' @include 'telemetry-metrics/va... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/telemetry/metrics/authn.mdx | main | vault | [
0.016291780397295952,
0.031670812517404556,
-0.0459769144654274,
-0.013436461798846722,
0.027263425290584564,
0.008025138638913631,
0.07702603191137314,
0.01214613113552332,
-0.0072183446027338505,
-0.0281447172164917,
0.07033359259366989,
-0.09198831021785736,
0.08421590179204941,
0.00656... | -0.039645 |
# Core system telemetry Core system telemetry provides information about the operational health of your Vault instance. ## Default metrics @include 'telemetry-metrics/vault/core/active.mdx' @include 'telemetry-metrics/vault/core/activity/fragment\_size.mdx' @include 'telemetry-metrics/vault/core/activity/segment\_write... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/telemetry/metrics/core-system.mdx | main | vault | [
0.02269306778907776,
0.034422483295202255,
-0.07893853634595871,
-0.035699956119060516,
-0.026158032938838005,
-0.0871863067150116,
0.052030183374881744,
0.08549148589372635,
0.005852243863046169,
-0.019043955951929092,
0.017217278480529785,
-0.06954080611467361,
0.04961119592189789,
-0.00... | 0.02545 |
# Raft telemetry Raft telemetry provides information on Vault [integrated storage](/vault/docs/configuration/storage/raft). ## Default metrics @include 'telemetry-metrics/vault/raft/apply.mdx' @include 'telemetry-metrics/vault/raft/barrier.mdx' @include 'telemetry-metrics/vault/raft/candidate/electself.mdx' @include 't... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/telemetry/metrics/raft.mdx | main | vault | [
0.035217784345149994,
0.03155357390642166,
-0.049091268330812454,
-0.050279032438993454,
0.0025290425401180983,
-0.05499570071697235,
0.03428835794329643,
0.046147819608449936,
-0.04240679740905762,
-0.02670573815703392,
0.04495967924594879,
-0.06171279773116112,
0.05755447596311569,
0.014... | -0.050961 |
# Secrets telemetry Secrets telemetry provides information about configured secrets engine operations. ## Default metrics @include 'telemetry-metrics/vault/secret/kv/count.mdx' @include 'telemetry-metrics/vault/secret/lease/creation.mdx' ## PKI metrics @include 'telemetry-metrics/secrets/pki/tidy/cert\_store\_current\_... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/telemetry/metrics/secrets.mdx | main | vault | [
-0.028919272124767303,
0.04590299353003502,
-0.03087090700864792,
-0.01100902073085308,
-0.030175022780895233,
-0.07678666710853577,
0.015420502051711082,
0.03510148450732231,
0.02405024878680706,
-0.017620975151658058,
0.06541980803012848,
-0.10935156792402267,
0.058651044964790344,
0.024... | 0.024788 |
# Activity telemetry Activity telemetry provides metric data about Vault behavior related to client usage, request volume and trends over a billing period. ## Default metrics @include 'telemetry-metrics/vault/client/billing\_period/activity.mdx' @include 'telemetry-metrics/vault/identity/entity/active/monthly.mdx' @inc... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/telemetry/metrics/activity.mdx | main | vault | [
0.040011897683143616,
0.006176745984703302,
-0.04611475393176079,
-0.015585901215672493,
-0.002592189470306039,
-0.02654026821255684,
0.05047314241528511,
0.014282964169979095,
0.034291721880435944,
-0.0210723839700222,
0.042484622448682785,
-0.05820899456739426,
0.0724545270204544,
0.0112... | -0.038948 |
# Storage plugin telemetry Storage telemetry provides information on the health of Vault storage and your configured storage backends. For integrated storage metrics, refer to the [Raft telemetry](/vault/docs/internals/metrics/raft) metric list. ## Barrier metrics @include 'telemetry-metrics/vault/barrier/delete.mdx' @... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/telemetry/metrics/storage.mdx | main | vault | [
0.032326389104127884,
0.016186611726880074,
-0.06599961221218109,
-0.024695677682757378,
-0.02343335561454296,
-0.08545457571744919,
0.023180102929472923,
0.0368722528219223,
0.0048267897218465805,
0.005188054405152798,
0.027960162609815598,
-0.04876163229346275,
0.058922480791807175,
0.00... | -0.031432 |
# Automated snapshots telemetry Automated snapshot telemetry provides information on automatically scheduled snapshot activity for the [Raft storage snapshot](/vault/docs/enterprise/automated-integrated-storage-snapshots) feature. ## Default metrics @include 'telemetry-metrics/vault/autosnapshots/last/success/time.mdx'... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/internals/telemetry/metrics/autosnap.mdx | main | vault | [
0.023018978536128998,
0.03647464141249657,
-0.02728004939854145,
-0.041419483721256256,
0.02153574861586094,
-0.03847416117787361,
0.011505436152219772,
0.032502926886081696,
-0.02381202206015587,
0.0011296347947791219,
0.0065407296642661095,
-0.044618960469961166,
0.06379534304141998,
0.0... | 0.019367 |
# Automate Vault cluster snapshots @include 'alerts/enterprise-only.mdx' You can configure Vault Enterprise to regularly save automated snapshots to local or cloud storage. ## Before you start - \*\*You must have a working knowledge of how Vault saves data\*\*. - \*\*You must have a valid Vault cluster configuration us... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/sysadmin/snapshots/automate.mdx | main | vault | [
0.04234883189201355,
0.04861963540315628,
-0.06674551218748093,
-0.04655282571911812,
0.0271628275513649,
0.02485819160938263,
-0.09327244013547897,
-0.003567117964848876,
-0.018066849559545517,
0.03762110695242882,
-0.018621115013957024,
-0.005839228164404631,
0.0654473826289177,
-0.02659... | -0.013494 |
This is to prevent excessive load on the cluster. To enable autoloading, set the `autoload\_enabled` parameter to `true` when creating or updating the automated snapshot configuration. For example, we can update the previous AWS S3 example to enable autoloading: ```json { "storage\_type": "aws-s3", "file\_prefix": "par... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/sysadmin/snapshots/automate.mdx | main | vault | [
-0.006315966602414846,
-0.017315179109573364,
-0.03913791850209236,
0.02537999302148819,
0.045012909919023514,
-0.013588477857410908,
-0.05759477987885475,
-0.03515966236591339,
0.10476015508174896,
0.053824082016944885,
-0.017656799405813217,
-0.030233174562454224,
0.03479514271020889,
-0... | 0.063167 |
# Manage snapshots All Vault editions support data backup and restoration with manual snapshots of the cluster state. Vault Enterprise adds support for configurable automated snapshots to local and cloud storage. When you save and securely retain Vault cluster snapshots, you help defend against data corruption or sabot... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/sysadmin/snapshots/index.mdx | main | vault | [
-0.006549249868839979,
-0.000391528446925804,
-0.021379299461841583,
0.006305904593318701,
0.03630756586790085,
0.005550018046051264,
-0.08058793842792511,
-0.0183393657207489,
0.0027707864064723253,
-0.005095846951007843,
0.01510848943144083,
0.07235977798700333,
0.052211057394742966,
-0.... | 0.082676 |
# Snapshots with integrated storage @include 'alerts/enterprise-only.mdx' Any production system should include a provision for taking regular backups. Vault Enterprise can be configured to take and store snapshots at a specific interval. # Configuration There can be multiple named snapshot configurations, each with the... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/sysadmin/snapshots/automation-overview.mdx | main | vault | [
0.012868120335042477,
0.01671484485268593,
-0.009914225898683071,
-0.023319929838180542,
0.05962600186467171,
-0.004993440117686987,
-0.0365438312292099,
-0.01823466271162033,
0.049298107624053955,
0.019858093932271004,
-0.021101024001836777,
0.03939200937747955,
0.1075267568230629,
-0.065... | 0.004951 |
# Save a Vault snapshot Manually back up data from your Vault cluster with a snapshot. If you are taking snapshots as preparation for a Vault Enterprise upgrade, review the [Automate upgrades with Vault Enterprise](/vault/tutorials/raft/raft-upgrade-automation) tutorial to learn how you can automate your upgrades with ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/sysadmin/snapshots/save.mdx | main | vault | [
0.0163956880569458,
0.019262051209807396,
-0.07570113986730576,
-0.04255472868680954,
0.00394051568582654,
-0.030699949711561203,
-0.06532261520624161,
0.008578203618526459,
-0.05656115710735321,
0.019750747829675674,
0.021321844309568405,
-0.03323841467499733,
0.06887900084257126,
-0.0467... | -0.012233 |
# Restore a Vault snapshot Manually restore data for a Vault cluster leader node with a saved snapshot. ## Before you start - \*\*You must have a working knowledge of how Vault saves data\*\*. - \*\*You must have a valid Vault cluster configuration using integrated storage\*\*. - \*\*You must know, and be able to conta... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/sysadmin/snapshots/restore.mdx | main | vault | [
-0.013522494584321976,
-0.024283720180392265,
-0.010609561577439308,
0.018316257745027542,
-0.017442822456359863,
-0.02418995089828968,
-0.07937348634004593,
-0.016993965953588486,
-0.02189861796796322,
0.01170735340565443,
0.036705221980810165,
0.006483382545411587,
0.08615080267190933,
-... | -0.019266 |
# Recover to a non-replicated cluster @include 'alerts/enterprise-only.mdx' Recover and restore a discrete secret from an integrated storage snapshot to a single, non-replicated cluster. @include 'sysadmin/snapshots/disabled-mount-warning.mdx' ## Before you start @include 'sysadmin/snapshots/restore-requirements/load-s... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/sysadmin/snapshots/recover-a-secret/single-cluster.mdx | main | vault | [
-0.02841009944677353,
0.03519248589873314,
-0.016388578340411186,
-0.03269348666071892,
0.03385977819561958,
-0.0026741826441138983,
-0.02528049610555172,
-0.03754443675279617,
0.04251481220126152,
0.0023451719898730516,
0.02056107297539711,
0.025015683844685555,
0.12933532893657684,
-0.04... | -0.040261 |
# Recover to a replicated cluster @include 'alerts/enterprise-only.mdx' Recover and restore a discrete secret from an integrated storage snapshot to a replicated cluster. @include 'sysadmin/snapshots/disabled-mount-warning.mdx' ## Before you start @include 'sysadmin/snapshots/restore-requirements/load-snapshots.mdx' @i... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/sysadmin/snapshots/recover-a-secret/replicated-cluster.mdx | main | vault | [
-0.005606741178780794,
0.017097637057304382,
-0.01726873777806759,
-0.03470573201775551,
0.04641943424940109,
-0.003490227507427335,
-0.03481462597846985,
-0.03309311345219612,
0.019450560212135315,
-0.021234700456261635,
0.0001245005551027134,
0.040268491953611374,
0.1415274292230606,
-0.... | 0.011252 |
# Recover discrete data from a snapshot @include 'alerts/enterprise-only.mdx' Vault Enterprise features a flexible, robust, and delegatable recovery mechanism for restoring deleted or mistakenly changed secrets from an integrated storage snapshot without resetting the entire cluster to the state in the snapshot. To rec... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/sysadmin/snapshots/recover-a-secret/index.mdx | main | vault | [
-0.03937342017889023,
0.01279357448220253,
-0.0518951416015625,
0.0022941117640584707,
0.033697016537189484,
-0.01642032153904438,
-0.05423456430435181,
-0.03941655158996582,
0.04492655768990517,
-0.0029072256293147802,
0.036979977041482925,
0.09717919677495956,
0.06733498722314835,
-0.053... | -0.02896 |
# File audit device The `file` audit device writes audit logs to a file. This is a very simple audit device: it appends logs to a file. The device does not currently assist with any log rotation. There are very stable and feature-filled log rotation tools already, so we recommend using existing tools. Sending a `SIGHUP... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/audit/file.mdx | main | vault | [
0.0700836181640625,
0.03953246772289276,
-0.08596647530794144,
-0.018730510026216507,
0.03228195011615753,
-0.03329559788107872,
0.02257373556494713,
-0.007727946154773235,
0.059785060584545135,
0.041386134922504425,
0.05056658014655113,
0.04792919382452965,
0.02682347595691681,
0.01587838... | -0.033059 |
# Audit logging With a small set of [exceptions](#exempted-api-endpoints), Vault audit devices record all API requests and responses in detail. An audit device can be a [file](/vault/docs/audit/file), a [syslog server](/vault/docs/audit/syslog), or a [socket](/vault/docs/audit/socket). Refer to the [best practices](/va... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/audit/index.mdx | main | vault | [
0.0753844603896141,
-0.0011418837821111083,
-0.0450955368578434,
0.0031214989721775055,
0.046984411776065826,
-0.08306102454662323,
-0.03192682936787605,
-0.0660666823387146,
0.03865962475538254,
0.01634012721478939,
-0.00010802614997373894,
0.0165715292096138,
0.015446308068931103,
0.0395... | 0.019882 |
quotes in JSON files: ```json { "name": "sidon", "age": "12" } ``` To calculate the keyed hash of any known value for a given audit device, use the [`/sys/audit-hash`](/vault/api-docs/system/audit-hash) API endpoint. Alternatively, you can selectively exempt specific request or response attributes from hashing for each... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/audit/index.mdx | main | vault | [
0.0068519520573318005,
0.10001225769519806,
-0.07524076849222183,
-0.02240622043609619,
0.0012150472030043602,
-0.08958574384450912,
-0.014706435613334179,
0.0004644730070140213,
0.03996681794524193,
-0.0060948883183300495,
0.003958514891564846,
0.02723201923072338,
0.05090826749801636,
0.... | -0.023081 |
# Best practices for audit logging The following recommendations apply generally to most Vault deployments. You should always independently evaluate whether a given recommendation makes sense in the context of your deployment and use of Vault. ## Test configuration changes Always test your audit logging changes in a no... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/audit/best-practices.mdx | main | vault | [
0.07948946952819824,
0.02678811363875866,
-0.0436549112200737,
0.012971377931535244,
0.07264533638954163,
-0.06616824120283127,
-0.03297702968120575,
-0.05379480868577957,
0.011020468547940254,
0.012711433693766594,
0.02662869729101658,
0.000702755234669894,
0.023692188784480095,
0.0496822... | -0.017664 |
helps protect against data loss. ## Configure audit devices Review the configuration options that are specific to the type of audit device, as well as those [common](/vault/api-docs/system/audit#parameters) to all audit device types, and ensure that you configure all audit devices in a way that is appropriate for your ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/audit/best-practices.mdx | main | vault | [
0.015581200830638409,
0.10523547977209091,
-0.010337242856621742,
-0.007767913397401571,
0.050530511885881424,
-0.07391396909952164,
0.0471157543361187,
-0.048481229692697525,
0.08383756130933762,
0.009295125491917133,
0.03259240835905075,
0.028674960136413574,
0.046136923134326935,
0.0226... | 0.037423 |
# Audit log entry schema Vault logs audit entries as individual JSON objects separated by line breaks. Audit log entries include attributes that are common across all API endpoints and endpoint-specific request and response attributes. Audit log entries represent API requests received by Vault and API response sent by ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/audit/schema.mdx | main | vault | [
-0.025724710896611214,
0.0857316330075264,
-0.06532952934503555,
0.02326197549700737,
0.048539310693740845,
-0.08185937255620956,
-0.018820596858859062,
-0.030954331159591675,
0.02529309131205082,
-0.004954455886036158,
-0.030547095462679863,
-0.010193494148552418,
0.06570868194103241,
-0.... | 0.02777 |
first time. Omitted when false. | | `entity\_id` | `string` | If the Vault token is associated with an entity, the ID of that entity. | | `policies` | `list(string)` | List of the names of the ACL policies associated with either the Vault token or the corresponding entity. | | `identity\_policies` | `list(string)` | If... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/audit/schema.mdx | main | vault | [
-0.07058367133140564,
0.033109184354543686,
-0.07540807127952576,
0.04253203794360161,
0.054424092173576355,
-0.03990482911467552,
0.06490745395421982,
-0.022530335932970047,
0.05031142383813858,
-0.05935356020927429,
0.0714176595211029,
-0.026039114221930504,
0.08726087212562561,
0.007494... | 0.006607 |
the client making the request, as seen by Vault. Note that load balancers, proxies, and reverse proxies may all mask the true client's IP address. | | `remote\_port` | `integer` | Port number used by the client making the request, as seen by Vault. | | `headers` | `object` | JSON object containing request headers [conf... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/audit/schema.mdx | main | vault | [
0.013680590316653252,
0.05112622305750847,
-0.06801554560661316,
-0.025683149695396423,
0.006480504758656025,
-0.11293265968561172,
-0.005666313227266073,
-0.009616285562515259,
0.06754140555858612,
0.013038277626037598,
-0.016219545155763626,
0.035662997514009476,
0.027477053925395012,
0.... | 0.090714 |
| | `mount\_running\_plugin\_version` | `string` | Version string for the Vault mount that responded to the API request. | | `mount\_running\_sha256` | `string` | If the mount that received the API request is an external plugin, the SHA-256 hash of the plugin's running version. | | `mount\_is\_external\_plugin` | `bool... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/audit/schema.mdx | main | vault | [
-0.016255956143140793,
0.03245913237333298,
-0.008206982165575027,
-0.04821265488862991,
0.03815111890435219,
-0.07803468406200409,
-0.06757300347089767,
-0.024179356172680855,
0.032863058149814606,
-0.06413760781288147,
0.06265386939048767,
-0.03220982477068901,
0.030156422406435013,
0.06... | -0.04211 |
# Syslog audit device The `syslog` audit device writes audit logs to syslog. It currently does not support a configurable syslog destination, and always sends to the local agent. This device is only supported on Unix systems, and should not be enabled if any standby Vault instances do not support it. ~> \*\*Warning\*\*... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/audit/syslog.mdx | main | vault | [
0.10142160952091217,
0.008175649680197239,
-0.02130655013024807,
-0.03605872392654419,
0.052949294447898865,
-0.07890228927135468,
0.023156780749559402,
-0.026286613196134567,
0.025326455011963844,
0.03748888149857521,
-0.015902481973171234,
-0.00817852932959795,
0.0397525355219841,
0.0324... | -0.015952 |
# Socket audit device The `socket` audit device writes to a TCP, UDP, or UNIX socket. ~> \*\*Warning:\*\* The loss of audit logs may occur when using the UDP socket audit type. Because UDP socket audit type is connectionless, meaning the UDP endpoint becomes unavailable, it’s possible that any number of audit logs writ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/audit/socket.mdx | main | vault | [
0.03933201730251312,
0.0424274243414402,
-0.008106105960905552,
0.003497310448437929,
0.030883030965924263,
-0.06013917177915573,
0.01813867688179016,
-0.056874167174100876,
0.05766639485955238,
0.04963110014796257,
0.026268163695931435,
0.00042435701470822096,
0.04233313724398613,
0.04653... | 0.01379 |
# Vault partner program Official partner integrations provide a verified and seamless user experience for mutual customers. Partners with verified \*\*runtime integrations\*\* or \*\*proprietary plugins\*\* receive one or both of the following partner badges for use on the associated product documentation to provide vi... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/partners/program.mdx | main | vault | [
-0.030989104881882668,
0.07634826749563217,
-0.055000901222229004,
-0.04256046190857887,
0.013948953710496426,
0.03156052529811859,
-0.013538172468543053,
0.038360271602869034,
-0.012655287981033325,
-0.09964539855718613,
0.05444011092185974,
-0.005749494303017855,
0.1006571426987648,
0.00... | 0.06385 |
be working on a similar integration. As much as possible, we try to connect similar parties to avoid duplicate work. ## Step 2: Enable your development ((#step2)) While not mandatory, we strongly encourage you to sign a mutual non-disclosure agreement (MNDA) to allow for open dialog and sharing of ideas between you and... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/partners/program.mdx | main | vault | [
-0.011830129660665989,
-0.030178559944033623,
-0.0694311112165451,
-0.04794446751475334,
-0.008944748900830746,
-0.07984579354524612,
-0.07507346570491791,
0.018117127940058708,
-0.015316345728933811,
-0.07591227442026138,
0.014042191207408905,
-0.009285056963562965,
0.06498552113771439,
-... | 0.070031 |
complete the review process you must: 1. Address all concerns or problems identified by the HashiCorp team. 1. Sign the HashiCorp Technology Partner Agreement 1. Review any applicable logo guidelines and your partner listing. 1. Communicate your plan to support your integration and respond to customer issues. ## Step 5... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/partners/program.mdx | main | vault | [
0.008724644780158997,
0.046150416135787964,
-0.038803212344646454,
-0.06007620319724083,
-0.018630361184477806,
0.01564895547926426,
-0.054010339081287384,
0.007137508597224951,
-0.07223528623580933,
-0.07079637795686722,
0.045450493693351746,
-0.005406126379966736,
0.05741199478507042,
-0... | 0.016389 |
# Verified external key partners To support a variety of use cases, Vault verifies protocol implementation and integrations with partner products, appliances, and applications that support advanced data protection features. @include 'alerts/partner-program.mdx' ## External key management (EKMS) Vault centrally manages ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/partners/external-keys.mdx | main | vault | [
-0.04696701094508171,
-0.014123440720140934,
-0.04684343934059143,
-0.04186464846134186,
-0.016046401113271713,
0.029918605461716652,
0.02712920866906643,
-0.006441817153245211,
0.06712314486503601,
-0.008769816718995571,
0.023305069655179977,
-0.010460343211889267,
0.12276214361190796,
-0... | 0.108571 |
| CDM 9.1 (Edge) | KMIP | 1.16.2+ | N/A | Scality | Scality RING | KMIP | 1.12+ | N/A | Snowflake | Snowflake | KMSE | 1.6+ | N/A | Veeam | Karsten K10 | Transit | 1.9+ | N/A | Veritas | NetBackup | KMIP | 1.13.9+ | N/A | VMware | vSphere 7.0, 8.0 | KMIP | 1.2+ | N/A | VMware | vSan 7.0, 8.0 | KMIP | 1.2+ | N/A | Yugab... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/partners/external-keys.mdx | main | vault | [
-0.021243764087557793,
-0.05350985378026962,
0.04868415743112564,
-0.0406617596745491,
0.006759924814105034,
-0.02163710817694664,
-0.03623406961560249,
0.03384498134255409,
-0.055012576282024384,
0.01125789899379015,
0.023726273328065872,
-0.08277317136526108,
-0.04834714159369469,
-0.098... | 0.172296 |
# Verified protocols To support a variety of use cases, Vault verifies protocol implementation and integrations with partner products, appliances, and applications that support advanced data protection features. ## IPv6 validation and compliance ((#ipv6)) [Vault Enterprise supports IPv6](https://www.hashicorp.com/trust... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/partners/protocols.mdx | main | vault | [
-0.01508057676255703,
0.04175163432955742,
-0.027203546836972237,
-0.07365072518587112,
0.024874063208699226,
-0.005560893565416336,
-0.0980282872915268,
-0.037012338638305664,
-0.0292470995336771,
-0.04209170863032341,
0.04370187968015671,
0.04204915463924408,
-0.012579631991684437,
-0.06... | 0.058116 |
# Verified HSM partners To support a variety of use cases, Vault verifies protocol implementation and integrations with partner products, appliances, and applications that support advanced data protection features. @include 'alerts/partner-program.mdx' ## Auto unsealing and HSM support Hardware Security Module (HSM) su... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/partners/hsm.mdx | main | vault | [
-0.030720937997102737,
0.036803361028432846,
-0.02957954630255699,
-0.025599338114261627,
0.007421555463224649,
0.016656652092933655,
-0.026201117783784866,
-0.005354294087737799,
-0.03541237860918045,
-0.07074420154094696,
0.03727027773857117,
0.06889186799526215,
0.08052654564380646,
-0.... | 0.025338 |
Yes | Yes | Yes | 1.17.2+ ***Last Updated**: May 03, 2023* IBM Z is a broader term and might mean running z/OS as well as Linux on IBM Z mainframe (s390x architecture). Vault is supported on Linux running on IBM Z environment. | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/partners/hsm.mdx | main | vault | [
-0.05208514630794525,
0.012876338325440884,
-0.06540736556053162,
-0.08273087441921234,
0.0024504181928932667,
-0.0635707750916481,
-0.03711877018213272,
0.03833012655377388,
-0.04132227599620819,
-0.058634597808122635,
0.024118218570947647,
0.12013586610555649,
0.07272861897945404,
0.0038... | 0.084237 |
# Password policies A password policy is a set of instructions on how to generate a password, similar to other password generators. These password policies are used in a subset of secret engines to allow you to configure how a password is generated for that engine. Not all secret engines utilize password policies, so c... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/concepts/password-policies.mdx | main | vault | [
-0.07652721554040909,
-0.023895788937807083,
-0.08523954451084137,
-0.059559695422649384,
0.0021681999787688255,
0.017109526321291924,
0.022175569087266922,
-0.06142077594995499,
0.0340588316321373,
-0.010358015075325966,
-0.018800681456923485,
0.06697061657905579,
0.12637552618980408,
0.0... | 0.009672 |
character outside the bounds of the charset. However this can introduce a problem with bias. ### Preventing bias When using the [modulo operation](https://en.wikipedia.org/wiki/Modulo\_operation) to generate a password, you must be very careful to prevent the introduction of bias. When generating a random number betwee... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/concepts/password-policies.mdx | main | vault | [
-0.019113222137093544,
-0.001175620243884623,
-0.0159909687936306,
-0.013580010272562504,
-0.08343393355607986,
0.045884523540735245,
0.019858403131365776,
0.02151038497686386,
0.08395742624998093,
-0.04884638264775276,
-0.024804124608635902,
0.029415326192975044,
0.1035492941737175,
-0.04... | -0.018158 |
{ charset = "abcdefghijklmnopqrstuvwxyz" min-chars = 1 } rule "charset" { charset = "ABCDEFGHIJKLMNOPQRSTUVWXYZ" min-chars = 1 } rule "charset" { charset = "0123456789" min-chars = 1 } rule "charset" { charset = "!@#$" min-chars = 1 } # Fleshes out the rest of the symbols but doesn't add any required characters rule "c... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/concepts/password-policies.mdx | main | vault | [
0.012670561671257019,
0.026497049257159233,
-0.00897443387657404,
0.01966763474047184,
-0.03569605574011803,
0.019877159968018532,
0.042325712740421295,
-0.01884668692946434,
0.12678463757038116,
-0.0365825854241848,
0.047091808170080185,
0.024167286232113838,
0.13164222240447998,
0.006582... | -0.034465 |
"abcdefghijklmnopqrstuvwxyz" min-chars = 1 } rule "charset" { charset = "ABCDEFGHIJKLMNOPQRSTUVWXYZ" min-chars = 1 } rule "charset" { charset = "0123456789" min-chars = 1 } rule "charset" { charset = "!@#$%^&\*" min-chars = 1 } ``` At least one charset must be specified for a policy to be valid. In order to generate a ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/concepts/password-policies.mdx | main | vault | [
-0.04826418310403824,
0.013592628762125969,
-0.06605041772127151,
-0.03089456632733345,
-0.128683939576149,
0.09497126936912537,
0.04027479514479637,
-0.007194068282842636,
0.00340858893468976,
-0.03871604800224304,
0.018505584448575974,
-0.07662832736968994,
0.19831553101539612,
-0.048699... | -0.046778 |
policy Vault ships with a default password policy that applies to any password generated by Vault without an explicit policy assignment. The default policy requires passwords include: - 20 characters total - 1 uppercase character - 1 lowercase character - 1 number - 1 special character ```hcl length = 20 rule "charset"... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/concepts/password-policies.mdx | main | vault | [
0.0015177869936451316,
0.010265910997986794,
-0.0774773433804512,
-0.05189932510256767,
-0.09137701243162155,
0.04035595804452896,
0.007767705246806145,
-0.008582855574786663,
0.044311076402664185,
-0.043777234852313995,
0.018214453011751175,
0.016029946506023407,
0.14180804789066315,
0.00... | -0.065019 |
# Event Notifications @include 'alerts/enterprise-only.mdx' Event notifications are arbitrary, \*\*non-secret\*\* data that can be exchanged between producers (Vault and plugins) and subscribers (Vault components and external users via the API). ## Event types Event types without the `path` metadata field require a roo... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/concepts/events.mdx | main | vault | [
0.057524148374795914,
-0.015024556778371334,
-0.04430033266544342,
-0.02498098462820053,
0.06774922460317612,
-0.06951864063739777,
0.03517511114478111,
-0.012708539143204689,
0.1371770054101944,
-0.02077319473028183,
-0.04544907435774803,
-0.04267672821879387,
0.06395357847213745,
0.03508... | 0.071302 |
`path`, `name`, | 1.21 | | ldap | `ldap/creds-create` | `modified`, `operation`, `path`, `name`, `vault\_index` | 1.21 | | ldap | `ldap/library-check-in` | `modified`, `operation`, `path`, `name`, `vault\_index` | 1.21 | | ldap | `ldap/library-check-out` | `modified`, `operation`, `path`, `name`, `vault\_index` | 1.21 ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/concepts/events.mdx | main | vault | [
0.07291211932897568,
-0.009061161428689957,
-0.12188176065683365,
-0.017171572893857956,
-0.021192079409956932,
-0.05548118054866791,
0.07575911283493042,
0.029771868139505386,
-0.035000547766685486,
0.009671141393482685,
0.06868055462837219,
-0.015412537381052971,
0.11465080827474594,
-0.... | -0.010273 |
`(string)` - the unique ID of the mounted plugin. - `mount\_path` `(string)` - the path that the plugin is mounted at. - `plugin` `(string)` - the name of the plugin, e.g., `kv`. Here is an example event notification in JSON format: ```json { "id": "a3be9fb1-b514-519f-5b25-b6f144a8c1ce", "source": "vault://mycluster", ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/concepts/events.mdx | main | vault | [
-0.029085690155625343,
0.030440347269177437,
-0.035128623247146606,
0.005747865419834852,
0.012166706845164299,
-0.05756111443042755,
0.0033840243704617023,
0.01549011841416359,
0.10955861955881119,
-0.05329045653343201,
0.04414992779493332,
-0.07244998961687088,
0.01612059585750103,
0.077... | 0.066365 |
the `events.alpha1` [experiment option](/vault/docs/configuration#experiments) in your Vault configuration or from the command line with the `-experiments` flag. For example: ```shell-session $ vault server -experiment events.alpha1 ``` | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/concepts/events.mdx | main | vault | [
0.11769644916057587,
0.02470211312174797,
-0.07514072209596634,
0.004261991009116173,
0.03427392616868019,
-0.059032391756772995,
-0.026972569525241852,
-0.05297625809907913,
0.043870959430933,
0.0033257072791457176,
0.0045077186077833176,
-0.007807173766195774,
-0.00945064052939415,
0.008... | -0.00612 |
# Billing start date It is the start of the period for which [automated](/vault/docs/enterprise/license/utilization-reporting) and [manual](/vault/docs/enterprise/license/manual-reporting) license utilization data will be reported for a cluster. This is the license start date if you do not have an explicit billing star... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/concepts/billing-start-date.mdx | main | vault | [
0.04514121636748314,
0.02660994976758957,
-0.07350003719329834,
-0.036519262939691544,
0.006339527666568756,
-0.0064912959933280945,
-0.04094953089952469,
-0.00356306042522192,
0.058914050459861755,
-0.02160065434873104,
-0.031811024993658066,
0.01727316901087761,
0.012089763768017292,
0.0... | -0.016513 |
# Recovery mode Vault can be started using the `-recovery` flag to bring it up in Recovery Mode. The main purpose of recovery mode is to allow direct access to storage in case Vault isn't starting up due to some newly discovered bug. This probably won't be helpful without a Vault expert on hand to advise. Differences b... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/concepts/recovery-mode.mdx | main | vault | [
-0.014204003848135471,
-0.031407542526721954,
-0.007753885816782713,
0.05295640230178833,
0.044035494327545166,
-0.035070132464170456,
-0.05486733093857765,
0.012491310946643353,
-0.014008395373821259,
-0.010757746174931526,
0.015047776512801647,
0.0809590071439743,
0.03158178925514221,
0.... | 0.036332 |
all nodes to agree on what nodes are part of the cluster. | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/concepts/recovery-mode.mdx | main | vault | [
0.07906096428632736,
-0.025524284690618515,
0.00032285365159623325,
0.025370927527546883,
0.09287462383508682,
0.016382873058319092,
-0.020753588527441025,
-0.10648436099290848,
-0.033915236592292786,
0.015975279733538628,
0.01651950739324093,
-0.04623999819159508,
0.028295600786805153,
-0... | 0.151193 |
# Lease, renew, and revoke With every dynamic secret and `service` type authentication token, Vault creates a \_lease\_: metadata containing information such as a time duration, renewability, and more. Vault promises that the data will be valid for the given duration, or Time To Live (TTL). Once the lease is expired, V... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/concepts/lease.mdx | main | vault | [
-0.047406136989593506,
0.07611919939517975,
0.001518446602858603,
0.021057192236185074,
0.011038322001695633,
-0.011165437288582325,
-0.04613671079277992,
-0.0471976101398468,
0.1532059907913208,
0.001405483577400446,
0.04528097063302994,
0.13274376094341278,
0.04347851499915123,
0.0081885... | -0.003938 |
implement token renewal logic in your application code, refer to the [code example in the Authentication doc](/vault/docs/concepts/auth#code-example). ## Prefix-based revocation In addition to revoking a single secret, operators with proper access control can revoke multiple secrets based on their lease ID prefix. Leas... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/concepts/lease.mdx | main | vault | [
0.0006076807039789855,
0.09200220555067062,
0.015699047595262527,
-0.015453319065272808,
-0.04720885679125786,
-0.03667300567030907,
-0.0239879060536623,
-0.0787305161356926,
0.11056704074144363,
0.014584864489734173,
0.015046543441712856,
0.05320071056485176,
0.10949698835611343,
-0.04783... | -0.036821 |
# Secure external data with Vault Not all personally identifiable information (PII) lives in Vault. For example, you may need to store credit card numbers, patient IDs, or social security numbers in an external databases. It can be difficult to secure sensitive data outside Vault and balance the need for applications t... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/concepts/transform.mdx | main | vault | [
-0.07012540102005005,
0.08080415427684784,
-0.05550278350710869,
-0.01936355233192444,
-0.012436040677130222,
-0.04759757220745087,
-0.021036960184574127,
0.042708687484264374,
0.07700373232364655,
-0.04815937951207161,
0.001488834386691451,
0.06272336095571518,
0.073731429874897,
-0.00204... | 0.112992 |
ciphertext made of 16 numbers.  Unlike stand-alone encryption, FPE maintains the original length and data structure for encoded data so the transformed data works with your existing database schema and validation systems. And, unlike tokenization, FPE preserve... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/concepts/transform.mdx | main | vault | [
-0.032874561846256256,
0.09461242705583572,
-0.1195422112941742,
-0.024843115359544754,
0.010282110422849655,
-0.046919599175453186,
0.012135791592299938,
0.051152303814888,
0.09476620703935623,
-0.07550375908613205,
-0.07473677396774292,
0.06620024889707565,
0.010387161746621132,
0.013364... | 0.129172 |
encode operation must perform writes to storage on the primary node of your Vault cluster. As a result, any storage performance limits on the primary node also limits scalability of the encode operation. In comparison, neither Vault transit encryption nor FPE transformation write to storage, and both can be horizontall... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/concepts/transform.mdx | main | vault | [
0.057540085166692734,
-0.03565099835395813,
-0.1044338271021843,
0.013781857676804066,
-0.06168382242321968,
-0.06061490997672081,
-0.07875162363052368,
0.06609049439430237,
0.01871670037508011,
-0.0029776005540043116,
-0.04826705902814865,
0.0786096528172493,
0.06460727751255035,
-0.05021... | -0.006385 |
# Username templating Some of the secrets engines that generate dynamic users for external systems provide the ability for Vault operators to customize how usernames are generated for said external systems. This customization feature uses the [Go template language](https://golang.org/pkg/text/template/). This page desc... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/concepts/username-templating.mdx | main | vault | [
-0.08504889160394669,
0.05348515883088112,
-0.04165621101856232,
-0.04841531440615654,
-0.11555402725934982,
0.005652671679854393,
0.04388980567455292,
0.055643144994974136,
0.046023592352867126,
-0.09637804329395294,
0.017620576545596123,
-0.04488066956400871,
0.04588747024536133,
0.01749... | 0.029631 |
a basic example that references the two fields that are provided to the template. In simplest terms, this is a simple string substitution. ~> This example does not have any randomness and should not be used when generating dynamic usernames. The purpose is to demonstrate referencing data within the Go template language... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/concepts/username-templating.mdx | main | vault | [
-0.00851316936314106,
0.09903215616941452,
0.045609552413225174,
0.018331369385123253,
-0.0841604620218277,
0.0356782004237175,
0.10215995460748672,
0.0776761993765831,
-0.036612603813409805,
-0.09920202940702438,
0.029832707718014717,
-0.07686855643987656,
0.025995692238211632,
-0.0066476... | 0.032865 |
# Tokens Tokens are opaque values so their structure is undocumented and subject to change. Scripts and automations that rely on the internal structure of a token in scripts will break. Tokens are the core method for \_authentication\_ within Vault. Tokens can be used directly or [auth methods](/vault/docs/concepts/aut... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/concepts/tokens.mdx | main | vault | [
0.0008195974514819682,
-0.00865115411579609,
-0.05042647570371628,
0.002828323282301426,
0.006540919654071331,
-0.09160400927066803,
-0.01442768145352602,
0.013554421253502369,
0.08338411897420883,
-0.027927467599511147,
0.009534609504044056,
0.06869889795780182,
0.06851794570684433,
-0.01... | 0.052461 |
root token with an expiration cannot create a root token that never expires 1. By using `vault operator generate-root` ([example](/vault/tutorials/operations/generate-root)) with the permission of a quorum of unseal key holders Root tokens are useful in development but should be extremely carefully guarded in productio... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/concepts/tokens.mdx | main | vault | [
-0.05412228778004646,
-0.042672064155340195,
-0.04269259050488472,
0.007704615127295256,
-0.03320729359984398,
-0.10718631744384766,
-0.13557682931423187,
0.046808354556560516,
0.07581104338169098,
0.01014573872089386,
0.04928377643227577,
0.043619826436042786,
0.06138007715344429,
0.00107... | 0.034973 |
service attack. Finally, the only way to "list tokens" is via the `auth/token/accessors` command, which actually gives a list of token accessors. While this is still a dangerous endpoint (since listing all of the accessors means that they can then be used to revoke all tokens), it also provides a way to audit and revok... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/concepts/tokens.mdx | main | vault | [
-0.047444429248571396,
-0.0017377709737047553,
0.0073550050146877766,
0.013154776766896248,
0.03510785475373268,
-0.03170713037252426,
-0.009409668855369091,
-0.013076312839984894,
0.11298200488090515,
-0.003879035357385874,
0.011251099407672882,
0.08844133466482162,
0.03478853404521942,
0... | 0.112477 |
### Periodic tokens In some cases, having a token be revoked would be problematic -- for instance, if a long-running service needs to maintain its SQL connection pool over a long period of time. In this scenario, a periodic token can be used. Periodic tokens can be created in a few ways: 1. By having `sudo` capability ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/concepts/tokens.mdx | main | vault | [
-0.07516927272081375,
-0.06338981539011002,
-0.022801795974373817,
-0.003971707075834274,
-0.08104374259710312,
-0.07318799942731857,
0.023896340280771255,
0.027318736538290977,
0.09788011014461517,
-0.0037570642307400703,
-0.0193753894418478,
0.0830235555768013,
0.08118326216936111,
0.019... | 0.128327 |
| Yes | No | | Can be Periodic | Yes | No | | Can have Explicit Max TTL | Yes | No (always uses a fixed TTL) | | Has Accessors | Yes | No | | Has Cubbyhole | Yes | No | | Revoked with Parent (if not orphan) | Yes | Stops Working | | Dynamic Secrets Lease Assignment | Self | Parent (if not orphan) | | Can be Used Across... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/concepts/tokens.mdx | main | vault | [
-0.08087684959173203,
-0.038322389125823975,
-0.037986911833286285,
0.061372365802526474,
-0.03668266907334328,
0.004887217655777931,
-0.032970819622278214,
0.0025480680633336306,
0.04874460771679878,
0.028377212584018707,
0.05020122602581978,
0.07432067394256592,
0.05551702901721001,
-0.0... | 0.213108 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.