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 |
|---|---|---|---|---|---|
# Use Kubernetes persistent cache When `kubernetes` is configured for the persistent cache type, Vault Agent will optimize the persistent cache specifically for Kubernetes. This type of persistent cache requires a Kubernetes service account token. The service account token is used during encryption and decryption of th... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/agent/caching/persistent-caches/kubernetes.mdx | main | vault | [
0.04010005295276642,
0.04471809044480324,
-0.03208525851368904,
-0.025655250996351242,
-0.04305475950241089,
-0.020216118544340134,
-0.014286729507148266,
-0.011099009774625301,
0.08463118225336075,
0.005807540379464626,
0.01711215451359749,
0.04166879132390022,
-0.01964551955461502,
0.010... | 0.065083 |
# Regenerate a Vault root token Your Vault root token is a special token that gives you access to \*\*all\*\* Vault operations. Best practice is to enable an appropriate authentication method for Vault admins once the server is running and revoke the root token. For emergency situations where your require a root token,... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/troubleshoot/generate-root-token.mdx | main | vault | [
-0.011468365788459778,
-0.01993357390165329,
-0.04002126678824425,
-0.016185231506824493,
-0.03742147609591484,
-0.06292125582695007,
-0.043340448290109634,
0.06814698874950409,
0.01792607083916664,
-0.020616551861166954,
0.007009407505393028,
-0.009028959088027477,
0.07208789885044098,
-0... | 0.002192 |
# Tune the lease time-to-live (TTL) The benefit of using Vault's dynamic secrets engines and auth methods is the ability to control how long the Vault-managed credentials (leases) remain valid. Often times, you generate short-lived credentials or tokens to reduce the risk of unauthorized attacks caused by leaked creden... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/troubleshoot/tune-lease-ttl.mdx | main | vault | [
0.03500796854496002,
0.04814693331718445,
-0.04491954296827316,
0.015980521216988564,
-0.029888024553656578,
-0.04476393759250641,
-0.031691763550043106,
0.028794266283512115,
0.03848704323172569,
-0.001832581008784473,
0.013220954686403275,
0.005577738396823406,
0.08934585005044937,
0.034... | -0.058107 |
lists all available parameters that you can tune. ```shell-session $ vault secrets tune -h ``` @include 'alerts/secret-engine-tune-gui-support.mdx' @include 'plugins/tune-keymgmt-steps.mdx' When you introduce Vault into your existing system, the existing applications may not be able to handle short-lived leases. You ca... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/troubleshoot/tune-lease-ttl.mdx | main | vault | [
0.05779628828167915,
0.03497792407870293,
-0.06042129546403885,
-0.06417300552129745,
-0.04417847841978073,
-0.05625031888484955,
-0.06773089617490768,
-0.012894026935100555,
-0.005129524972289801,
-0.055976904928684235,
-0.0014181770384311676,
0.054209332913160324,
0.11307702958583832,
0.... | -0.077338 |
# Troubleshoot lease problems Explanations, workarounds, and solutions for common lease problems in Vault. ## `429 - Too Many Requests` ### Problem Vault returns a `429 - Too Many Requests` response when users try to authenticate. For example: ```text Error making API request. URL: PUT https://127.0.0.1:61555/v1/auth/u... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/troubleshoot/lease-issues.mdx | main | vault | [
-0.01497909240424633,
0.06129944324493408,
-0.03034156933426857,
-0.016634220257401466,
-0.03417292609810829,
-0.0742446780204773,
-0.04689813032746315,
-0.019729528576135635,
0.04318201541900635,
0.03232315555214882,
-0.0027051460929214954,
0.006247290875762701,
0.08967059850692749,
0.084... | -0.041714 |
# Vault Enterprise license keys @include 'alerts/enterprise-only.mdx' Vault Enterprise 1.8 introduced EULA enhancements and license keys that control the availability of features. You must have a Vault Enterprise binary (evaluation or non-evaluation) downloaded from [releases.hashicorp.com](https://releases.hashicorp.c... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/license/index.mdx | main | vault | [
0.059896159917116165,
0.037787195295095444,
-0.025553030893206596,
-0.11577055603265762,
-0.012906745076179504,
0.020446091890335083,
-0.04807686060667038,
-0.012227898463606834,
-0.0010949017014354467,
-0.058451708406209946,
0.024734213948249817,
0.01727933995425701,
0.05269596725702286,
... | -0.006792 |
Enterprise License](/vault/tutorials/enterprise/hashicorp-enterprise-license) - guided walkthrough for loading a Vault license. | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/license/index.mdx | main | vault | [
0.02126486226916313,
0.05425534024834633,
-0.0853019431233406,
-0.09965717792510986,
0.011781665496528149,
-0.02501463145017624,
-0.010027337819337845,
0.023796703666448593,
-0.017714355140924454,
-0.043955907225608826,
0.028827069327235222,
0.0790267065167427,
-0.03471725434064865,
-0.025... | 0.179339 |
# Anonymous product usage reporting @include 'alerts/enterprise-only.mdx' HashiCorp collects usage data about how Vault clusters are being used. Product usage data is not used for billing or and is numerical only, and no sensitive information of any nature is being collected. The data is collected as part of the [licen... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/license/product-usage-reporting.mdx | main | vault | [
0.07405275851488113,
0.045680079609155655,
-0.09714638441801071,
-0.04921950772404671,
0.06428317725658417,
-0.02169186621904373,
0.07810527831315994,
0.013232567347586155,
0.042913008481264114,
-0.0679006427526474,
0.024548353627324104,
0.019064711406826973,
0.04724251478910446,
-0.029335... | 0.040349 |
within Vault. | | `vault.quotas.ratelimit.entity\_then\_ip\_with\_secondary\_rate.count` | Total number of rate limit quotas using "entity\_then\_ip" group\_by mode with secondary rate within Vault. | | `vault.quotas.ratelimit.entity\_then\_none.count` | Total number of rate limit quotas using "entity\_then\_none" grou... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/license/product-usage-reporting.mdx | main | vault | [
0.0324767641723156,
0.029161687940359116,
-0.06630802899599075,
0.0028198552317917347,
-0.037941526621580124,
-0.027953792363405228,
0.01406498346477747,
0.005551359616219997,
0.07581688463687897,
0.03209413215517998,
0.07202094793319702,
-0.09563430398702621,
0.09910338371992111,
0.020819... | -0.04408 |
| `vault.db.mongodb.plugin.count` | The total number of MongoDB database plugin connections in Vault. | | `vault.db.mongodbatlas.plugin.count` | The total number of MongoDB Atlas database plugin connections in Vault. | | `vault.db.mssql.plugin.count` | The total number of MSSQL database plugin connections in Vault. | |... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/license/product-usage-reporting.mdx | main | vault | [
0.0598592646420002,
-0.04167215898633003,
-0.08635858446359634,
0.04475846141576767,
-0.05454788729548454,
0.009064353071153164,
0.016117779538035393,
0.015038195066154003,
0.048931851983070374,
0.0026153838261961937,
-0.01073539163917303,
-0.005257982760667801,
0.05055045336484909,
-0.011... | -0.034594 |
number of Transform secret engines in Vault. | | `vault.secret.engine.transit.count` | The total number of Transit secret engines in Vault. | | `vault.secret.engine.database.count` | The total number of Database secret engines in Vault. | | `vault.secret.engine.plugin.count` | The total number of custom plugin secret e... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/license/product-usage-reporting.mdx | main | vault | [
0.005898528266698122,
-0.0467134527862072,
-0.05235111713409424,
0.03957400098443031,
-0.004843841772526503,
0.04390890896320343,
-0.04371819272637367,
-0.041284579783678055,
0.047759007662534714,
0.0005207853391766548,
0.012632154859602451,
-0.04010360687971115,
0.09243421256542206,
-0.05... | -0.043422 |
across all namespaces in Vault. | | `vault.policies.rgp.count` | The total number of Replication Governance Policies (RGP) across all namespaces in Vault. | | `vault.policies.acl.count` | The total number of Access Control List (ACL) policies across all namespaces in Vault. | | `vault.policies.acl.control\_group.count`... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/license/product-usage-reporting.mdx | main | vault | [
0.007793909404426813,
-0.05800650641322136,
-0.07000075280666351,
-0.011077978648245335,
0.05916077643632889,
-0.025925111025571823,
0.0284119825810194,
-0.0635700598359108,
0.025304453447461128,
0.04165485501289368,
0.04633255675435066,
0.007591589353978634,
0.08866962045431137,
-0.002003... | 0.036303 |
# Change your Vault license @include 'alerts/enterprise-only.mdx' - You have an available Vault Enterprise license key. - You have admin privileges for your Vault deployment environment. Vault Enterprise automatically looks for valid license information in the following locations: Priority | Location | Variable / Field... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/license/change-license.mdx | main | vault | [
0.09918749332427979,
0.044275108724832535,
-0.035704825073480606,
-0.10888007283210754,
-0.002321443287655711,
-0.0012870541540905833,
-0.024956708773970604,
-0.006077752914279699,
0.029507774859666824,
-0.02418743446469307,
-0.027106625959277153,
-0.010126794688403606,
0.06160084530711174,
... | -0.126478 |
# Autoload an enterprise license @include 'alerts/enterprise-only.mdx' - You have an available Vault Enterprise license key. - You have admin privileges for your Vault deployment environment. Vault Enterprise automatically looks for valid license information in the following locations: Priority | Location | Variable / ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/license/autoloading.mdx | main | vault | [
0.08694897592067719,
0.04387816786766052,
-0.06611515581607819,
-0.10339834541082382,
0.007685402873903513,
-0.0014401092194020748,
-0.015870582312345505,
0.007124023512005806,
0.022972391918301582,
-0.03754262253642082,
-0.016809914261102676,
-0.016795819625258446,
0.05231586471199989,
0.... | -0.086344 |
# Automated license utilization reporting @include 'alerts/enterprise-only.mdx' Automated license utilization reporting sends license utilization data to HashiCorp without requiring you to manually collect and report them. Automated reporting shares the minimum data required to validate license utilization as defined i... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/license/utilization/auto-reporting.mdx | main | vault | [
0.03800734505057335,
0.03497815877199173,
-0.0842292308807373,
-0.062483519315719604,
-0.008643638342618942,
-0.06997055560350418,
-0.03247639164328575,
0.016085229814052582,
0.07656676322221756,
-0.037295110523700714,
-0.005444174166768789,
0.0386643260717392,
0.06059284508228302,
0.02201... | 0.058931 |
that you review the [example payloads](#example-payloads) before opting out. If you have concerns with any of the automatically-reported data please bring them to your account manager. You have two options to opt out of automated reporting: - HCL configuration (recommended) - Environment variable (requires restart) ###... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/license/utilization/auto-reporting.mdx | main | vault | [
0.023978400975465775,
0.06487074494361877,
-0.07599348574876785,
0.029443243518471718,
0.005890238098800182,
0.056029826402664185,
-0.04242530092597008,
-0.019774021580815315,
-0.014663093723356724,
-0.03549791872501373,
0.011966608464717865,
-0.024592382833361626,
0.11674200743436813,
-0.... | -0.024631 |
`development\_cluster` value based on their HCL configuration. All clusters in a replication group must have the same `development\_cluster` setting in their HCL configuration. In the event of a promotion or failover, the new primary cluster's HCL configuration will determine the value reported by all clusters in the r... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/license/utilization/auto-reporting.mdx | main | vault | [
-0.01552404835820198,
-0.006456335540860891,
-0.039086975157260895,
0.054114606231451035,
0.04897134378552437,
-0.028161128982901573,
-0.07322783023118973,
-0.07590317726135254,
0.025782383978366852,
-0.03290770947933197,
0.02608327940106392,
-0.03861301392316818,
0.07699809968471527,
-0.0... | 0.127896 |
"value": 0, "mode": "write" }, "certcount.current\_month\_estimate": { "key": "certcount.current\_month\_estimate", "value": 0, "mode": "write" }, "certcount.previous\_month\_complete": { "key": "certcount.previous\_month\_complete", "value": 0, "mode": "write" } }, "product\_version": "1.21.0+ent", "license\_id": "7d6... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/license/utilization/auto-reporting.mdx | main | vault | [
0.038841698318719864,
0.08881783485412598,
-0.0759081318974495,
0.013609659858047962,
-0.023794539272785187,
-0.016516361385583878,
0.01002970989793539,
0.010864430107176304,
0.04019571840763092,
0.04382193833589554,
0.06026393175125122,
-0.11299038678407669,
0.027667468413710594,
-0.03478... | 0.051817 |
# Manual license utilization reporting @include 'alerts/enterprise-only.mdx' Manual license utilization reporting allows you to export, review, and send license utilization data to HashiCorp via the CLI or [HCP web portal](https://portal.cloud.hashicorp.com/). Use these reports to understand how much more you can deplo... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/license/utilization/manual-reporting.mdx | main | vault | [
0.05072292312979698,
0.03503309190273285,
-0.07998435199260712,
-0.05426561459898949,
0.024235175922513008,
0.010183250531554222,
0.02384844236075878,
0.029748177155852318,
-0.011583319865167141,
-0.0024647838436067104,
-0.016745736822485924,
0.012386079877614975,
0.016804920509457588,
-0.... | 0.060885 |
error persists, please contact your account representative. ## Enable manual reporting Upgrade to a release that supports manual license utilization reporting. These releases include: - Vault Enterprise 1.16.0 and later - Vault Enterprise 1.15.6 and later - Vault Enterprise 1.14.10 and later ## Configuration Administra... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/license/utilization/manual-reporting.mdx | main | vault | [
-0.005302814766764641,
0.06863811612129211,
-0.08676046133041382,
-0.021142080426216125,
-0.03277947008609772,
0.0018134242855012417,
-0.03444593399763107,
0.029077503830194473,
0.04483480751514435,
0.014177477918565273,
0.0441703200340271,
0.0013876606244593859,
0.053468260914087296,
0.01... | -0.05182 |
# Automatically upgrade Vault clusters @include 'alerts/enterprise-only.mdx' Operators running Vault Enterprise with integrated storage can use automated upgrades to upgrade the Vault version currently running in a cluster automatically. There are a few different ways to make this upgrade happen, and control which vers... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/automated-upgrades.mdx | main | vault | [
0.08784198760986328,
0.014714880846440792,
-0.007650439161807299,
-0.06029581278562546,
0.05243462324142456,
-0.07008664309978485,
-0.020315079018473625,
-0.029898416250944138,
0.008965223096311092,
-0.010044117458164692,
0.03220615163445473,
0.006648389156907797,
0.08471985906362534,
-0.0... | 0.022596 |
version is less than current version | | 1.11.0+release.1 | 1.11.0+release.2 | Yes | No | `release.1` and `release.2` are build metadata and ignored when comparing versions | | 1.11.0-release.1+123 | 1.11.0-release.1+456 | Yes | No | Versions are equal, build metadata is ignored. | | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/automated-upgrades.mdx | main | vault | [
0.029080821201205254,
0.021647391840815544,
0.048924025148153305,
-0.10550369322299957,
0.06503395736217499,
-0.07514230161905289,
-0.05021680146455765,
0.003445057664066553,
0.011425627395510674,
-0.021599609404802322,
0.056114260107278824,
-0.00697201257571578,
-0.019841820001602173,
-0.... | -0.054734 |
# Enforce lease count quotas @include 'alerts/enterprise-only.mdx' Vault features an extension to resource quotas that allows operators to enforce limits on how many leases are created. For a given lease count quota, if the number of leases in the cluster hits the configured limit, `max\_leases`, additional lease creat... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/lease-count-quotas.mdx | main | vault | [
0.01420518383383751,
-0.008806685917079449,
-0.05879763886332512,
-0.01857548952102661,
-0.00975084863603115,
-0.01095545757561922,
-0.0008593285456299782,
-0.022788193076848984,
0.06194000318646431,
-0.000780576781835407,
0.0019195324275642633,
0.029612381011247635,
0.12988898158073425,
0... | 0.080172 |
mount, path, or role) as described in the [Lease count quota precedence](#lease-count-quota-precedence) section above. ## Quota inspection Vault also allows the inspection of the state of lease count quotas in a Vault cluster through various [metrics](/vault/docs/internals/telemetry/metrics/core-system#quota-metrics) a... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/lease-count-quotas.mdx | main | vault | [
0.027885228395462036,
0.025985227897763252,
-0.04725039005279541,
-0.00860007107257843,
-0.033911414444446564,
-0.07672236859798431,
-0.05363990366458893,
0.02010071463882923,
0.05557376518845558,
0.007206230890005827,
0.005008315667510033,
-0.018322313204407692,
0.08838102221488953,
0.050... | 0.018435 |
# Augment entropy with external sampling @include 'alerts/enterprise-only.mdx' Entropy augmentation **is not** available with "FIPS 140-3 Inside" variants of Vault. Vault Enterprise features a mechanism to sample entropy (or randomness for cryptographic operations) from external cryptographic modules via the [seals](/v... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/entropy-augmentation.mdx | main | vault | [
-0.02134876325726509,
0.023177238181233406,
-0.04753263667225838,
-0.055016472935676575,
0.009419072419404984,
-0.07497206330299377,
0.04338659346103668,
-0.004254198167473078,
0.08986572921276093,
-0.016167493537068367,
-0.013638434931635857,
0.013883804902434349,
0.07390265166759491,
-0.... | 0.055833 |
/vault/docs/configuration | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/entropy-augmentation.mdx | main | vault | [
0.045605726540088654,
0.04219050705432892,
-0.08414597064256668,
-0.030480874702334404,
-0.00961515586823225,
-0.06305307149887085,
-0.05262768268585205,
0.05207470431923866,
0.01876785233616829,
-0.039282456040382385,
0.016568565741181374,
0.08456408977508545,
0.0686936229467392,
0.004701... | -0.011338 |
# Design your Vault Enterprise cluster @include 'alerts/enterprise-only.mdx' If you want to implement a robust Vault cluster, you need to understand how Vault manages clusters, storage, and replication. ## Before you start - \*\*Complete the [HashiCorp Enterprise Academy Onboarding](https://onboarding.hashicorp.com/tra... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/cluster-design.mdx | main | vault | [
0.05959603562951088,
0.00047862358042038977,
-0.07573851943016052,
-0.047437649220228195,
-0.017114125192165375,
-0.06252643465995789,
-0.06515362113714218,
0.02941449172794819,
-0.021972522139549255,
-0.0191881712526083,
-0.04343461990356445,
0.036200616508722305,
0.10595956444740295,
-0.... | 0.080074 |
# Long-term support for Vault @include 'alerts/enterprise-only.mdx' Long-term support (LTS) eases upgrade requirements for installations that cannot upgrade frequently, quickly, or easily. ## LTS summary | Question | Answer | | --- | --- | | [Who should consider long-term support?](#who) | Enterprise customers using Va... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/lts.mdx | main | vault | [
0.053620509803295135,
0.012424333952367306,
0.03634996339678764,
-0.10217934846878052,
0.04976760968565941,
-0.0422796793282032,
-0.08496669679880142,
0.0250143613666296,
-0.05256393179297447,
-0.07534661889076233,
0.011753838509321213,
0.0697019100189209,
0.00613320991396904,
-0.012010502... | 0.040901 |
there a risk to updating to a non-LTS Vault Enterprise version? Long-term support is intended for Enterprise customers who cannot upgrade frequently enough to stay within the standard maintenance timeline of one year. The goal is to establish a predictable upgrade path with a longer timeline rather than extending the l... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/lts.mdx | main | vault | [
0.032530635595321655,
-0.009716185741126537,
0.04859258234500885,
-0.09673163294792175,
0.012542509473860264,
-0.04213240370154381,
-0.11912953108549118,
-0.006093292497098446,
-0.003603811375796795,
-0.04809636250138283,
0.020250003784894943,
0.06958375871181488,
-0.012105820700526237,
-0... | -0.057154 |
# Use control groups for authorization @include 'alerts/enterprise-and-hcp.mdx' Vault Enterprise has support for Control Group Authorization. Control Groups add additional authorization factors to be required before satisfying a request. When a Control Group is required for a request, a limited duration response wrappi... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/control-groups.mdx | main | vault | [
-0.003211833303794265,
0.07404910027980804,
-0.0514213964343071,
-0.003444385016337037,
-0.003692236263304949,
-0.0407656654715538,
0.06499169766902924,
-0.028906306251883507,
-0.036230605095624924,
-0.039893753826618195,
-0.02427820861339569,
-0.023076392710208893,
0.10352529585361481,
0.... | 0.037216 |
executing any operation against `kv/\*`. In addition, by virtue of the `controlled\_capabilities` field in the first path stanza, `delete`,`list`, and `sudo` operations will require an additional approval from the "admin" group. ``` path "kv/\*" { capabilities = ["read", "list", "create"] control\_group = { controlled\... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/control-groups.mdx | main | vault | [
-0.03820120915770531,
-0.016777804121375084,
-0.07632085680961609,
0.06507951766252518,
-0.03982199355959892,
-0.028946436941623688,
0.056886132806539536,
0.028101995587348938,
-0.0370328351855278,
0.041743144392967224,
0.061872683465480804,
-0.05589992552995682,
0.06116300821304321,
0.012... | 0.116124 |
# Use performance standby nodes @include 'alerts/enterprise-and-hcp.mdx' Vault supports a multi-server mode for high availability. This mode protects against outages by running multiple Vault servers. High availability mode is automatically enabled when using a data store that supports it. You can learn more about HA m... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/performance-standby.mdx | main | vault | [
0.04559992253780365,
0.06857211887836456,
-0.08222366124391556,
-0.004019117448478937,
-0.024730859324336052,
-0.03067590855062008,
-0.026721196249127388,
-0.01896929182112217,
0.00870240107178688,
-0.014646329917013645,
-0.05517718195915222,
0.12820769846439362,
0.07814288884401321,
-0.09... | 0.057911 |
# Eventual consistency in Vault replication @include 'alerts/enterprise-and-hcp.mdx' When running in a cluster, Vault has an eventual consistency model. Only one node (the leader) can write to backend storage. Users generally expect read-after-write consistency: in other words, after writing foo=1, a subsequent read of... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/consistency.mdx | main | vault | [
0.05794204771518707,
-0.0027740777004510164,
-0.05992911756038666,
0.046865835785865784,
-0.02158374711871147,
-0.0736386701464653,
-0.07399838417768478,
-0.007972352206707,
0.05290934816002846,
0.003455223748460412,
-0.04350995272397995,
0.1350964903831482,
0.11486495286226273,
-0.0604583... | 0.013541 |
span across clusters. As such, when logging in to a secondary cluster using a shared mount, Vault tries to generate an entity and alias if they don't already exist, and these must be stored on the primary using an RPC. Something similar happens with groups. ## Clock skew and replication lag As seen above, both performa... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/consistency.mdx | main | vault | [
0.016772396862506866,
-0.008321892470121384,
-0.04921192303299904,
0.03296112269163132,
0.0670836791396141,
-0.08913115411996841,
-0.08288262039422989,
-0.050757285207509995,
0.07609600573778152,
-0.05796590819954872,
0.004394694231450558,
0.08550955355167389,
0.01868378184735775,
-0.05978... | 0.038304 |
be able to see the value that was just written. If the WAL index isn't seen within those 2 seconds, the Vault node completes the request anyway, returning a warning in the response. This mitigation option still exists in Vault 1.7, though now there is a configuration option to adjust the wait time: [best\_effort\_wal\_... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/consistency.mdx | main | vault | [
0.018225915729999542,
0.04224605858325958,
-0.018623273819684982,
0.0862220823764801,
0.04951576516032219,
-0.05482947826385498,
-0.06330324709415436,
-0.0695916935801506,
0.022861706092953682,
0.03999606892466545,
-0.05496840178966522,
0.0810609757900238,
0.008840302005410194,
-0.07003131... | -0.054408 |
making use of some of the above mitigations without modifying clients. By setting `enforce\_consistency="always"`, Proxy will always provide the `X-Vault-Index` consistency header. The value it uses for the header will be based on the responses that have passed through the Proxy previously. The option `when\_inconsiste... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/consistency.mdx | main | vault | [
-0.04344572871923447,
0.019961997866630554,
0.010967468842864037,
0.01621989905834198,
-0.016844414174556732,
-0.05780414491891861,
-0.035897184163331985,
-0.05919502303004265,
0.015524355694651604,
0.00024204568762797862,
-0.025582121685147285,
0.11585375666618347,
0.06172424554824829,
-0... | -0.011126 |
# Wrap seals with encryption @include 'alerts/enterprise-and-hcp.mdx' Vault Enterprise features a mechanism to wrap values with an extra layer of encryption for supported [seals](/vault/docs/configuration/seal). This adds an extra layer of protection and is useful in some compliance and regulatory environments, includi... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/sealwrap.mdx | main | vault | [
0.007502987515181303,
0.04308673366904259,
-0.038200587034225464,
-0.07791247218847275,
0.01044631376862526,
-0.019440164789557457,
0.01875612884759903,
0.05438933148980141,
0.007139781955629587,
-0.04186294972896576,
-0.002160978503525257,
0.02577868476510048,
0.036989279091358185,
0.0028... | 0.049816 |
takes place below the replication logic. As a result, it is transparent to replication. Replication will convey which values should be seal-wrapped, but it is up to the seal on the local cluster to implement it. In practice, this means that seal wrapping can be used without needing to have the replicated keys on both e... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/sealwrap.mdx | main | vault | [
-0.03875485807657242,
-0.030493898317217827,
-0.0545930378139019,
0.051340486854314804,
0.020973265171051025,
-0.0408160462975502,
-0.011651108041405678,
-0.024004822596907616,
0.0002513956278562546,
0.007966186851263046,
0.07763142138719559,
0.03579267859458923,
0.07448309659957886,
-0.04... | 0.05227 |
# Use redundancy zones @include 'alerts/enterprise-only.mdx' Vault Enterprise redundancy zones provide both read scaling and resiliency benefits by enabling the deployment of non-voting nodes alongside voting nodes on a per availability zone basis. When using redundancy zones, if an operator chooses to deploy Vault acr... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/redundancy-zones.mdx | main | vault | [
0.046276453882455826,
-0.004434932954609394,
-0.06177094951272011,
-0.005075695924460888,
-0.01590110920369625,
-0.023852413520216942,
-0.040455661714076996,
0.03288775682449341,
0.024337105453014374,
0.005359957460314035,
-0.03547590225934982,
0.017885440960526466,
0.13453689217567444,
-0... | 0.057968 |
# Vault HSM support overview @include 'alerts/enterprise-only.mdx' - Root key Wrapping: Vault protects its root key by transiting it through the HSM for encryption rather than splitting into key shares - Automatic Unsealing: Vault stores its HSM-wrapped root key in storage, allowing for automatic unsealing - [Seal Wrap... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/hsm/index.mdx | main | vault | [
-0.029730143025517464,
0.03533152490854263,
-0.06442243605852127,
-0.05298469215631485,
0.042146503925323486,
-0.0017004521796479821,
-0.05526402220129967,
0.049840062856674194,
0.004147700034081936,
-0.032845254987478256,
0.005493787582963705,
0.07720600068569183,
0.03994274511933327,
-0.... | -0.045821 |
# HSM security details @include 'alerts/enterprise-only.mdx' This page provides information to help ensure that a Vault HSM deployment is performed as securely as possible. ## PKCS#11 authentication PKCS#11 authentication occurs via a slot number and PIN. In practice, because the PIN is not required to be numeric (and ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/hsm/security.mdx | main | vault | [
0.004967154935002327,
0.06642505526542664,
-0.11334952712059021,
-0.05341751128435135,
0.017991119995713234,
0.06534488499164581,
0.04446854069828987,
0.05328812077641487,
0.06523825228214264,
-0.048634596168994904,
-0.018808763474225998,
0.06585396826267242,
0.08450616151094437,
-0.078940... | -0.116159 |
# How HSM support changes Vault behavioral @include 'alerts/enterprise-only.mdx' This page contains information about the behavioral differences that take effect when using Vault with an HSM. ## Key split between unseal keys and recovery keys Normally, Vault uses a single set of unseal keys to perform both decryption o... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/hsm/behavior.mdx | main | vault | [
0.02474113181233406,
0.008622259832918644,
-0.03675788268446922,
-0.0218198262155056,
0.04566477611660957,
-0.00384271377697587,
-0.05169844999909401,
0.021720077842473984,
0.013978809118270874,
-0.05140696093440056,
0.038661565631628036,
0.07983137667179108,
0.075923390686512,
-0.07432994... | -0.022245 |
# Configure Vault with time-based, one-time passwords (TOTP) for MFA @include 'alerts/enterprise-only.mdx' This page demonstrates the TOTP MFA on ACL'd paths of Vault. ## Configuration 1. Enable the appropriate auth method: ```text $ vault auth enable userpass ``` 1. Fetch the mount accessor for the enabled auth method... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/mfa/mfa-totp.mdx | main | vault | [
-0.007692848332226276,
0.029835311695933342,
-0.1083666980266571,
-0.03434184566140175,
0.006548863835632801,
-0.012188605964183807,
-0.018040761351585388,
-0.023536527529358864,
0.07333774864673615,
-0.021189028397202492,
0.025153307244181633,
-0.001980176195502281,
0.10886576026678085,
0... | -0.011387 |
# Multi-factor authentication (MFA) support in Vault @include 'alerts/enterprise-only.mdx' Vault Enterprise has support for Multi-factor Authentication (MFA), using different authentication types. MFA is built on top of the Identity system of Vault. ## MFA types MFA in Vault can be of the following types. - \*\*Time-ba... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/mfa/index.mdx | main | vault | [
-0.021656164899468422,
0.019585156813263893,
-0.06107410788536072,
-0.055924106389284134,
0.03608047217130661,
-0.0018864027224481106,
0.0127103291451931,
-0.025270303711295128,
0.06238490343093872,
-0.024228829890489578,
-0.0011194846592843533,
-0.008241632021963596,
0.10324518382549286,
... | 0.045439 |
# Configure Vault with Duo for MFA @include 'alerts/enterprise-only.mdx' This page demonstrates the Duo MFA on ACL'd paths of Vault. ## Configuration 1. Enable the appropriate auth method: ```text $ vault auth enable userpass ``` 1. Fetch the mount accessor for the enabled auth method: ```text $ vault auth list -detail... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/mfa/mfa-duo.mdx | main | vault | [
-0.0016779020661488175,
0.031950198113918304,
-0.11330920457839966,
-0.056474052369594574,
-0.0053274743258953094,
-0.03803510218858719,
-0.02998613752424717,
-0.01127844862639904,
0.055715516209602356,
-0.049109816551208496,
0.06787364184856415,
-0.028972426429390907,
0.10127893835306168,
... | -0.020895 |
# Configure Vault with PingID for MFA @include 'alerts/enterprise-only.mdx' This page demonstrates PingID MFA on ACL'd paths of Vault. ## Configuration 1. Enable the appropriate auth method: ```text $ vault auth enable userpass ``` 1. Fetch the mount accessor for the enabled auth method: ```text $ vault auth list -deta... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/mfa/mfa-pingid.mdx | main | vault | [
0.011043732985854149,
0.053830500692129135,
-0.09846805781126022,
-0.04187683016061783,
-0.021422870457172394,
-0.05261770635843277,
0.017291994765400887,
-0.032390985637903214,
0.05499231070280075,
-0.013211939483880997,
0.027180351316928864,
-0.017472149804234505,
0.09570469707250595,
0.... | 0.031468 |
# Configure Vault with Okta for MFA @include 'alerts/enterprise-only.mdx' This page demonstrates the Okta MFA on ACL'd paths of Vault. ## Configuration 1. Enable the appropriate auth method: ```text $ vault auth enable userpass ``` 1. Fetch the mount accessor for the enabled auth method: ```text $ vault auth list -deta... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/mfa/mfa-okta.mdx | main | vault | [
0.0025964449159801006,
0.07253921777009964,
-0.07851886749267578,
-0.027815578505396843,
-0.016522321850061417,
-0.05618137866258621,
-0.006967298686504364,
-0.024419035762548447,
0.06960974633693695,
-0.030647549778223038,
0.05588707700371742,
-0.021342681720852852,
0.09549478441476822,
0... | -0.003967 |
# Configure SSH secrets engine to use PKCS 11 HSM using managed keys @include 'alerts/enterprise-only.mdx' SSH secrets engine can be pluged into Vault's centralised abstraction layer called [managed keys](/vault/docs/enterprise/managed-keys) to delegate crypto-operations operations to a trusted external KMS or HSM. Thi... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/managed-keys/ssh-secret-engine.mdx | main | vault | [
0.03827550262212753,
0.03145357966423035,
-0.11187858134508133,
-0.03501224145293236,
-0.027654172852635384,
0.05436326190829277,
-0.027663636952638626,
0.027686048299074173,
-0.012638087384402752,
-0.02930929884314537,
-0.014554282650351524,
-0.016917891800403595,
0.09267602115869522,
-0.... | -0.028879 |
You configured the managed key with `any\_mount=false` in the previous step. This command grants access to the `ssh-CA-key` to the SSH secrets engine's mount. 1. Configure SSH CA to use managed keys. ```shell-session $ vault write ssh-client-signer/config/ca managed\_key\_name="ssh-CA-key" Success! Data written to: ssh... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/managed-keys/ssh-secret-engine.mdx | main | vault | [
0.08369086682796478,
0.022435320541262627,
-0.012538798153400421,
0.037472743541002274,
-0.021809406578540802,
0.01658627763390541,
-0.05384209752082825,
0.02465626411139965,
0.04327823221683502,
0.025422189384698868,
0.04804941639304161,
-0.03234807774424553,
0.09004940837621689,
0.070038... | -0.100816 |
# Use 3rd party key management for private keys @include 'alerts/enterprise-and-hcp.mdx' Within certain environments, customers want to leverage key management systems external to Vault, when handling, storing, and interacting with private key material, or are required to do so by standards requirements. To satisfy the... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/managed-keys/index.mdx | main | vault | [
0.018765978515148163,
0.022674858570098877,
-0.07571486383676529,
-0.04390627145767212,
0.0033063862938433886,
-0.02218904159963131,
0.034847769886255264,
0.022485341876745224,
0.061065759509801865,
-0.03416534513235092,
-0.005091247148811817,
0.015001285821199417,
0.16541218757629395,
-0.... | -0.001345 |
# Configure transit secrets engine to use PKCS 11 HSM using managed keys @include 'alerts/enterprise-only.mdx' Transit secrets engine can be pluged into Vault's centralised abstraction layer called [managed keys](/vault/docs/enterprise/managed-keys) to delegate crypto-operations operations to a trusted external KMS or ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/managed-keys/transit-secret-engine.mdx | main | vault | [
0.031011218205094337,
0.0069323196075856686,
-0.0882059782743454,
-0.0406903438270092,
-0.030127625912427902,
0.02147066965699196,
-0.011759631335735321,
0.009097428061068058,
-0.01956319622695446,
-0.0347907654941082,
-0.03626841679215431,
-0.0016386602073907852,
0.13271711766719818,
-0.0... | -0.022598 |
Create a transit key. ```shell-session $ vault write transit/keys/hsm-transit-key \ type=managed\_key \ managed\_key\_name=transit-rsa-key \ allow\_plaintext\_backup=false \ exportable=false ``` \*\*Example output:\*\* ```text Key Value --- ----- allow\_plaintext\_backup false auto\_rotate\_period 0s deletion\_allowed ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/managed-keys/transit-secret-engine.mdx | main | vault | [
0.054552361369132996,
0.015207221731543541,
-0.09707551449537277,
0.011929155327379704,
-0.024944353848695755,
0.039842139929533005,
-0.015463161282241344,
0.016886716708540916,
-0.008597984910011292,
0.037532176822423935,
0.04413037747144699,
0.006707644090056419,
0.10596689581871033,
-0.... | -0.063121 |
# Examples @include 'alerts/enterprise-and-hcp.mdx' Following are some examples that help to introduce concepts. If you are unfamiliar with writing Sentinel policies in Vault, please read through to understand some best practices. Additional examples can be found [here](https://github.com/hashicorp/vault-guides/tree/ma... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/sentinel/examples.mdx | main | vault | [
0.02210845984518528,
0.016211438924074173,
-0.03742792457342148,
-0.059005189687013626,
0.032001759856939316,
-0.04726240783929825,
0.032970309257507324,
-0.0006000141729600728,
-0.042310841381549835,
-0.009534992277622223,
0.04750522971153259,
0.0006723603582940996,
0.07839310169219971,
0... | 0.072527 |
given time. Tokens created after this time, since they were not a part of the compromise, will not be subject to this restriction. ## Delegate EGP policy management under a path The following policy gives token holders with this policy (via their tokens or their Identity entities/groups) the ability to write EGP polici... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/sentinel/examples.mdx | main | vault | [
-0.0228984784334898,
0.04755312204360962,
-0.0013618513476103544,
-0.029911808669567108,
-0.0501164011657238,
-0.08551893383264542,
0.030092576518654823,
-0.008240844123065472,
0.020808586850762367,
-0.00048307570978067815,
0.026953376829624176,
0.004286942537873983,
0.06466200202703476,
0... | -0.040894 |
# Sentinel properties for Vault @include 'alerts/enterprise-and-hcp.mdx' Vault injects a rich set of data into the running Sentinel environment, allowing for very fine-grained controls. The set of available properties are enumerated on this page. The following properties are available for use in Sentinel policies. ## N... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/sentinel/properties.mdx | main | vault | [
0.01488829031586647,
0.005184502806514502,
-0.06512615829706192,
0.05899776145815849,
0.025763900950551033,
-0.053915154188871384,
0.04847369343042374,
-0.0228953268378973,
0.04778439179062843,
-0.01915225014090538,
-0.03333922475576401,
-0.06029264256358147,
0.09581832587718964,
-0.018618... | 0.072462 |
use-count limit | | `path` | `string` | The request path that resulted in creation of this token | | `period` | `duration` | If the token has a period, the duration of the period in nanoseconds, suitable for use with the `time` import | | `period\_seconds` | `int` | If the token has a period, the duration of the period... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/sentinel/properties.mdx | main | vault | [
-0.04904733598232269,
-0.04368393495678902,
-0.049480319023132324,
0.06086880713701248,
-0.05432035028934479,
-0.009954825975000858,
0.07460718601942062,
0.04486313462257385,
0.01578359864652157,
0.011051449924707413,
0.005090935155749321,
-0.07665286958217621,
0.038166895508766174,
0.0244... | 0.156762 |
`string` | The alias's name | ### Groups properties These exist at the `identity.groups` namespace. | Name | Type | Description | | :-------- | :---------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------- | | `b... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/sentinel/properties.mdx | main | vault | [
0.025606926530599594,
0.09669053554534912,
-0.0011473018676042557,
0.033796221017837524,
-0.08342663943767548,
0.023592554032802582,
0.12508904933929443,
0.017522694543004036,
-0.028866775333881378,
-0.045517053455114365,
0.06350109726190567,
-0.06830152124166489,
-0.009161158464848995,
-0... | 0.043411 |
# Manage Vault policies with Sentinel @include 'alerts/enterprise-and-hcp.mdx' Vault Enterprise integrates HashiCorp Sentinel to provide a rich set of access control functionality. Because Vault is a security-focused product trusted with high-risk secrets and assets, and because of its default-deny stance, integration ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/sentinel/index.mdx | main | vault | [
0.003147728042677045,
0.03237760066986084,
-0.05458604916930199,
-0.03532181680202484,
0.06681542843580246,
-0.04544166103005409,
0.035180818289518356,
-0.008579699322581291,
0.06292647123336792,
-0.01171512994915247,
0.007407257333397865,
0.06155781447887421,
0.051541611552238464,
0.00837... | 0.113386 |
education namespace. The group members inherit the group-level policy.   #### Versions 1.15.0-rc1, 1.14.3, 1.13.7, and earlier The training namespace is a child n... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/sentinel/index.mdx | main | vault | [
-0.07481696456670761,
0.0022505398374050856,
-0.0115206278860569,
0.06714606285095215,
0.07560379058122635,
0.0010607769945636392,
0.04513900727033615,
-0.10817851126194,
0.01925901137292385,
-0.0172323826700449,
0.09834884107112885,
0.003985957708209753,
0.01188441552221775,
0.06200068444... | 0.086481 |
learn how to author Sentinel policies in Vault. | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/sentinel/index.mdx | main | vault | [
0.06058631092309952,
0.003574794391170144,
-0.04251173883676529,
-0.0003174252633471042,
0.06024457514286041,
-0.031034696847200394,
-0.013696813024580479,
-0.009023045189678669,
-0.022176364436745644,
0.057312171906232834,
-0.005229320377111435,
0.06181250885128975,
0.013814177364110947,
... | 0.128722 |
# Run Vault with many namespaces @include 'alerts/enterprise-and-hcp.mdx' Use namespaces to create isolated environments within Vault Enterprise. By default, Vault limits the number and depth of namespaces based on your storage configuration. The information below provides guidance on how to modify your namespace limit... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/namespaces/namespace-limits.mdx | main | vault | [
0.04556455463171005,
-0.015283891931176186,
-0.02628905139863491,
-0.05593978986144066,
-0.030894819647073746,
-0.09246468544006348,
-0.04175432398915291,
-0.0366586409509182,
0.024258961901068687,
-0.05085399001836777,
-0.031167156994342804,
-0.021372506394982338,
0.10842755436897278,
-0.... | -0.031579 |
By default, Vault uses 256 workers to perform rollback operations. Mounts with a large number of namespaces can become bottlenecks that slow down the overall rollback process. The effects of the slowdown vary based on the particular mounts. At minimum, your Vault deployment will take longer to fully purge stale data an... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/namespaces/namespace-limits.mdx | main | vault | [
0.010835608467459679,
0.015685470774769783,
-0.041018739342689514,
-0.018755409866571426,
-0.03243444487452507,
-0.13927839696407318,
-0.04477264732122421,
-0.061123378574848175,
0.03740585967898369,
-0.017844879999756813,
0.06021728366613388,
0.08367785066366196,
0.05696643143892288,
-0.0... | -0.067064 |
# Namespace and secure multi-tenancy (SMT) support in Vault @include 'alerts/enterprise-and-hcp.mdx' Many organizations implement Vault as a service to provide centralized management of sensitive data and ensure that the different teams in an organization operate within isolated environments known as \*\*tenants\*\*. M... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/namespaces/index.mdx | main | vault | [
0.013461918570101261,
0.008960124105215073,
-0.05316684767603874,
-0.030142158269882202,
0.008431443944573402,
-0.052184395492076874,
-0.017053963616490364,
-0.05357634648680687,
0.10125841200351715,
-0.02471388317644596,
-0.0024147971998900175,
0.011409514583647251,
0.09117836505174637,
0... | 0.01281 |
You can also provide an absolute namespace path without using the `X-Vault-Namespace` header. Vault constructs the fully qualified namespace path based on the calling namespace and the `X-Vault` header to route the request to the appropriate namespace. For example, the following requests all route to the `ns1/ns2/secre... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/namespaces/index.mdx | main | vault | [
0.006829739548265934,
-0.04499064385890961,
-0.09365471452474594,
-0.02018074132502079,
-0.023666130378842354,
-0.0946463942527771,
-0.03637252375483513,
0.01518084667623043,
0.04913315549492836,
-0.04717637225985527,
-0.009485345333814621,
-0.05472882464528084,
0.06322383880615234,
0.0696... | -0.032113 |
# Best practices for namespaces and mount paths Namespaces are isolated environments that functionally create "Vaults within a Vault." They have separate login paths, and support creating and managing data isolated to their namespace. This functionality enables you to provide Vault as a service to tenants. , which can ease policy management. Vault provides an internal layer of identity management that can be used to map entities t... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/namespaces/namespace-structure.mdx | main | vault | [
-0.031067965552210808,
0.026632802560925484,
-0.07900137454271317,
-0.02926938235759735,
0.018291050568223,
0.006092084106057882,
0.04977875202894211,
0.025079762563109398,
0.062152471393346786,
-0.04014122486114502,
-0.006006376352161169,
-0.008210721425712109,
0.053417790681123734,
0.018... | 0.001213 |
needed and the roles defined within the mounts. Sharing mounts between teams has benefits and risk. It is up to you to find the right balance of granularity between the various mounts needed and the roles defined within the mounts. Below are a couple use cases with their benefits and risks. You create a single KV mount... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/namespaces/namespace-structure.mdx | main | vault | [
-0.05502650514245033,
0.00993144791573286,
-0.028735697269439697,
-0.0406063050031662,
0.04496144503355026,
-0.029115844517946243,
-0.08542801439762115,
0.07474134117364883,
0.05026452615857124,
-0.09809854626655579,
-0.00873283576220274,
-0.03404775634407997,
0.1086651012301445,
0.0720871... | -0.000952 |
# Create an administrative namespace @include 'alerts/enterprise-only.mdx' Grant access to a predefined subset of privileged system backend endpoints in the Vault API with an administrative namespace. HCP Vault Dedicated clusters include an administrative namespace (`admin`) by default. For more information on managing... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/namespaces/create-admin-namespace.mdx | main | vault | [
0.09422393143177032,
0.017560478299856186,
-0.08119691163301468,
-0.08146706223487854,
-0.03622480854392052,
-0.021873870864510536,
-0.0026477561332285404,
0.019420960918068886,
0.022490937262773514,
-0.0069948649033904076,
-0.01769842579960823,
-0.09615021198987961,
0.13410957157611847,
-... | -0.036828 |
# Configure cross namespace access in Vault Using the `sys/config/group\_policy\_application` endpoint, you can enable secrets sharing across multiple independent namespaces. Historically, any policies attached to an [identity group](/vault/docs/concepts/identity#identity-groups) would only apply when the Vault token a... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/namespaces/configure-cross-namespace-access.mdx | main | vault | [
-0.021371355280280113,
-0.007890328764915466,
-0.06480806320905685,
-0.0064069610089063644,
-0.0021145588252693415,
-0.08020806312561035,
0.018024472519755363,
-0.06502139568328857,
0.08074432611465454,
-0.027245737612247467,
0.03757045418024063,
0.013934046030044556,
0.05478772521018982,
... | -0.030338 |
# Exclusion syntax for audit data @include 'alerts/enterprise-only.mdx' As of Vault 1.18.0, you can enable audit devices with an `exclude` option to exclude specific fields in an audit entry that is written to a particular audit log, and fine-tune your auditing process. Excluding audit entry fields is an advanced featu... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/audit/exclusion.mdx | main | vault | [
0.09198006987571716,
0.11149786412715912,
-0.00972567219287157,
-0.018325749784708023,
0.11241883039474487,
-0.060129713267087936,
0.03634416684508324,
-0.1136397197842598,
0.06945326924324036,
-0.01455245353281498,
0.05341329053044319,
-0.014007741585373878,
0.08991552144289017,
-0.022213... | -0.057489 |
"", "forwarded\_from": "", "request": , "response": , "time": "", "type": "" } ``` ### Auth object (``) The following auth object definition includes example data with simple types (`string`, `bool`, `int`) and used in other JSON examples that include an `` object. ```json { "accessor": "", "client\_token": "", "displa... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/audit/exclusion.mdx | main | vault | [
-0.030813485383987427,
0.06850933283567429,
-0.020564043894410133,
0.028908632695674896,
-0.0325421541929245,
-0.057597316801548004,
0.048155736178159714,
0.014512463472783566,
0.03729929402470589,
0.03041299432516098,
-0.01463439129292965,
-0.07345273345708847,
0.039265889674425125,
0.068... | 0.076675 |
# Filter syntax for audit data @include 'alerts/enterprise-only.mdx' As of Vault 1.16.0, you can enable audit devices with a `filter` option to limit the audit entries written to a particular audit log and fine-tune your auditing process. Filtering audit logs is an advanced feature. Exclusively enabling filtered device... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/audit/filtering.mdx | main | vault | [
0.09199928492307663,
0.0567946694791317,
-0.01180377509444952,
-0.029405953362584114,
0.10625939816236496,
-0.09501080214977264,
0.03441530093550682,
-0.09607076644897461,
0.05813633278012276,
-0.02300933748483658,
-0.010663074441254139,
-0.004867694340646267,
0.08006861805915833,
0.022051... | -0.08112 |
| `sys/audit/test` ## `filter` properties for audit devices Filters can only reference the following properties of an audit entry: Property | Example | Description ------------- | ----------------------------------- | -------------------------- `mount\_point` | `mount\_point == \"auth/oidc\"` | Log all entries for the ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/audit/filtering.mdx | main | vault | [
0.007062443532049656,
0.02913191169500351,
-0.025210365653038025,
0.02841397002339363,
0.03887799009680748,
-0.08513251692056656,
0.10100090503692627,
0.009325454942882061,
0.044316839426755905,
-0.017765773460268974,
0.07683022320270538,
-0.1079811230301857,
0.029606783762574196,
0.045670... | -0.025814 |
# Check for Merkle tree corruption @include 'alerts/enterprise-only.mdx' Vault Enterprise replication uses Merkle trees to keep the cluster state, and rolls cluster state into a Merkle root hash. When data is updated or removed in a cluster, the Merkle tree is also updated. In certain circumstances detailed later in th... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/replication/check-merkle-tree-corruption.mdx | main | vault | [
0.08915053308010101,
0.02416209876537323,
0.0089715039357543,
-0.05085151642560959,
0.1013079509139061,
-0.14140662550926208,
-0.0943574532866478,
-0.020099112764000893,
0.055981166660785675,
-0.0012229979038238525,
-0.0007225569570437074,
0.07000743597745895,
0.05951794981956482,
-0.06448... | -0.033391 |
state machine (FSM) is entering merkle-diff mode, in which it tries to fetch conflicting pages from the primary cluster. The diff result is empty, indicated by an immediate switch to the stream-wals mode and \*\*skipping the merkle-sync operation\*\*. Further into the log, the performance secondary cluster immediately ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/replication/check-merkle-tree-corruption.mdx | main | vault | [
0.00042521601426415145,
0.019383398815989494,
0.016651557758450508,
0.011504851281642914,
0.10061927139759064,
-0.10280634462833405,
-0.0063692848198115826,
-0.04226395860314369,
0.011465921066701412,
-0.0003627886762842536,
0.01719857193529606,
0.049092382192611694,
0.022950485348701477,
... | 0.011585 |
in the subtrees, including replicated and local subtrees. The replicated tree is indexed by number 1 in the map and the local tree is indexed by number `2`. The `tree\_type` sub-field also shows which tree contains a corrupted page. The replicated subtree stores the information that is replicated to either a disaster r... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/replication/check-merkle-tree-corruption.mdx | main | vault | [
-0.07576365768909454,
0.02926618792116642,
0.04836774244904518,
0.021551379933953285,
0.0367484949529171,
-0.12093871831893921,
-0.10508710145950317,
-0.06699579209089279,
0.041757676750421524,
-0.0026608675252646208,
0.0038997449446469545,
0.07321301847696304,
0.06609289348125458,
-0.0500... | 0.102634 |
these indexes are repeated for every page. It's possible that only the full page is corrupted without having any corrupted subpages. In that case, the `corrupted` field in the page map is true, and no subpages are listed. ## Caveats and considerations We generally recommend that you consult the merkle-check endpoint be... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/replication/check-merkle-tree-corruption.mdx | main | vault | [
-0.0018609820399433374,
-0.001224258914589882,
0.10426026582717896,
0.021634185686707497,
0.03410855308175087,
-0.05882349982857704,
-0.06670171022415161,
-0.0853753462433815,
-0.043126825243234634,
-0.01655401848256588,
0.01707673817873001,
0.10659340023994446,
0.008445926010608673,
-0.10... | -0.00836 |
# Replication support in Vault @include 'alerts/enterprise-and-hcp.mdx' ## Overview Many organizations have infrastructure that spans multiple datacenters. Vault provides the critical services of identity management, secrets storage, and policy management. This functionality is expected to be highly available and to sc... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/replication/index.mdx | main | vault | [
-0.027034573256969452,
-0.029760025441646576,
-0.06848212331533432,
-0.044533621519804,
-0.02462564781308174,
-0.06926718354225159,
-0.05247753486037254,
-0.01613864302635193,
0.07140152156352997,
0.031203482300043106,
-0.014052332378923893,
0.09868607670068741,
0.15052427351474762,
-0.028... | 0.141185 |
There exist other storage entries that aren't mount specific. For example, the Integrated Storage Autopilot configuration is an `ignored` storage entry, which allows for disaster recovery secondaries to have a different configuration than their primary. Tokens and leases are written to `local` storage entries. ## Perfo... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/replication/index.mdx | main | vault | [
0.0219980850815773,
-0.006316386163234711,
-0.03563351929187775,
-0.04029555991292,
-0.027999848127365112,
-0.06739690154790878,
-0.07872620970010757,
0.022433122619986534,
0.06825792789459229,
0.0010664529399946332,
-0.020661378279328346,
0.04047157242894173,
0.14687180519104004,
0.021695... | 0.037174 |
the same seal type, but see [sealwrap](/vault/docs/enterprise/sealwrap#seal-wrap-and-replication) for the full details. Also note that enabling replication will modify the secondary seal. If the secondary uses an auto seal, its recovery configuration and keys will be replaced; if it uses shamir, its seal configuration ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/replication/index.mdx | main | vault | [
-0.02689964510500431,
-0.0036121250595897436,
-0.021285608410835266,
-0.043048519641160965,
-0.029246436432003975,
-0.03461671993136406,
-0.015920262783765793,
0.012763602659106255,
-0.02500295825302601,
-0.05938097834587097,
0.06410139799118042,
0.0820264220237732,
0.07320650666952133,
-0... | 0.007652 |
replication token to carry the redirect address of the primary cluster as part of the token. In most cases this means that simply providing the token to a new secondary is enough to activate replication, although this can also be overridden when the token is provided to the secondary. Secondary activation tokens should... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/replication/index.mdx | main | vault | [
-0.04409891739487648,
0.0146231260150671,
-0.026868827641010284,
-0.011723264120519161,
0.020390773192048073,
-0.08376366645097733,
-0.021151505410671234,
0.030377758666872978,
0.05519680306315422,
-0.02973148785531521,
0.027603954076766968,
0.06881701946258545,
0.0656614750623703,
-0.0210... | 0.145552 |
# PKCS#11 support in Vault @include 'alerts/enterprise-only.mdx' PKCS11 provider is part of the [KMIP Secret Engine](/vault/docs/secrets/kmip), which requires [Vault Enterprise](https://www.hashicorp.com/products/vault/pricing) with the Advanced Data Protection (ADP) module. The PKCS11 provider supports a subset of key... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/pkcs11-provider/index.mdx | main | vault | [
-0.04207255318760872,
0.08647473156452179,
-0.10779361426830292,
-0.11311567574739456,
0.021991709247231483,
-0.049883883446455,
-0.018958982080221176,
0.012439871206879616,
0.08766487240791321,
-0.05037236958742142,
-0.02486271969974041,
0.024789879098534584,
0.028238829225301743,
-0.0494... | -0.010001 |
```hcl slot { server = "127.0.0.1:5696" tls\_cert\_path = "cert.pem" ca\_path = "ca.pem" scope = "my-service" } ``` See [below](#configuration) for all available parameters. 1. Copy the certificates from the KMIP credentials into the files specified in the configuration file (e.g., `cert.pem`, and `ca.pem`). 1. You sho... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/pkcs11-provider/index.mdx | main | vault | [
-0.0063571622595191,
0.04164232313632965,
-0.08049259334802628,
-0.08383610099554062,
-0.08432477712631226,
0.006470114458352327,
-0.03721269220113754,
-0.015016709454357624,
0.052230194211006165,
-0.0736498013138771,
-0.005361253395676613,
-0.07560557126998901,
0.06508706510066986,
-0.005... | -0.102323 |
- `VAULT\_KMIP\_CA\_FILE`: location of the TLS CA bundle used to authenticate the connection to the KMIP engine. - `VAULT\_KMIP\_SERVER`: address and port of the KMIP engine to use for encryption and storage. - `VAULT\_KMIP\_SCOPE`: KMIP scope to use for encryption and storage - `VAULT\_KMIP\_CACHE`: whether or not to ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/pkcs11-provider/index.mdx | main | vault | [
-0.004903055261820555,
0.07208966463804245,
-0.03447575122117996,
-0.034844327718019485,
-0.01640172488987446,
-0.07341545075178146,
0.054565366357564926,
0.0021601843181997538,
0.061828963458538055,
-0.03001091070473194,
0.039212919771671295,
-0.014020998030900955,
0.07022111862897873,
-0... | 0.009574 |
| The following signing mechanisms are currently supported: | Name | Mechanism Number |Provider Version|Vault Version| | ------------------ | ---------------- |----------------|-------------| | RSA-PKCS | `0x0001` | 0.2.0 | 1.13 | | SHA256-RSA-PKCS | `0x0040` | 0.2.0 | 1.13 | | SHA384-RSA-PKCS | `0x0041` | 0.2.0 | 1.13... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/pkcs11-provider/index.mdx | main | vault | [
0.0005371366860345006,
-0.04234844818711281,
-0.0773354023694992,
-0.11539492011070251,
-0.003937201574444771,
-0.04304652288556099,
-0.042671237140893936,
-0.015323737636208534,
0.012022987008094788,
-0.0033036042004823685,
0.059210143983364105,
-0.0019491893472149968,
0.06945737451314926,
... | -0.058083 |
- [ ] `C\_InitPIN` - [ ] `C\_SetPIN` - [ ] `C\_GetOperationState` - [ ] `C\_SetOperationState` - [ ] `C\_GetFunctionStatus` - [ ] `C\_CancelFunction` - [ ] `C\_WaitForSlotEvent` - Signing - [ ] `C\_SignInit` - [ ] `C\_Sign` - [ ] `C\_SignUpdate` - [ ] `C\_SignFinal` - [ ] `C\_SignRecoverInit` - [ ] `C\_SignRecover` - [... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/pkcs11-provider/index.mdx | main | vault | [
-0.0072735995054244995,
0.029951198026537895,
-0.10247386991977692,
-0.04505064710974693,
-0.023707032203674316,
-0.055028144270181656,
0.11379627138376236,
0.05681261420249939,
-0.04894546419382095,
-0.02630332112312317,
0.04757431522011757,
-0.08989565819501877,
0.003320126561447978,
-0.... | 0.120161 |
# Configure PKCS#11 with AWS KMS external key store (XKS) @include 'alerts/enterprise-only.mdx' ~> \*\*Note\*\*: AWS [`xks-proxy`](https://github.com/aws-samples/aws-kms-xks-proxy) is used in this document as a sample implementation. Vault's KMIP Secrets Engine can be used as an external key store for the AWS KMS [Exte... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/pkcs11-provider/aws-xks.mdx | main | vault | [
-0.056434955447912216,
0.08130337297916412,
-0.06752168387174606,
-0.06331825256347656,
0.005660844501107931,
-0.026680372655391693,
0.02469555288553238,
0.016824871301651,
0.06339042633771896,
0.04737009108066559,
-0.0013532371958717704,
0.03480474650859833,
0.09478447586297989,
-0.067735... | -0.016275 |
and CA bundle (e.g., `/etc/kmip/ca.pem`) to the `xks-proxy` server (doesn't matter where, as long as the `xks-proxy` process has access to it) from the Vault setup. 1. Create a `configuration/settings\_vault.toml` file for the XKS to Vault PKCS#11 configuration, and set the `XKS\_PROXY\_SETTINGS\_TOML` environment vari... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/pkcs11-provider/aws-xks.mdx | main | vault | [
-0.009609807282686234,
0.043705277144908905,
-0.09794197976589203,
-0.09639876335859299,
-0.06782949715852737,
-0.06896091997623444,
-0.04370773583650589,
0.012461479753255844,
0.04843054339289665,
-0.027529867365956306,
0.023018375039100647,
-0.006930243689566851,
0.08640158176422119,
0.0... | -0.133972 |
"", "KeyUsage": "ENCRYPT\_DECRYPT", "KeyState": "Enabled", "Origin": "EXTERNAL\_KEY\_STORE", "CustomKeyStoreId": "cks-16460f66b34705025", "KeyManager": "CUSTOMER", "CustomerMasterKeySpec": "SYMMETRIC\_DEFAULT", "KeySpec": "SYMMETRIC\_DEFAULT", "EncryptionAlgorithms": [ "SYMMETRIC\_DEFAULT" ], "MultiRegion": false, "Xks... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/pkcs11-provider/aws-xks.mdx | main | vault | [
-0.006309036165475845,
0.05300198495388031,
-0.01815217360854149,
-0.045717258006334305,
-0.030737269669771194,
-0.0011734176659956574,
0.07012716680765152,
-0.007536240387707949,
0.03359004855155945,
0.06790528446435928,
0.029136309400200844,
-0.11086145788431168,
0.06421005725860596,
-0.... | -0.037635 |
# Configure PKCS#11 with Oracle TDE @include 'alerts/enterprise-only.mdx' [Oracle Transparent Data Encryption](https://docs.oracle.com/en/database/oracle/oracle-database/19/asoag/introduction-to-transparent-data-encryption.html) (TDE) is supported with the [Vault PKCS#11 provider](/vault/docs/enterprise/pkcs11-provider... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/pkcs11-provider/oracle-tde.mdx | main | vault | [
-0.03290693461894989,
0.022538132965564728,
-0.07206129282712936,
-0.09490526467561722,
-0.019242167472839355,
-0.02589435689151287,
0.021713700145483017,
0.02695772983133793,
0.04080388322472572,
-0.010763154365122318,
-0.0472000427544117,
-0.0031570785213261843,
0.05539954826235771,
-0.0... | -0.0351 |
the location of the CA bundle on the Oracle database. - `scope` is the KMIP scope to authenticate against and where the TDE master keys and associated metadata will be stored. The default location the PKCS#11 library will look for the configuration file is the current directory (`./vault-pkcs11.hcl`) and `/etc/vault-pk... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/pkcs11-provider/oracle-tde.mdx | main | vault | [
0.03135288879275322,
0.028995012864470482,
-0.06729406863451004,
-0.04852854087948799,
0.004053791519254446,
-0.0356932133436203,
-0.0027878268156200647,
0.05859712138772011,
0.014523042365908623,
0.0004957969067618251,
0.010227094404399395,
-0.08956830203533173,
0.06521448493003845,
0.017... | -0.086971 |
# FIPS compliance in Vault @include 'alerts/enterprise-only.mdx' The [Federal Information Processing Standard](https://www.nist.gov/federal-information-standards-fips) is a cryptography-focused certification standard for U.S. Government usage. ## FIPS 140-3 attestation [Leidos](https://www.leidos.com/capabilities/techn... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/fips/index.mdx | main | vault | [
-0.004969221539795399,
0.00412214919924736,
-0.04959610849618912,
-0.06924385577440262,
0.029530880972743034,
-0.05162717029452324,
0.008405430242419243,
0.025518249720335007,
0.023033147677779198,
-0.001290011452510953,
0.023317554965615273,
0.05754879489541054,
-0.030873442068696022,
0.0... | 0.082066 |
# Built-in FIPS 140-3 support @include 'alerts/enterprise-only.mdx' Special builds of Vault Enterprise (marked with a `fips1403` feature name) include built-in support for FIPS 140-3 compliance. Unlike using Seal Wrap for FIPS compliance, this binary has no external dependencies on a HSM. To use this feature, you must ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/fips/fips1403.mdx | main | vault | [
0.014212783426046371,
0.01725909486413002,
-0.03697706386446953,
-0.07555609196424484,
0.014749032445251942,
-0.05414588376879692,
-0.043864957988262177,
0.023439880460500717,
0.05238497629761696,
-0.015073052607476711,
0.014333224855363369,
0.05450247600674629,
-0.006144715938717127,
0.00... | 0.056914 |
Root CA involves a concerted, non-Vault effort to accomplish and must be done thoughtfully. As such Hashicorp cannot provide support for workloads that are affected either technically or via non-compliance that results from converting existing cluster workloads to the FIPS 140-3 Inside binary. Instead, we suggest leavi... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/fips/fips1403.mdx | main | vault | [
-0.007504377979785204,
0.00405485462397337,
-0.04060612618923187,
-0.027536673471331596,
-0.005045995581895113,
-0.08486604690551758,
-0.0787568986415863,
0.000665422820020467,
0.05138406530022621,
-0.0026194655802100897,
0.019345667213201523,
-0.004308834671974182,
-0.008287378586828709,
... | 0.025533 |
(gdb) run ...additional GDB output elided... Thread 1 "vault" hit Breakpoint 1, 0x0000000000454950 in \_goboringcrypto\_BORINGSSL\_bcm\_power\_on\_self\_test () (gdb) backtrace #0 0x0000000000454950 in \_goboringcrypto\_BORINGSSL\_bcm\_power\_on\_self\_test () #1 0x00000000005da8f0 in runtime.asmcgocall () at /usr/loca... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/fips/fips1403.mdx | main | vault | [
-0.0060709998942911625,
-0.0029756512958556414,
-0.1029466763138771,
0.016939135268330574,
-0.014238575473427773,
-0.1107928603887558,
-0.027913521975278854,
0.014111170545220375,
-0.01001644041389227,
-0.04901393875479698,
0.05123429745435715,
-0.02597288228571415,
-0.0597112700343132,
-0... | 0.044238 |
# Seal wrap for FIPS compliance @include 'alerts/enterprise-only.mdx' Vault Enterprise features a mechanism to wrap values with an extra layer of encryption for supporting [seals](/vault/docs/configuration/seal). This adds an extra layer of protection and is useful in some compliance and regulatory environments, includ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/enterprise/fips/sealwrap.mdx | main | vault | [
-0.012619154527783394,
0.041273415088653564,
-0.034889545291662216,
-0.05786373093724251,
0.026522504165768623,
-0.03934890404343605,
0.025060376152396202,
0.06803177297115326,
0.003590361215174198,
-0.015233650803565979,
0.018568048253655434,
0.029045453295111656,
0.02405538223683834,
0.0... | 0.069481 |
# Userpass auth method @include 'tips/custom-authn.mdx' The `userpass` auth method allows users to authenticate with Vault using a username and password combination. The username/password combinations are configured directly to the auth method using the `users/` path. This method cannot read usernames and passwords fro... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/userpass.mdx | main | vault | [
0.03861241787672043,
0.002624504268169403,
-0.0768350213766098,
-0.0931297317147255,
-0.0845683142542839,
-0.026585830375552177,
-0.001088623539544642,
0.014052147977054119,
0.03398982062935829,
-0.030677879229187965,
-0.014440660364925861,
-0.014443513937294483,
0.10867445915937424,
0.026... | -0.114614 |
# OCI auth method The OCI Auth method for Vault enables authentication and authorization using [OCI Identity](https://docs.cloud.oracle.com/iaas/Content/Identity/Concepts/overview.htm) credentials. This plugin is developed in a separate GitHub repository at https://github.com/hashicorp/vault-plugin-auth-oci, but is aut... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/oci.mdx | main | vault | [
-0.03892906755208969,
0.05409237742424011,
-0.06467270851135254,
-0.014267674647271633,
0.01159329991787672,
-0.12175469100475311,
0.05099674314260483,
-0.0029775002039968967,
0.06388887017965317,
-0.0795627310872078,
0.00897341687232256,
0.02052350901067257,
0.07945127040147781,
0.0565311... | 0.053435 |
group previously created. - In production, add only the OCID of groups and dynamic groups that can take the admin role in Vault. ```json { "token\_policies": "vaultadminpolicy", "token\_ttl": "1800", "ocid\_list": "ocid1.group.oc1..aaaaaaaaiqnblimpvmegkqh3bxilrdvjobr7qd223g275idcqhexamplefq,ocid1.dynamicgroup.oc1..aaaa... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/oci.mdx | main | vault | [
0.02285362035036087,
0.043353479355573654,
-0.06850679963827133,
0.015896815806627274,
-0.025219541043043137,
-0.0614779070019722,
0.002914103912189603,
0.010515579953789711,
0.03201006352901459,
-0.031899381428956985,
0.039334140717983246,
-0.0606364980340004,
0.05697889253497124,
0.04508... | -0.093804 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.