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 |
|---|---|---|---|---|---|
of the role creation ```text $ vault write ssh-client-signer/roles/my-role -<<"EOH" { "default\_extensions": { "permit-pty": "" } // ... } EOH ``` - As part of the signing operation itself: ```text $ vault write ssh-client-signer/sign/my-role -<<"EOH" { "extensions": { "permit-pty": "" } // ... } EOH ``` ### No port fo... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/ssh/signed-ssh-certificates.mdx | main | vault | [
0.10760034620761871,
0.06059033051133156,
-0.030991196632385254,
-0.035256482660770416,
0.05779002234339714,
-0.049559034407138824,
-0.03168908506631851,
0.0051699369214475155,
-0.06320789456367493,
-0.0383206382393837,
0.08612141758203506,
-0.05106024071574211,
0.049173515290021896,
0.134... | -0.058136 |
# Tokenization transform Not to be confused with Vault tokens, Tokenization exchanges a sensitive value for an unrelated value called a \_token\_. The original sensitive value cannot be recovered from a token alone, they are irreversible. Instead, unlike format preserving encryption, tokenization is stateful. To decode... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/transform/tokenization.mdx | main | vault | [
-0.028178280219435692,
0.030507322400808334,
-0.04362517222762108,
0.005216993857175112,
0.043866828083992004,
-0.06804187595844269,
0.0017801073845475912,
0.01605219393968582,
0.07597862929105759,
-0.019808365032076836,
-0.01879728026688099,
0.06131133809685707,
0.042595990002155304,
-0.0... | 0.057387 |
on primary nodes, the scalability of the encode operation is limited by the primary's storage performance. Additionally, using internal storage, since writes must be performed on primary nodes, the scalability of the encode operation will be limited by the performance of the primary and its storage subsystem. All other... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/transform/tokenization.mdx | main | vault | [
-0.008581050671637058,
-0.018860843032598495,
-0.050652436912059784,
-0.001593920635059476,
-0.02366296574473381,
-0.09579051285982132,
-0.07781760394573212,
0.08546485751867294,
0.050817832350730896,
0.01587829180061817,
-0.03844846785068512,
0.06160658597946167,
0.035543207079172134,
-0.... | 0.157509 |
table to determine if it needs to create or modify the tables when using that endpoint. If you make changes to those tables yourself, the automatic schema management may become out of sync and may fail in the future. External stores may often be preferred due to their ability to achieve a much higher scale of performan... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/transform/tokenization.mdx | main | vault | [
0.003625123528763652,
-0.03887201100587845,
-0.0761924684047699,
0.009242981672286987,
0.028818733990192413,
-0.00806319247931242,
-0.02748974785208702,
0.010903256013989449,
0.02979924902319908,
0.044860366731882095,
0.03851205110549927,
0.0038961204700171947,
0.027691753581166267,
-0.025... | 0.084943 |
# Transform secrets engine @include 'alerts/enterprise-and-hcp.mdx' Transform secrets engine requires [Vault Enterprise](https://www.hashicorp.com/products/vault/pricing) with the Advanced Data Protection Transform (ADP-Transform) module. The Transform secrets engine handles secure data transformation and tokenization ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/transform/index.mdx | main | vault | [
-0.08259017020463943,
0.08578356355428696,
-0.0947474017739296,
-0.03938135504722595,
-0.027921373024582863,
-0.04566217586398125,
-0.016962168738245964,
-0.023989245295524597,
0.03270493447780609,
-0.05338691547513008,
-0.014639294706285,
0.05401448905467987,
0.03963852301239967,
-0.04079... | 0.121586 |
and other transformation-specific values such as the tweak source or the masking character to use. - \*\*Templates\*\* allow us to determine what and how to capture the value that we want to transform. - \*\*Alphabets\*\* provide the set of valid UTF-8 character contained within both the input and transformed value on ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/transform/index.mdx | main | vault | [
-0.0844387337565422,
0.028919097036123276,
-0.09520386904478073,
-0.01335155125707388,
0.001135844737291336,
-0.019226672127842903,
0.022843701764941216,
-0.025999097153544426,
0.058750346302986145,
-0.08443010598421097,
-0.05112583935260773,
-0.025659730657935143,
-0.05329995974898338,
-0... | 0.093203 |
value is an encrypted version of the input with the format preserved. However, the value itself may be \_invalid\_ with respect to other standards. For example the output credit card number may not validate (it likely won't create a valid check digit). So one must consider when the outputs are stored whether validation... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/transform/index.mdx | main | vault | [
-0.05384349450469017,
0.07070492208003998,
-0.05338037759065628,
0.008596299216151237,
-0.0077189733274281025,
-0.013455634005367756,
0.01908915862441063,
-0.0056606922298669815,
0.08470243960618973,
-0.05313745513558388,
-0.014564935117959976,
0.026144366711378098,
0.039804305881261826,
-... | 0.103838 |
a resource: - A transformation cannot be deleted if it's in use by a role. - A template or store cannot be deleted if it's in use by a transformation. - An alphabet cannot be deleted if it's in use by a template. ## Provided builtin resources The secret engine provides a set of builtin templates and alphabets that are ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/transform/index.mdx | main | vault | [
-0.13928988575935364,
0.07922068983316422,
-0.0538853295147419,
-0.023856058716773987,
0.018903210759162903,
0.061872728168964386,
-0.001516040530987084,
-0.08764734864234924,
0.05638682469725609,
-0.11127215623855591,
0.002666797488927841,
0.07328679412603378,
-0.015657177194952965,
-0.00... | 0.096659 |
Generate an ephemeral 256-bit AES key. 2. Wrap the target key using the ephemeral AES key with AES-KWP. 3. Wrap the AES key under the Vault wrapping key using RSAES-OAEP with MGF1 and either SHA-1, SHA-224, SHA-256, SHA-384, or SHA-512. 4. Delete the ephemeral AES key. 5. Append the wrapped target key to the wrapped AE... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/transform/index.mdx | main | vault | [
-0.030023396015167236,
0.07817845046520233,
-0.06253986805677414,
0.013511626049876213,
-0.01912582293152809,
-0.051400698721408844,
-0.06795990467071533,
-0.02589220181107521,
0.015598024241626263,
0.003692583180963993,
-0.00200840481556952,
-0.003946851938962936,
0.033653296530246735,
-0... | -0.071164 |
# FF3-1 tweak usage documentation The Vault's transform secrets engine uses the FF3-1 algorithm for FPE (format preserving encryption) transformations. The key benefit of format preserving encryption schemes is that it allows for the secure encryption of plaintexts over small domain spaces [1]. However, this comes with... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/transform/ff3-tweak-details.mdx | main | vault | [
-0.0851973295211792,
0.04933163523674011,
-0.11051598191261292,
0.006397966295480728,
0.01084833312779665,
-0.05881265550851822,
-0.0023161894641816616,
-0.014554882422089577,
0.03800931200385094,
-0.05368064343929291,
-0.025500498712062836,
0.02745254710316658,
-0.009565574117004871,
-0.0... | -0.008084 |
randomly chosen tweaks should have high entropy within each half of the tweak. In the worst case scenario, creating many encryptions with tweaks with the same right or left half will lead to more biased encryptions (where the distinction between the corresponding encryptions rely solely on the randomness of the abelian... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/transform/ff3-tweak-details.mdx | main | vault | [
-0.11064593493938446,
0.041547052562236786,
0.009644986130297184,
0.032220952212810516,
0.0016186924185603857,
-0.06126643344759941,
0.00001093302580557065,
-0.048925790935754776,
0.041248176246881485,
-0.016345979645848274,
-0.02448246069252491,
0.032731395214796066,
-0.0194977056235075,
... | -0.020201 |
# Use the ACME protocol with the PKI plugin The Automatic Certificate Management Environment (ACME) protocol is an IETF standardized protocol, [RFC 8555](https://datatracker.ietf.org/doc/html/rfc8555), that lets you automate the way clients prove control over a domain name and request a leaf certificate from an ACME ce... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/acme.mdx | main | vault | [
-0.11343937367200851,
0.054708413779735565,
-0.07215342670679092,
0.03182590380311012,
-0.010523668490350246,
-0.08343569934368134,
-0.01194596104323864,
0.03411524370312691,
0.038821496069431305,
-0.052235040813684464,
-0.02700601890683174,
-0.08628594875335693,
0.09739018976688385,
0.118... | 0.038497 |
Certbot: ```shell-session $ certbot certonly \ --server https://localhost:8200/v1/pki/acme/directory \ --eab-kid \ --eab-hmac-key ``` With or without EAB, requests from the ACME client do not use traditional Vault authentication. Instead, the requests authenticate through the ACME protocol. With EAB, a Vault authentica... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/acme.mdx | main | vault | [
-0.05440395325422287,
0.03316005319356918,
-0.09274594485759735,
0.016876468434929848,
-0.015083800069987774,
-0.05982181802392006,
-0.008192935958504677,
0.08662442862987518,
0.03072475455701351,
-0.032796312123537064,
0.057015370577573776,
-0.0475643165409565,
0.09015189111232758,
0.0305... | -0.012906 |
# Quick start: root CA setup This document provides a brief overview of setting up a Vault PKI Secrets Engine with a Root CA certificate. #### Mount the backend The first step to using the PKI backend is to mount it. Unlike the `kv` backend, the `pki` backend is not mounted by default. ```shell-session $ vault secrets ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/quick-start-root-ca.mdx | main | vault | [
0.004248421173542738,
0.036199480295181274,
-0.05339832231402397,
-0.014711697585880756,
-0.03947468101978302,
-0.06468294560909271,
-0.10637881606817245,
0.08875948935747147,
0.048660460859537125,
-0.037304576486349106,
0.041638027876615524,
-0.005608001258224249,
0.09264377504587173,
0.0... | -0.060299 |
credentials using the `example-dot-com` role configuration. Here we see the dynamically generated private key and certificate. Using ACLs, it is possible to restrict using the pki backend such that trusted operators can manage the role definitions, and both users and applications are restricted in the credentials they ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/quick-start-root-ca.mdx | main | vault | [
-0.026234857738018036,
0.01862395741045475,
-0.0870964527130127,
0.019796185195446014,
-0.049589645117521286,
-0.05791446939110756,
-0.015293285250663757,
0.057511862367391586,
-0.0009964974597096443,
-0.050970498472452164,
-0.03268233686685562,
-0.004559332504868507,
0.1193522959947586,
0... | -0.04179 |
# PKI secrets engine @include 'x509-sha1-deprecation.mdx' If you are using Vault 1.11.0+ as a Connect CA, run a Consul version which includes the fix for [GH-15525](https://github.com/hashicorp/consul/pull/15525). Refer to this [Knowledge Base article](https://support.hashicorp.com/hc/en-us/articles/11308460105491) for... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/index.mdx | main | vault | [
-0.05200430005788803,
0.0355067178606987,
-0.0017090170877054334,
-0.04357144981622696,
-0.0318615548312664,
-0.10411085188388824,
-0.07041776180267334,
0.012323291972279549,
0.09620928019285202,
-0.03890756517648697,
0.010978263802826405,
0.06556601077318192,
0.05658147111535072,
0.053007... | -0.036505 |
# Quick start: intermediate CA setup In the [first Quick Start guide](/vault/docs/secrets/pki/quick-start-root-ca), certificates were issued directly from the root certificate authority. As described in the example, this is not a recommended practice. This guide builds on the previous guide's root certificate authority... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/quick-start-intermediate-ca.mdx | main | vault | [
0.02892833761870861,
0.064760223031044,
0.003044327488169074,
-0.028808189556002617,
-0.03590770065784454,
-0.09181564301252365,
-0.061880651861429214,
0.039458371698856354,
0.035639408975839615,
-0.04043206572532654,
0.04978335648775101,
0.00023370290000457317,
0.10658453404903412,
0.0714... | -0.14728 |
e9t+2iwryh5+rnq+pg6anmgwHldptJc1XEFZA2UUQ89RP7kOGQF6IkIS -----END RSA PRIVATE KEY----- private\_key\_type rsa serial\_number 3e:20:32:c6:af:a7:20:4e:b1:95:67:fb:86:bc:cb:90:f4:31:b6:f3 ``` Vault has now generated a new set of credentials using the `example-dot-com` role configuration. Here we see the dynamically genera... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/quick-start-intermediate-ca.mdx | main | vault | [
-0.06820264458656311,
0.004324374254792929,
-0.039674513041973114,
0.012205330654978752,
-0.018100358545780182,
-0.02192082069814205,
-0.04168599843978882,
0.05681883543729782,
0.013048844411969185,
-0.027719637379050255,
-0.005268421024084091,
-0.020795252174139023,
0.08443789184093475,
0... | -0.031103 |
# Certificate Issuance External Policy Service (CIEPS) This document covers high-level architecture and service APIs used by the Vault PKI Secrets Engine when communicating with the Certificate Issuance External Policy Service (CIEPS) . ## What is Certificate Issuance External Policy Service (CIEPS)? Hashicorp Vault's ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/cieps.mdx | main | vault | [
-0.11480249464511871,
0.07897739857435226,
-0.03554491326212883,
-0.04262566193938255,
0.010052626021206379,
-0.10650718957185745,
-0.0024521835148334503,
0.05729788541793823,
0.10437726974487305,
-0.025034287944436073,
0.05205985903739929,
-0.029625385999679565,
0.07705862075090408,
0.041... | 0.102652 |
its key material or delegate key creation to the trusted Vault service, with no impact on the functionality CIEPS can provide. The CIEPS service can be scoped to respond to requests from either a single PKI mount or multiple, getting information about the requesting user and the Vault PKI instance from the CIEPS messag... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/cieps.mdx | main | vault | [
-0.09056621044874191,
0.09778272360563278,
-0.059632666409015656,
-0.07243183255195618,
-0.010139448568224907,
-0.08706432580947876,
0.003125273622572422,
0.0002465104917064309,
0.11543525010347366,
-0.03950212150812149,
0.035717807710170746,
-0.015488998964428902,
0.08466584980487823,
-0.... | 0.112233 |
Unverified contact information submitted by the requesting ACME account on creation. - `created\_date` `(string: RFC 3999 format)` - Timestamp when the account was created. - `eab` `(map[string]interface{}, optional)` - When present, the details of the EAB used to authorize this account via Vault authentication. If not... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/cieps.mdx | main | vault | [
-0.0706402137875557,
0.024609385058283806,
-0.10563406348228455,
0.002381628844887018,
-0.009684666059911251,
-0.05442133918404579,
0.08182880282402039,
0.015183774754405022,
0.04117391258478165,
-0.015812866389751434,
0.020872794091701508,
-0.05823247879743576,
0.08655038475990295,
-0.022... | 0.019633 |
the above request, only one of the `certificate` or `error` fields should be specified. In the event both `certificate` and `error` are present, the `error` will be appended to the returned `warnings` and the `certificate` will be issued. Using the `application/json` content type, the server should reply with the follo... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/cieps.mdx | main | vault | [
-0.04500337317585945,
0.09443929046392441,
-0.06132893264293671,
-0.01979655772447586,
-0.018132049590349197,
-0.08927366882562637,
0.035142961889505386,
0.05812884494662285,
0.001773928408510983,
-0.052052438259124756,
0.0032147748861461878,
-0.07374794036149979,
0.1257496029138565,
0.049... | -0.04082 |
# PKI secrets engine considerations To successfully deploy this secrets engine, there are a number of important considerations to be aware of, as well as some preparatory steps that should be undertaken. You should read all of these \_before\_ using this secrets engine or generating the CA to use with this secrets engi... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/considerations.mdx | main | vault | [
-0.026630045846104622,
-0.013692278414964676,
-0.011898456141352654,
0.020250611007213593,
-0.0159942377358675,
-0.024153556674718857,
-0.06607749313116074,
-0.005120697431266308,
-0.05577810853719711,
-0.020212676376104355,
0.03707383573055267,
-0.05548451095819473,
0.07685454189777374,
0... | 0.066252 |
The operations on a root should generally be limited to issuing and revoking intermediate CAs, which is a highly privileged operation; it becomes much easier to audit these operations when they're in a separate mount than if they're mixed in with day-to-day leaf issuance. A common pattern is to have one mount act as yo... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/considerations.mdx | main | vault | [
-0.0642511323094368,
0.004044703207910061,
0.005366315133869648,
-0.020155880600214005,
-0.006632974836975336,
-0.07025985419750214,
-0.12197377532720566,
0.030792316421866417,
0.05003027990460396,
-0.06473007053136826,
0.1010897159576416,
0.04170314595103264,
0.1131686344742775,
0.0579199... | -0.100775 |
than EC key generation. If performance and throughput are a necessity, consider using EC keys (including NIST P-curves and Ed25519) instead of RSA. - Key signing requests (via `/pki/sign`) will be faster than (`/pki/issue`), especially for RSA keys: this removes the necessity for Vault to generate key material and can ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/considerations.mdx | main | vault | [
0.0073351324535906315,
0.0815487802028656,
-0.02126345783472061,
0.025185393169522285,
0.029065169394016266,
-0.06734040379524231,
-0.10237531363964081,
0.04787063971161842,
0.1118476614356041,
-0.01424500998109579,
0.0033015613444149494,
0.04787038639187813,
0.0722062811255455,
-0.0306247... | 0.06131 |
This allows for several layers of separation of concerns between TLS-based services. ### Cross-Signed intermediates When cross-signing intermediates from two separate roots, two separate intermediate issuers will exist within the Vault PKI mount. In order to correctly serve the cross-signed chain on issuance requests, ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/considerations.mdx | main | vault | [
-0.0483505018055439,
0.023977244272828102,
-0.015459689311683178,
-0.030694667249917984,
0.017854493111371994,
-0.10233908891677856,
-0.06995943188667297,
0.02735196053981781,
0.06931953877210617,
-0.04603354260325432,
0.042049940675497055,
0.03327938914299011,
0.08164150267839432,
0.05093... | 0.025192 |
Use a restrictive [`allowed\_roles`, `allowed\_issuers`, and `default\_directory\_policy` ACME configuration](/vault/api-docs/secret/pki#set-acme-configuration) to let only a single role and issuer be used. This prevents user choice, allowing some global restrictions to be placed on issuance and avoids requiring ACME c... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/considerations.mdx | main | vault | [
-0.035310298204422,
0.036487579345703125,
-0.05785003677010536,
0.018469849601387978,
0.009776619262993336,
-0.05132319778203964,
0.044104453176259995,
0.03438542038202286,
0.020124545320868492,
-0.02924364246428013,
0.0373430997133255,
-0.01903611049056053,
0.11142246425151825,
0.07860367... | -0.010252 |
paths; a client could use a HTTP challenge to force Vault to reach out to a server on a network it could otherwise not access. ### ACME and client counting In Vault 1.14, ACME contributes differently to usage metrics than other interactions with the PKI Secrets Engine. Due to its use of unauthenticated requests (which ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/considerations.mdx | main | vault | [
-0.06870520859956741,
-0.009075668640434742,
-0.02436893805861473,
0.03495444357395172,
0.011127956211566925,
-0.04484621807932854,
-0.01588871330022812,
0.023794123902916908,
0.15829457342624664,
-0.05096380412578583,
-0.02987281233072281,
0.04382411018013954,
0.11465618759393692,
0.05580... | 0.006857 |
with lots of certificates, it will be done on a schedule rather than on demand. ### NotAfter behavior on leaf certificates In Vault 1.11.0, the PKI Secrets Engine has introduced a new `leaf\_not\_after\_behavior` [parameter on issuers](/vault/api-docs/secret/pki#leaf\_not\_after\_behavior). This allows modification of ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/considerations.mdx | main | vault | [
-0.04516664892435074,
0.0715814009308815,
-0.025682900100946426,
0.024939728900790215,
0.04913556948304176,
-0.11028441786766052,
-0.11428548395633698,
-0.009970315732061863,
0.0643547847867012,
-0.04693654924631119,
0.08093030750751495,
0.041523344814777374,
0.07338792830705643,
0.0475590... | -0.039564 |
If they point to the wrong issuer's information, these applications may break. ## Distribution of CRLs and OCSP Both CRLs and OCSP allow interrogating revocation status of certificates. Both of these methods include internal security and authenticity (both CRLs and OCSP responses are signed by the issuing CA within Vau... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/considerations.mdx | main | vault | [
-0.08736908435821533,
0.056866079568862915,
-0.010141696780920029,
0.02503373846411705,
-0.027319712564349174,
-0.13760001957416534,
-0.05720595642924309,
0.00686426879838109,
0.1125323548913002,
-0.05605473741889,
-0.005720615852624178,
0.04943756014108658,
0.04978654906153679,
0.00726620... | -0.100599 |
[Performance Replication](/vault/docs/enterprise/replication#performance-replication). In a replicated PKI Secrets Engine mount, issuer and role information is synced between the Performance Primary and all Performance Secondary clusters. However, each Performance Secondary cluster has its own local storage of issued c... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/considerations.mdx | main | vault | [
-0.020618824288249016,
0.06985301524400711,
-0.04815443232655525,
0.01629548706114292,
-0.01882302016019821,
-0.12240201979875565,
-0.06579016894102097,
-0.03802400082349777,
0.09146921336650848,
-0.05729655176401138,
0.012738408520817757,
0.09458040446043015,
0.09076017141342163,
-0.01626... | -0.039958 |
issuer name. This can be avoided by using OCSP to track revocation, but note that performance characteristics are different between OCSP and CRLs. ~> Note: As of Go 1.20 and Vault 1.13, Go correctly formats the CRL's issuer name and this notice [does not apply](https://github.com/golang/go/commit/a367981b4c8e3ae955eca9... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/considerations.mdx | main | vault | [
-0.026201186701655388,
0.07492721080780029,
-0.026523223146796227,
0.0010138105135411024,
-0.016651615500450134,
-0.041524771600961685,
-0.07054077088832855,
0.016965268179774284,
0.07082214206457138,
-0.056736987084150314,
0.02864135429263115,
0.006429370958358049,
0.06265820562839508,
0.... | -0.076884 |
Beyond Vault's default telemetry around request processing, PKI exposes count and duration metrics for the issue, sign, sign-verbatim, and revoke calls. The metrics keys take the form `mount-path,operation,[failure]` with labels for namespace and role name. Note that these metrics are per-node and thus would need to be... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/considerations.mdx | main | vault | [
0.013524566777050495,
0.03847768157720566,
0.007826912216842175,
0.007070344407111406,
-0.03180841729044914,
-0.13808095455169678,
-0.02089071460068226,
0.002786509459838271,
0.11149120330810547,
-0.016978241503238678,
0.026293281465768814,
-0.030037900432944298,
0.09179339557886124,
0.036... | -0.087309 |
of the CA which issued the requested certificate, - `serial\_number` - the serial number of the certificate that was issued, - `error` - to show errors associated with the request, and - `ca\_chain` - optional due to noise; the full CA chain of the issuer of the requested certificate. ~> Note: These list of parameters ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/considerations.mdx | main | vault | [
-0.06843928247690201,
0.08023175597190857,
-0.02867651730775833,
-0.03989924117922783,
-0.014420541003346443,
-0.03454463928937912,
-0.0014840306248515844,
-0.02517644874751568,
0.016517160460352898,
-0.05879918485879898,
0.0744338408112526,
0.011538365855813026,
0.09062690287828445,
0.023... | -0.101111 |
| | `/config/ca` | Read | Yes | Yes | | | | | `/config/crl` | Read | Yes | Yes | | | | | `/config/issuers` | Read | Yes | Yes | | | | | `/crl/rotate` | Read | Yes | Yes | | | | | `/crl/rotate-delta` | Read | Yes | Yes | | | | | `/roles/:role` | Write | Yes | Yes | | | | | `/issuer/:issuer\_ref` | Read | Yes | Yes | | |... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/considerations.mdx | main | vault | [
-0.021269986405968666,
0.03172268345952034,
-0.039829619228839874,
0.05918283388018608,
-0.028652917593717575,
-0.010440945625305176,
0.06716067343950272,
-0.006856022402644157,
-0.04629925638437271,
0.0239598099142313,
0.12181705236434937,
-0.013370854780077934,
0.0689152255654335,
-0.012... | 0.010625 |
Config | Yes | | URL Config | Yes | | Issuer Config | Yes | | Key Config | Yes | | CRL | No | | Revoked Certificates | No | | Leaf/Issued Certificates | No | | Certificate Metadata | No | The main effect is that within the PKI secrets engine leaf certificates issued with `no\_store` set to `false` are stored local to t... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/considerations.mdx | main | vault | [
-0.002442060736939311,
0.03884578496217728,
-0.03143453970551491,
0.08502371609210968,
0.06120142713189125,
-0.059226445853710175,
-0.05604218691587448,
-0.004224681295454502,
0.0960027202963829,
-0.03860044106841087,
0.04750010371208191,
0.05616888031363487,
0.05562041699886322,
-0.041458... | 0.076062 |
signing CSRs with the PSS signature algorithm. If using a managed key that requires a RSA PSS algorithm (such as GCP or a PKCS#11 HSM) as a backing for an intermediate CA key, attempting to generate a CSR (via `pki/intermediate/generate/kms`) will fail signature verification. In this case, the CSR will need to be gener... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/considerations.mdx | main | vault | [
-0.04126755893230438,
0.05808747932314873,
-0.030059542506933212,
0.017503859475255013,
0.027477409690618515,
-0.08481718599796295,
-0.05170084908604622,
0.05743081867694855,
0.054259251803159714,
-0.052363425493240356,
0.018058963119983673,
0.026704704388976097,
0.10746943205595016,
0.018... | -0.145378 |
# Certificate Management Protocol v2 (CMPv2) This document summarizes Vault's PKI Secrets Engine implementation of the [CMPv2 protocol](https://datatracker.ietf.org/doc/html/rfc4210) , its configuration, and limitations. ## What is Certificate Management Protocol v2 (CMPv2)? The CMP protocol is an IETF standardized pro... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/cmpv2.mdx | main | vault | [
-0.03463761880993843,
0.04741085320711136,
0.0023373966105282307,
-0.01957111619412899,
-0.019184980541467667,
-0.0746917650103569,
-0.07724107056856155,
0.04170619323849678,
-0.01911735348403454,
-0.044988490641117096,
0.03438564017415047,
-0.04016173630952835,
0.0725327581167221,
0.08458... | 0.046916 |
set it enabled and configure default path policy and authentication. ```shell-session vault write pki/config/cmp -< | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/cmpv2.mdx | main | vault | [
0.056462887674570084,
0.08233051002025604,
-0.02502082847058773,
-0.049904964864254,
-0.05863676965236664,
0.0010539231589064002,
-0.05052865669131279,
0.052120283246040344,
0.032209571450948715,
0.059643734246492386,
0.013441246002912521,
-0.008204241283237934,
0.037588849663734436,
0.109... | -0.014058 |
# PKI secrets engine - rotation primitives Since Vault 1.11.0, Vault's PKI Secrets Engine supports multiple issuers in a single mount point. By using the certificate types below, rotation can be accomplished in various situations involving both root and intermediate CAs managed by Vault. ## X.509 certificate fields X.5... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/rotation-primitives.mdx | main | vault | [
-0.08946757018566132,
0.0971214696764946,
-0.04651477932929993,
-0.07731448113918304,
-0.011498005129396915,
-0.06979550421237946,
-0.07886997610330582,
0.027438197284936905,
0.09257655590772629,
-0.06037047132849693,
0.0419023372232914,
0.06082959100604057,
0.12350556254386902,
0.03119212... | -0.059973 |
the store (such as intermediates). - The [Issuer](https://datatracker.ietf.org/doc/html/rfc5280#section-4.1.2.4) and [signatureValue](https://datatracker.ietf.org/doc/html/rfc5280#section-4.1.1.3) of this certificate. - In the issued certificate's Issuer field, the issuing certificate places its own Subject value. This... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/rotation-primitives.mdx | main | vault | [
-0.009926942177116871,
0.09565428644418716,
-0.04950953647494316,
-0.02285328134894371,
0.05682569369673729,
-0.05951966345310211,
0.022244768217206,
0.000020054832930327393,
0.06730058044195175,
-0.06659428775310516,
0.04487749934196472,
-0.0022490499541163445,
0.10373077541589737,
0.0248... | -0.012329 |
Encrypt has successfully rotated intermediates to present a cross-signed chain ([for older Android devices](https://letsencrypt.org/2020/12/21/extending-android-compatibility.html)). Assuming the old intermediate's parent(s) are still valid and trusted, certificates issued under old intermediates should continue to val... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/rotation-primitives.mdx | main | vault | [
-0.06416602432727814,
-0.014097965322434902,
0.040865637362003326,
-0.10088815540075302,
0.019607732072472572,
-0.0732981488108635,
-0.11240946501493454,
0.02369060181081295,
0.04882191866636276,
-0.04490549489855766,
0.0746336504817009,
0.10977305471897125,
0.12862543761730194,
0.02535526... | -0.09292 |
| ------------------- ``` The above process results in two trust paths: either of root A or root B (or both) could exist in the client's trust stores and the leaf certificate would validate correctly. Because the same key material is used for both intermediate certificates (C and D), the issued leaf certificate's signa... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/rotation-primitives.mdx | main | vault | [
-0.07271014153957367,
0.00723687931895256,
0.004228518810123205,
-0.028384067118167877,
0.08243867009878159,
-0.06128183752298355,
-0.013833698816597462,
0.03687048703432083,
0.023020736873149872,
-0.08160814642906189,
0.06525219976902008,
-0.03170125558972359,
0.12472759187221527,
0.02360... | -0.087847 |
Unlike the cross-signed primitive, this primitive type can be used on all types of certificates (including leaves, intermediates, and roots). #### Process flow ``` ------------------- | generate key pair | ---------------> ... ------------------- ... | | ... -------------- -------------- ... | generate CSR | <-> | gene... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/rotation-primitives.mdx | main | vault | [
-0.06587283313274384,
0.06913992762565613,
-0.08226048201322556,
-0.011334951967000961,
-0.027734454721212387,
-0.08954577893018723,
-0.03940083831548691,
0.06857611984014511,
0.02125193551182747,
-0.019670395180583,
0.006595882587134838,
-0.09047592431306839,
0.08968184143304825,
-0.05055... | 0.04629 |
to new keys and extend their lifetimes. This time-based rotation is what ultimately allows us to rotate root certificates. There's two main variants of this: a \*\*forward\*\* primitive, wherein an old certificate is used to bless new key material, and a \*\*backwards\*\* primitive, wherein a new certificate is used to... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/rotation-primitives.mdx | main | vault | [
-0.09237653017044067,
-0.03148410841822624,
0.004737601615488529,
-0.0070387013256549835,
0.030916007235646248,
-0.05911269783973694,
-0.09097126871347427,
0.04461568593978882,
0.11411638557910919,
0.0034090811386704445,
0.09482148289680481,
0.09621316194534302,
0.038220811635255814,
-0.00... | 0.047295 |
online with only the new root certificate, and connect to all existing systems. 5. Existing systems can now be migrated with a one-shot root switch: the new root can be added and the old root can be removed at the same time. Assuming the above step 3 can be achieved in a reasonable amount of time, this decreases the ti... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/rotation-primitives.mdx | main | vault | [
-0.0359877310693264,
-0.048184435814619064,
-0.019148925319314003,
-0.04179031401872635,
0.04378433898091316,
-0.09125245362520218,
-0.13887667655944824,
0.05706939101219177,
0.061293020844459534,
-0.03125763311982155,
0.0853915885090828,
0.08841104805469513,
0.028225205838680267,
0.016775... | -0.026124 |
# Enrollment over Secure Transport (EST) This document covers configuration and limitations of Vault's PKI Secrets Engine implementation of the [EST protocol](https://datatracker.ietf.org/doc/html/rfc7030) . ## What is Enrollment over Secure Transport (EST)? The EST protocol is an IETF standardized protocol, [RFC 7030]... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/est.mdx | main | vault | [
-0.0064587960951030254,
-0.0021247253753244877,
-0.028275934979319572,
-0.027287043631076813,
-0.012005808763206005,
-0.051891740411520004,
-0.023601392284035683,
0.025421790778636932,
0.022494718432426453,
-0.039697472006082535,
0.02533026970922947,
0.024695996195077896,
0.05932406708598137... | 0.070998 |
don't provide any sort of configuration for different path-prefixes, and will default to hitting the host on the path `https://:/.well-known/est/`. Some clients allow a single label, sometimes referred to as `additional path segment`, to accommodate different issuers. This label will be added to the path after the est ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/est.mdx | main | vault | [
0.06271745264530182,
0.00874583050608635,
-0.0309669878333807,
-0.04057034105062485,
-0.023745819926261902,
-0.06056869775056839,
-0.055627189576625824,
0.03243804723024368,
0.05082205682992935,
-0.04012397304177284,
0.024900853633880615,
0.02024918980896473,
0.056837018579244614,
0.118574... | -0.015734 |
# Troubleshoot PKI secrets engine and ACME Solve common problems related to ACME client integration with Vault PKI Secrets Engine's ACME server. ## Error: ACME feature requires local cluster 'path' field configuration to be set If ACME works on some nodes of a Vault Enterprise cluster but not on others, it likely means... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/troubleshooting-acme.mdx | main | vault | [
-0.026976389810442924,
-0.015063066966831684,
-0.06601618975400925,
0.049621906131505966,
0.005996484309434891,
-0.08787459880113602,
-0.058191489428281784,
-0.010068872943520546,
0.04288278520107269,
-0.027202604338526726,
0.03788323327898979,
-0.0024907412007451057,
0.0778769925236702,
0... | 0.041204 |
Vault server logs or attempting to fetch a certificate via an ACME client, an error like: > ACME validation failed for a465a798-4400-6c17-6735-e1b38c23de38-tls-alpn-01: ... indicates that the server was unable to validate this challenge accepted by the client. ### Cause Vault can not verify the server's identity throug... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/troubleshooting-acme.mdx | main | vault | [
-0.07862985879182816,
0.06363138556480408,
-0.023112360388040543,
0.006980064790695906,
-0.03525440767407417,
-0.0858430340886116,
-0.06409610062837601,
-0.030877988785505295,
0.04975709319114685,
-0.040283869951963425,
-0.025679171085357666,
-0.026966726407408714,
0.07152529805898666,
0.0... | -0.087252 |
# Set up and use the PKI secrets engine This document provides a brief overview of the setup and usage of the PKI Secrets Engine. ## Setup Most secrets engines must be configured in advance before they can perform their functions. These steps are usually completed by an operator or configuration management tool. 1. Ena... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/setup.mdx | main | vault | [
-0.003499748418107629,
0.025797102600336075,
-0.05395413562655449,
0.004169132560491562,
-0.06932947039604187,
-0.04923269525170326,
-0.08276256173849106,
0.020715156570076942,
0.030267035588622093,
-0.06576277315616608,
0.029975248500704765,
0.007455245591700077,
0.06615926325321198,
0.03... | -0.024104 |
# Configure a Simple Certificate Enrollment Protocol (SCEP) @include 'alerts/enterprise-only.mdx' SCEP is an IETF standardized protocol ([RFC 8894](https://datatracker.ietf.org/doc/html/rfc8894)) that allows clients to acquire client certificates and associated Certificate Authority (CA) certificates. You can configure... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/scep.mdx | main | vault | [
0.016982080414891243,
0.035843461751937866,
-0.1134229376912117,
-0.11340419948101044,
-0.0038155801594257355,
-0.03530062735080719,
0.02886856347322464,
0.005750723648816347,
0.032022640109062195,
-0.006140669342130423,
-0.013224933296442032,
-0.03732271119952202,
0.12468322366476059,
0.0... | 0.000551 |
then added to the mount's delegated auth accessors. ```shell-session $ vault secrets tune \ -delegated-auth-accessors="auth\_scep\_e2f4f6d5" \ -delegated-auth-accessors="auth\_cert\_4088ac2d" \ pki ``` ## Step 3: Configure your SCEP authentication mount The following example uses two different authentication methods: c... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/pki/scep.mdx | main | vault | [
0.043940361589193344,
0.057271573692560196,
-0.06965534389019012,
0.0033280737698078156,
0.040175534784793854,
0.0036987117491662502,
0.04220346733927727,
0.00902069266885519,
0.01565859280526638,
0.0599946528673172,
0.028989922255277634,
-0.04294397309422493,
0.1034262552857399,
0.1050343... | -0.034805 |
# GitHub actions Workflows in GitHub Actions can make use of secrets stored in Vault by using a [`vault-action`](https://github.com/marketplace/actions/hashicorp-vault) step. ## Example Here is an example `vault-action` step in a workflow: ```yaml jobs: build: # ... steps: # ... - name: Import Secrets uses: hashicorp/v... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/platform/github-actions.mdx | main | vault | [
-0.016923241317272186,
0.009192198514938354,
-0.08497297018766403,
0.0002229762467322871,
-0.014511334709823132,
-0.02370797097682953,
-0.038017068058252335,
0.005539325065910816,
0.08118478953838348,
-0.03800955042243004,
0.021168582141399384,
-0.01047029159963131,
0.050284579396247864,
0... | 0.01747 |
# Configure the Vault ServiceNow Credential Resolver ## MID server properties The following [properties] are supported by the Vault Credential Resolver: - `mid.external\_credentials.vault.address` `(string: "")` - Address of Vault Agent as resolveable by the MID server. For example, if Vault Agent is on the same server... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/platform/servicenow/configuration.mdx | main | vault | [
-0.03333665058016777,
0.06332524865865707,
-0.051249582320451736,
-0.06133868545293808,
-0.059944018721580505,
-0.07841293513774872,
-0.03492376208305359,
0.027442190796136856,
0.10767735540866852,
-0.033160772174596786,
-0.007852962240576744,
-0.027581188827753067,
0.11981869488954544,
0.... | -0.13059 |
a MID server and target to test your configuration. | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/platform/servicenow/configuration.mdx | main | vault | [
0.031061742454767227,
-0.027816923335194588,
-0.06197890639305115,
-0.038504768162965775,
-0.003720981301739812,
-0.09929107129573822,
-0.07233183830976486,
0.018488774076104164,
-0.03399889916181564,
0.019824108108878136,
0.012714684009552002,
0.02869257889688015,
0.027823418378829956,
-0... | 0.184989 |
# Vault Credential Resolver ServiceNow® MID servers can use the Vault Credential Resolver to consume secrets directly from Vault for the purpose of performing discovery. See [installation](/vault/docs/platform/servicenow/installation) and [configuration](/vault/docs/platform/servicenow/configuration) for help getting s... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/platform/servicenow/index.mdx | main | vault | [
-0.08828236907720566,
-0.030232353135943413,
-0.011950794607400894,
-0.07334941625595093,
-0.04699534550309181,
-0.05638828128576279,
0.009663444012403488,
0.024054553359746933,
0.11723929643630981,
-0.0003400463901925832,
-0.04022941738367081,
0.049892328679561615,
0.08863531053066254,
0.... | 0.044674 |
# Troubleshoot the Vault ServiceNow Credential Resolver ## Check the logs Check the [log files] inside `logs/` in the agent installation folder for logs and errors. The resolver logs a line for each credential ID that it successfully queries, and also logs the fields that the credentials were extracted from. If a parti... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/platform/servicenow/troubleshooting.mdx | main | vault | [
-0.021522890776395798,
0.021456029266119003,
-0.03256365284323692,
-0.05056613311171532,
-0.05868574231863022,
-0.04294741526246071,
-0.030028872191905975,
-0.0242602676153183,
0.08279713243246078,
0.00036103048478253186,
-0.035149432718753815,
-0.038559816777706146,
0.1194436252117157,
0.... | -0.139691 |
# Install Vault ServiceNow Credential Resolver ## Prerequisites \* ServiceNow version Quebec+ (untested on previous versions) \* MID server version Quebec+ (untested on previous versions) \* Discovery and external credential plugins activated on ServiceNow \* Working Vault deployment accessible from the MID server ## I... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/platform/servicenow/installation.mdx | main | vault | [
-0.006346379406750202,
0.02112690359354019,
-0.0887056291103363,
-0.057331282645463943,
-0.08662956953048706,
0.00045424254494719207,
0.0035321537870913744,
0.0181814506649971,
-0.0014069407479837537,
-0.03553945571184158,
-0.03156733140349388,
-0.03932385891675949,
0.11507852375507355,
0.... | -0.087011 |
# Configure the Vault EKM provider Configuration is stored in a `config.json` file under ProgramData in a path that mirrors the installation folder. This defaults to `C:\ProgramData\HashiCorp\Transit Vault EKM Provider\config.json`. -> \*\*Note:\*\* If the Vault EKM Provider has already been installed, Microsoft SQL Se... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/platform/mssql/configuration.mdx | main | vault | [
0.08283238857984543,
-0.044103965163230896,
-0.06426309794187546,
0.04491027072072029,
-0.05866466090083122,
-0.02679232321679592,
-0.035955868661403656,
-0.03548039123415947,
0.04525033012032509,
0.013401228934526443,
0.03794706612825394,
-0.037167739123106,
0.07878195494413376,
0.0312431... | 0.001418 |
# Vault EKM provider for SQL server Requires [Vault Enterprise](https://www.hashicorp.com/products/vault/pricing) with **Advanced Data Protection Key Management** module. Microsoft SQL Server supports [Transparent Data Encryption][tde] (TDE). The Database Encryption Keys (DEK) can be protected by asymmetric Key Encrypt... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/platform/mssql/index.mdx | main | vault | [
-0.011895164847373962,
-0.041344258934259415,
-0.037719059735536575,
-0.0011669318191707134,
-0.04171466454863548,
-0.024894677102565765,
0.0001848463580245152,
-0.01910378970205784,
0.057139355689287186,
0.022667689248919487,
0.03440609201788902,
0.001065581920556724,
0.0848943442106247,
... | 0.040797 |
# Rotate encryption keys with the Vault EKM provider Both the database encryption key and Vault Transit's asymmetric key can be rotated independently. ## Database encryption key (DEK) rotation To rotate the database encryption key, you can execute the [following SQL query](https://docs.microsoft.com/en-us/sql/t-sql/sta... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/platform/mssql/rotation.mdx | main | vault | [
0.011787833645939827,
0.012308131903409958,
-0.06616578996181488,
-0.0016711639473214746,
-0.1099119484424591,
0.02318357676267624,
0.013299643062055111,
-0.057387933135032654,
0.12155110388994217,
0.09052372723817825,
0.05607699602842331,
0.06377965211868286,
0.12336819618940353,
-0.03964... | -0.112758 |
# Upgrade the Vault EKM provider ~> \*\*Note:\*\* The upgrade process will put the database into maintenance mode and require a restart. It is highly recommended to test this procedure in a staging environment prior to running it on a production database. 1. Disable the Vault EKM Provider, and verify it is marked disab... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/platform/mssql/upgrading.mdx | main | vault | [
0.08527890592813492,
-0.0026300589088350534,
0.009409877471625805,
-0.02263486571609974,
-0.010264180600643158,
-0.05163705721497536,
-0.05210867524147034,
-0.0627896785736084,
0.01197311282157898,
0.01589953899383545,
0.0825917050242424,
-0.025723397731781006,
0.058451276272535324,
0.0126... | -0.02806 |
# Release notes Each version is available to download from the [releases](https://releases.hashicorp.com/vault-mssql-ekm-provider/) page. ## 0.3.1 (February 25th, 2026) FEATURES \* Added 1-hour caching for Vault license checks to reduce repeated license status API calls. \* The Vault API client now implements exponenti... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/platform/mssql/changelog.mdx | main | vault | [
-0.024511385709047318,
0.025173524394631386,
0.021098267287015915,
-0.019692620262503624,
-0.03284933790564537,
-0.07404143363237381,
-0.07551661133766174,
-0.049346715211868286,
0.060577332973480225,
0.02227611653506756,
0.06675313413143158,
0.09089300036430359,
0.06230447068810463,
-0.01... | 0.037523 |
# Troubleshoot the Vault EKM provider ## Check windows event logs Logs from the Vault EKM provider will appear in Windows Event Viewer under "Windows Logs" > "Application" with source "Transit Vault EKM Provider". ### Enable trace logging If the logs in the Event Viewer don't give enough information to help debug your ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/platform/mssql/troubleshooting.mdx | main | vault | [
0.06552820652723312,
-0.03156984969973564,
-0.031125299632549286,
0.04732023552060127,
-0.02681095339357853,
-0.043020859360694885,
-0.017772549763321877,
-0.07978986203670502,
0.09873893857002258,
0.026990115642547607,
0.030131740495562553,
-0.04675419628620148,
0.0823696032166481,
0.0497... | -0.076588 |
# Install the Vault EKM provider This guide assumes you are installing the Vault EKM Provider for the first time. For upgrade instructions, see [upgrading](/vault/docs/platform/mssql/upgrading). ## Prerequisites \* Vault Enterprise server 1.9+ with a license for the Advanced Data Protection Key Management module \* Mic... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/platform/mssql/installation.mdx | main | vault | [
0.04606377333402634,
-0.022335974499583244,
-0.1029367670416832,
-0.04427463188767433,
-0.059667132794857025,
0.0036084922030568123,
-0.02343253791332245,
0.0063517033122479916,
0.022157961502671242,
0.027946580201387405,
0.006567768752574921,
-0.002500802744179964,
0.08560359477996826,
-0... | 0.015915 |
'ekm-encryption-key'; ``` -> \*\*Note:\*\* This is the first step at which the EKM provider will communicate with Vault. If Vault is misconfigured, this step is likely to fail. See [troubleshooting](/vault/docs/platform/mssql/troubleshooting) for tips on specific error codes. The above steps use the latest version of t... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/platform/mssql/installation.mdx | main | vault | [
0.024980831891298294,
-0.035018112510442734,
-0.020196784287691116,
0.04195065796375275,
-0.09312909096479416,
0.007215661462396383,
-0.02763420343399048,
-0.02676982246339321,
0.04977203905582428,
0.04469679668545723,
0.03864775598049164,
-0.057843223214149475,
0.13161581754684448,
0.0074... | -0.062347 |
# Vault MCP server reference This page contains reference information about the Vault MCP server, including configuration options and tools. ## Available tools The Vault MCP server provides specialized tools that AI models can use to access and perform certain Vault operations. These tools work automatically when you a... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/mcp-server/reference.mdx | main | vault | [
-0.02919689193367958,
-0.005404445342719555,
-0.06377499550580978,
0.008574286475777626,
-0.02196202054619789,
-0.031695712357759476,
-0.01842370256781578,
-0.0037098361644893885,
-0.006674621254205704,
-0.014935530722141266,
0.047839634120464325,
-0.005785212852060795,
0.08534514904022217,
... | 0.065924 |
configuration can be provided through multiple methods (\*\*in order of precedence\*\*): - HTTP Query: `VAULT\_ADDR` - HTTP Headers: `VAULT\_ADDR`, `X-Vault-Token`, and `X-Vault-Namespace` - Environment Variables: Standard `VAULT\_ADDR`, `VAULT\_TOKEN`, and `VAULT\_NAMESPACE env vars` ## Environment variables You can s... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/mcp-server/reference.mdx | main | vault | [
0.03760732710361481,
0.032016001641750336,
-0.11261630803346634,
-0.02734212391078472,
-0.06036493554711342,
-0.09783916920423508,
-0.0663423091173172,
0.004758614581078291,
0.016092238947749138,
-0.009679804556071758,
0.022493679076433182,
-0.05067646875977516,
0.06183677166700363,
0.0203... | -0.115711 |
# Vault MCP server The Vault MCP Server is a Model Context Protocol (MCP) server implementation that provides integration with HashiCorp Vault for managing secrets and mounts. This server uses both `stdio` and `StreamableHTTP` transports for MCP communication, making it compatible with Claude for Desktop and other MCP ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/mcp-server/overview.mdx | main | vault | [
-0.026953622698783875,
-0.033236559480428696,
-0.016525449231266975,
-0.10105754435062408,
0.02594779245555401,
-0.03687380999326706,
-0.02238023839890957,
0.04652145504951477,
0.07102395594120026,
-0.025923212990164757,
-0.00013576107448898256,
0.05350251495838165,
0.09406105428934097,
-0... | 0.108145 |
# Deploy the Vault MCP server The Vault Model Context Protocol (MCP) server enables AI models to interact with Vault and perform actions using up-to-date APIs. This page explains how to install, configure, and integrate the MCP server with your AI client. ## Overview The Vault MCP server is a specialized service that p... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/mcp-server/deploy.mdx | main | vault | [
0.0381542406976223,
-0.006350663956254721,
-0.005821100436151028,
-0.06694566458463669,
-0.019811291247606277,
-0.041292186826467514,
-0.09190881997346878,
0.040547218173742294,
-0.009270458482205868,
-0.015331017784774303,
-0.01595926471054554,
0.002339980797842145,
0.05522271618247032,
0... | 0.066575 |
an `mcp.json` file with the following configuration in your workspace's `.vscode` directory: ```json { "servers": { "vault": { "command": "docker", "args": [ "run", "-i", "--rm", "-e", "<>", "-e", "<>", "-e", "<>", "hashicorp/vault-mcp-server" ], "type": "stdio" } } } ``` 1. Verify the installation by opening the chat ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/mcp-server/deploy.mdx | main | vault | [
0.023484034463763237,
-0.024431655183434486,
-0.046556416898965836,
-0.019557099789381027,
-0.00818284135311842,
-0.06989412009716034,
-0.0870797410607338,
-0.0070180948823690414,
0.02293139137327671,
0.0005799352657049894,
0.03015754371881485,
-0.04169517382979393,
-0.04650239273905754,
0... | 0.050218 |
steps - Begin prompting your AI model about Vault operations. Refer to [Prompt an AI model](/vault/docs/mcp-server/prompt-model) for guidance on effective prompting techniques. - Ask for help with specific Vault operations and workflows. - Explore advanced configuration options for your specific deployment needs. | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/mcp-server/deploy.mdx | main | vault | [
0.07472342997789383,
-0.03950585052371025,
0.007942592725157738,
-0.039392173290252686,
0.0008940303232520819,
-0.05075890198349953,
-0.045807965099811554,
0.01708470843732357,
-0.023716803640127182,
-0.022536102682352066,
-0.004483058117330074,
-0.01589486189186573,
0.08352749049663544,
0... | 0.063907 |
# Prompt a model connected to the Vault MCP server This topic provides example prompts for helping you manage HashiCorp Vault after installing the Vault model context protocol (MCP) server. Refer to [Deploy the Vault MCP server](/vault/docs/mcp-server/deploy) for instructions on how to deploy the server. @include 'aler... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/mcp-server/prompt-model.mdx | main | vault | [
0.06840197741985321,
-0.02083565853536129,
-0.010938302613794804,
-0.07817883044481277,
-0.010733273811638355,
-0.029631871730089188,
-0.07437121868133545,
0.03903338313102722,
0.007316824980080128,
-0.02217959053814411,
0.018745681270956993,
0.031075241044163704,
0.10009294003248215,
0.00... | 0.004767 |
PKI secrets engine 2. \*\*Create root issuer\*\*: Generates the root certificate authority 3. \*\*Create PKI role\*\*: Configures certificate issuance policies 4. \*\*Issue certificate\*\*: Generates a certificate for validation #### PKI API sequence ```json { "path": "pki\_root", "description": "Root CA for example.co... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/mcp-server/prompt-model.mdx | main | vault | [
-0.07567993551492691,
0.012435960583388805,
-0.007626918610185385,
-0.026917608454823494,
-0.03375864773988724,
-0.11745473742485046,
-0.08282152563333511,
0.03772761672735214,
0.023824775591492653,
-0.021571656689047813,
0.029756668955087662,
-0.06698303669691086,
0.06180061027407646,
0.1... | -0.001628 |
Certificate Chain -----BEGIN CERTIFICATE----- [Intermediate CA certificate] -----END CERTIFICATE----- ## Installation Instructions 1. Save certificate to: `/etc/ssl/certs/api.internal.example.com.crt` 2. Save private key to: `/etc/ssl/private/api.internal.example.com.key` 3. Set secure permissions: `chmod 600 /etc/ssl/... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/mcp-server/prompt-model.mdx | main | vault | [
-0.079156294465065,
0.07897951453924179,
-0.006283728405833244,
-0.01967034861445427,
-0.007389738690108061,
-0.04539485275745392,
-0.06881491094827652,
0.002387483837082982,
-0.007204161025583744,
-0.022735796868801117,
0.05947092920541763,
-0.06789790093898773,
0.11506304889917374,
0.069... | -0.03533 |
# Security model for Vault MCP server ## Purpose of this document This document explains the security model for the Vault Model Context Protocol (MCP) server when operating the server locally using the STDIO or streamable HTTP transport. Understanding this model helps you safely integrate local AI agents with Vault too... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/mcp-server/security-model.mdx | main | vault | [
-0.03109612688422203,
-0.0022400585003197193,
-0.016378846019506454,
-0.05957724526524544,
0.01598266325891018,
-0.059256359934806824,
0.012661988846957684,
0.02759423479437828,
0.05617791414260864,
-0.019462235271930695,
-0.024993855506181717,
0.0009258512291125953,
0.11547058820724487,
-... | 0.190052 |
part of the threat model for the Vault MCP Server: ### Foundational model Concerns related to the underlying AI models, training data, and inherent vulnerabilities. ## Recommendations for securely using the Vault MCP server ### Ensuring local-only server access We recommend running the MCP Server locally (127.0.0.1) th... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/mcp-server/security-model.mdx | main | vault | [
-0.01651202328503132,
0.012615728192031384,
-0.05013148486614227,
-0.08044684678316116,
0.002792312763631344,
-0.03728293627500534,
-0.09410502761602402,
0.03213612735271454,
-0.021511616185307503,
-0.008870051242411137,
0.03113964945077896,
0.012415374629199505,
0.014917436055839062,
0.00... | 0.033412 |
# LTS Vault change tracker [Long-term support](/vault/docs/enterprise/) offers extended maintenance through minor releases for select, major Vault Enterprise versions. Current LTS release | Extended maintenance release ------------------- | ---------------------------- 1.19.x | 1.16.x Before you perform a direct LTS up... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/updates/lts-tracker.mdx | main | vault | [
0.010544896125793457,
0.01975603774189949,
0.053949885070323944,
-0.07343324273824692,
0.06818732619285583,
-0.011578270234167576,
-0.10191642493009567,
0.0013289308408275247,
-0.08092016726732254,
-0.04377762973308563,
0.07540350407361984,
0.06008429452776909,
-0.0055976128205657005,
0.05... | -0.07536 |
# Important changes \*\*Last updated\*\*: 2025-10-04 Always review important or breaking changes and remediation recommendations before upgrading Vault. ## Breaking changes @include '../../../global/partials/important-changes/breaking-changes/client-count-timestamp.mdx' @include '../../../global/partials/important-chan... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/updates/important-changes.mdx | main | vault | [
-0.009167501702904701,
0.003119655651971698,
-0.0002294131845701486,
-0.026149168610572815,
0.0019827827345579863,
-0.016594531014561653,
-0.10284315049648285,
-0.059372760355472565,
-0.013202421367168427,
-0.00493600545451045,
0.05276221036911011,
0.06662040948867798,
0.04043928161263466,
... | -0.080514 |
# Vault release notes Release | RC date | GA date ------- | ---------- | ---------- 1.21.x | 2025-10-09 | 2025-10-22 @include 'release-notes/intro.mdx' @include 'tips/change-tracker.mdx' ## Executive summary Vault Enterprise 1.21 minimizes operational burden, improves pricing visibility, and provides increased pricing ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/updates/release-notes.mdx | main | vault | [
-0.06657136976718903,
0.020319970324635506,
-0.008399507962167263,
-0.03257744014263153,
0.04956083372235298,
0.0131660345941782,
-0.012209315784275532,
-0.02225690893828869,
-0.037836719304323196,
0.05739831551909447,
0.021785659715533257,
0.028048742562532425,
0.10573164373636246,
0.0087... | 0.073914 |
| RACF passphrase support in the LDAP plugin | Use RACF passphrases (up to 100 characters) with the LDAP secrets engine plugin. | Supports longer, more secure RACF passphrases and helps you keep up with changing security policy requirements. | | Eventing in the LDAP Secrets Engine | The LDAP secrets engine now [emits e... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/updates/release-notes.mdx | main | vault | [
-0.03631875291466713,
-0.07648555934429169,
-0.12372948974370956,
-0.02249852754175663,
0.052670419216156006,
-0.001229413435794413,
-0.04384184256196022,
0.07308463007211685,
-0.013202589005231857,
-0.022010881453752518,
0.04760999605059624,
0.052050553262233734,
0.03240615874528885,
-0.0... | 0.054829 |
# Vault change tracker Summary tables of important changes that may affect your ability to upgrade Vault. ## Changes for 1.21.x @include '../../../global/partials/important-changes/summary-tables/1\_21.mdx' ## Changes for 1.20.x @include '../../../global/partials/important-changes/summary-tables/1\_20.mdx' ## Changes f... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/updates/change-tracker.mdx | main | vault | [
0.05065648630261421,
0.017696615308523178,
0.018759265542030334,
-0.0664190724492073,
0.05022253468632698,
-0.05464412271976471,
-0.05507408455014229,
-0.019637111574411392,
-0.026340393349528313,
0.048732925206422806,
0.016881803050637245,
-0.02170669659972191,
0.04434196278452873,
0.0314... | -0.089264 |
# Deprecation notices Vault implements a multi-phased approach to deprecations to provide users with advanced warning, minimize business disruptions, and allow for the safe handling of data affected by a feature removal. If you have questions or concerns about a deprecated feature, please create a topic on the [Vault c... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/updates/deprecation.mdx | main | vault | [
0.002268655924126506,
0.06552760303020477,
0.054932061582803726,
-0.0350508987903595,
0.043594490736722946,
-0.05156702920794487,
-0.0937863141298294,
0.021573398262262344,
-0.043882157653570175,
-0.0417870432138443,
0.062051594257354736,
0.06023884192109108,
0.01882113702595234,
-0.004894... | 0.00535 |
# Manually install a Vault binary Install Vault using a compiled binary. ## Before you start - \*\*You must have a valid Vault binary\*\*. You can [download and unzip a precompiled binary](/vault/install) or [build a local instance of Vault from source code](/vault/docs/install/build-from-code). ## Step 1: Configure th... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/get-vault/install-binary.mdx | main | vault | [
0.08879373967647552,
0.005227577406913042,
-0.07669514417648315,
-0.044360704720020294,
-0.04820369556546211,
-0.038118552416563034,
-0.060759179294109344,
0.06648177653551102,
-0.03737027198076248,
-0.01305848453193903,
0.0040939971804618835,
-0.05880427360534668,
0.04916400834918022,
0.0... | -0.144242 |
Create a basic Vault configuration file for testing and development. The sample configuration below disables TLS for simplicity and is not appropriate for production use. Refer to the [configuration documentation](/vault/docs/configuration) for a full list of supported parameters. 1. Create a file called `vault.hcl` un... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/get-vault/install-binary.mdx | main | vault | [
0.03730237856507301,
0.0938229039311409,
-0.09196668863296509,
-0.0022031289990991354,
-0.023633776232600212,
-0.08190980553627014,
-0.0697333812713623,
-0.06413775682449341,
0.027111997827887535,
-0.0075378124602139,
-0.0096640195697546,
-0.04354342073202133,
0.07748489826917648,
0.047235... | -0.089955 |
# Get Vault You can get Vault through a variety of package managers or from HashiCorp directly. ## Vault version syntax @include 'version-syntax.mdx' ## Get notified of new releases You can subscribe to specific tags in the [Vault discussion forum](https://discuss.hashicorp.com/) to receive alerts about recent changes.... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/get-vault/index.mdx | main | vault | [
0.09511306881904602,
0.0009827001485973597,
-0.02811596542596817,
-0.07463893294334412,
0.09231767058372498,
-0.0655626729130745,
-0.04020985960960388,
0.016109418123960495,
0.00030836276710033417,
-0.028987204656004906,
0.008602841757237911,
-0.020499903708696365,
0.008139909245073795,
-0... | 0.015475 |
# Build Vault from code Clone the official Vault repo and build a Vault binary from source code for your system. - You have [Go](https://golang.org) installed and the `GOPATH` environment variable configured. - You have [`git`](https://www.git-scm.com/) installed. 1. Create a `hashicorp` source directory under your `GO... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/get-vault/build-from-code.mdx | main | vault | [
0.06935989856719971,
0.011348539032042027,
-0.09189137071371078,
-0.05626693367958069,
-0.041936568915843964,
-0.032306596636772156,
-0.006683287676423788,
0.0848095566034317,
-0.007051215507090092,
-0.014644131995737553,
0.0640515685081482,
-0.038346704095602036,
0.02549312449991703,
0.05... | -0.039975 |
# Token authentication The `token` auth method is built-in and is at the core of client authentication. Other auth methods may be used to authenticate a client, but they eventually result in the generation of a client token managed by the `token` backend. Every token has a number of properties: - ID - The primary ID of... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/internals/token.mdx | main | vault | [
-0.054391197860240936,
0.023628169670701027,
-0.04396645724773407,
0.034870248287916183,
0.04071293771266937,
-0.059570446610450745,
0.055537186563014984,
-0.003217629622668028,
0.16360807418823242,
-0.007292696740478277,
-0.008200912736356258,
0.08093387633562088,
0.091519795358181,
-0.04... | 0.192795 |
# 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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.