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 |
|---|---|---|---|---|---|
# IBM Db2 Vault supports IBM Db2 credential management using the LDAP secrets engine. Access to Db2 is managed by facilities that reside outside the Db2 database system. By default, user authentication is completed by a security facility that relies on operating system based authentication of users and passwords. This ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/db2.mdx | main | vault | [
-0.06456918269395828,
-0.06484129279851913,
-0.0673089548945427,
-0.025896241888403893,
-0.030293209478259087,
-0.041452907025814056,
0.022520791739225388,
0.03433806449174881,
0.02103392593562603,
-0.05892277881503105,
0.022997388616204262,
0.02185949869453907,
0.07450089603662491,
-0.040... | 0.043838 |
connect to Db2. Read the rotated password of the LDAP user that was used in the static role. ```shell-session $ vault read ldap/static-cred/static ``` \*\*Successful output:\*\* ```shell-session Key Value --- ----- dn uid=staticuser,ou=users,dc=example,dc=com last\_vault\_rotation 2022-03-14T11:56:15.252772-07:00 passw... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/db2.mdx | main | vault | [
-0.0003643493400886655,
-0.016746776178479195,
-0.10538428276777267,
-0.015444056130945683,
-0.04182547330856323,
-0.01577666960656643,
-0.021209992468357086,
0.052475105971097946,
-0.03078298829495907,
-0.025414925068616867,
0.04991935193538666,
-0.02370457537472248,
0.08573149889707565,
... | -0.100822 |
# Database secrets engine The database secrets engine generates database credentials dynamically based on configured roles. It works with a number of different databases through a plugin interface. There are a number of built-in database types, and an exposed framework for running custom database types for extendabilit... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/index.mdx | main | vault | [
-0.06698805838823318,
-0.039228081703186035,
-0.07093185186386108,
0.006711954716593027,
-0.05095459893345833,
0.007376229856163263,
0.04631105065345764,
-0.042461976408958435,
0.06242777779698372,
-0.041881900280714035,
-0.021568287163972855,
0.08098046481609344,
0.08781153708696365,
0.00... | 0.067707 |
the credential TTL. For more details on rotating root credentials in the DB Secrets engine, refer to the [Rotate Root credentials](/vault/api-docs/secret/databases#rotate-root-credentials) API docs. @include 'rotation-manager-logging.mdx' ## Setup Most secrets engines must be configured in advance before they can perfo... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/index.mdx | main | vault | [
-0.01665370911359787,
-0.03172285482287407,
-0.12059526890516281,
-0.033679939806461334,
-0.08206400275230408,
-0.008119485341012478,
-0.06443347036838531,
0.010710243135690689,
0.056032657623291016,
-0.029186835512518883,
0.04889688268303871,
0.048945117741823196,
0.08811474591493607,
0.0... | -0.100103 |
for the role (or leave blank). - Set the \*\*Rotation period\*\* for the role password. By default, Vault rotates passwords every 24 hours. - If you want to bypass an initial rotation on creation, toggle \*\*Rotate immediately\*\* to off. - For dynamic roles: - Set the TTL and max TTL expiry times. By default, TTL is 1... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/index.mdx | main | vault | [
-0.035515785217285156,
0.039160117506980896,
-0.07675150036811829,
0.021015871316194534,
-0.0806933268904686,
0.03587250038981438,
-0.03308527544140816,
0.007967988029122353,
0.036787454038858414,
-0.03243689611554146,
0.01321942638605833,
0.033688563853502274,
0.09163776785135269,
-0.0040... | -0.083357 |
credential that Vault will generate and make available to database plugins. See the documentation of individual database plugins for the credential types they support and usage examples. ## Onboarding static database users When a static database user is onboarded to the database secrets engine, by default Vault immedia... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/index.mdx | main | vault | [
-0.011092056520283222,
-0.05095073953270912,
-0.10701190680265427,
-0.005812323652207851,
-0.10972962528467178,
0.0069491066969931126,
-0.008991577662527561,
0.029770974069833755,
0.0028514517471194267,
-0.019836431369185448,
-0.014366301707923412,
0.013128777034580708,
0.10808185487985611,
... | -0.0891 |
The default password generation can be represented as the following password policy: ```hcl length = 20 rule "charset" { charset = "abcdefghijklmnopqrstuvwxyz" min-chars = 1 } rule "charset" { charset = "ABCDEFGHIJKLMNOPQRSTUVWXYZ" min-chars = 1 } rule "charset" { charset = "0123456789" min-chars = 1 } rule "charset" {... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/index.mdx | main | vault | [
-0.00558040477335453,
-0.01924309693276882,
-0.10327402502298355,
0.018183421343564987,
-0.1361294835805893,
0.05399118736386299,
-0.032086458057165146,
-0.039463240653276443,
0.044003210961818695,
-0.05024072527885437,
-0.00502954563125968,
0.003561785677447915,
0.1161145567893982,
0.0089... | -0.117429 |
# Custom database secrets engines ~> The interface for custom database plugins has changed in Vault 1.6. Vault will continue to recognize the now deprecated version of this interface for some time. If you are using a plugin with the deprecated interface, you should upgrade to the newest version. See [Upgrading database... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/custom.mdx | main | vault | [
-0.029426584020256996,
-0.0531158372759819,
-0.08059242367744446,
0.008304247632622719,
-0.08281277865171432,
-0.00007708910561632365,
-0.05081062763929367,
-0.0047812373377382755,
-0.0006041369051672518,
-0.004978820215910673,
0.012125704437494278,
0.05097024142742157,
0.04980427399277687,
... | -0.032353 |
helper function located in `sdk/database/helper/dbutil` called `QueryHelper` that assists in doing this string replacement. You are not required to use it, but it will make your plugin's behavior consistent with the built-in plugins. The `InitializeRequest` object contains a map of keys to values. This data is what the... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/custom.mdx | main | vault | [
-0.06302134692668915,
-0.024951910600066185,
-0.10164780914783478,
0.05544504523277283,
-0.0931243821978569,
0.0028698828537017107,
0.019035769626498222,
0.014736047945916653,
-0.007488300558179617,
0.00038889158167876303,
0.04146837443113327,
-0.009298160672187805,
0.0695500448346138,
-0.... | -0.020266 |
like any other: ```shell-session $ vault write database/config/mydatabase \ plugin\_name=mydatabase-database-plugin \ allowed\_roles="readonly" \ myplugins\_connection\_details="..." ``` ## Updating database plugins to leverage plugin versioning @include 'plugin-versioning.mdx' In addition to the `Database` interface a... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/custom.mdx | main | vault | [
0.06876344978809357,
-0.024664390832185745,
-0.08855299651622772,
-0.04942222312092781,
-0.044274166226387024,
-0.016385728493332863,
-0.035968612879514694,
0.006151361856609583,
-0.04314861446619034,
-0.001081287395209074,
0.05285714566707611,
0.0018204995431005955,
0.005790140014141798,
... | -0.02662 |
in the requests or responses. It also simplifies the interface by merging several into a single function call. ### Upgrading your custom database Vault 1.6 supports both version 4 and version 5 database plugins. The support for version 4 plugins will be removed in a future release. Version 5 database plugins will not f... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/custom.mdx | main | vault | [
0.05663365125656128,
-0.037045225501060486,
-0.05226664990186691,
-0.034745462238788605,
-0.005857083946466446,
-0.05876455828547478,
-0.10564293712377548,
-0.04704318195581436,
0.003732373472303152,
-0.024333298206329346,
0.06517899036407471,
0.05547109991312027,
0.0009885237086564302,
-0... | -0.027071 |
the `DeleteUserRequest` object. | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/custom.mdx | main | vault | [
-0.08094128966331482,
-0.022214841097593307,
-0.11694063246250153,
-0.05162273719906807,
-0.055525582283735275,
-0.08461028337478638,
0.11926355957984924,
-0.08399368822574615,
0.06381034851074219,
0.013578154146671295,
-0.0035755194257944822,
0.026855533942580223,
0.02268598973751068,
-0.... | 0.129714 |
# Snowflake database secrets engine Snowflake is disabling password authentication for all users in [November of 2025.](https://www.snowflake.com/en/blog/blocking-single-factor-password-authentification) HashiCorp has added support for key pair authentication in place of passwords, including root-rotation. Snowflake is... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/snowflake.mdx | main | vault | [
-0.02373306266963482,
-0.01800621673464775,
-0.12907247245311737,
-0.008993103168904781,
-0.03672760725021362,
-0.007071162573993206,
-0.05751907452940941,
0.011853575706481934,
-0.012457909993827343,
-0.05059554800391197,
-0.03537077084183693,
0.09132304787635803,
0.0674775093793869,
-0.0... | -0.039643 |
read database/creds/my-password-role Key Value --- ----- lease\_id database/creds/my-password-role/2f6a614c-4aa2-7b19-24b9-ad944a8d4de6 lease\_duration 1h lease\_renewable true password SsnoaA-8Tv4t34f41baD username v\_root\_my\_password\_role\_fU0jqEy4wMNoAY2h60yd\_1610561532 ``` #### Key pair credentials 1. Configure... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/snowflake.mdx | main | vault | [
0.05918068811297417,
-0.005243143532425165,
-0.11366629600524902,
0.016727589070796967,
-0.07092789560556412,
0.016195598989725113,
0.04459260776638985,
0.04950302466750145,
0.004758596420288086,
-0.0097314128652215,
-0.0211415346711874,
-0.05585048720240593,
0.07230249792337418,
0.0324532... | -0.105481 |
# Redshift database secrets engine Redshift is a supported plugin for the database secrets engine. This plugin generates database credentials dynamically based on configured roles for the AWS Redshift database service, and also supports [Static Roles](/vault/docs/secrets/databases#static-roles). See the [database secre... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/redshift.mdx | main | vault | [
-0.01082086656242609,
-0.04381547123193741,
-0.08822587877511978,
0.03207610920071602,
-0.08154016733169556,
-0.006544201169162989,
-0.022391732782125473,
-0.005013872403651476,
-0.0022607226856052876,
-0.05777852237224579,
-0.02637251652777195,
-0.0043071783147752285,
0.09597232937812805,
... | -0.013278 |
# InfluxDB database secrets engine @include 'x509-sha1-deprecation.mdx' InfluxDB is one of the supported plugins for the database secrets engine. This plugin generates database credentials dynamically based on configured roles for the InfluxDB database. See the [database secrets engine](/vault/docs/secrets/databases) d... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/influxdb.mdx | main | vault | [
-0.04382586479187012,
-0.016991084441542625,
-0.07828833907842636,
-0.02567032352089882,
-0.0837186947464943,
-0.03495001420378685,
-0.014518815092742443,
-0.03809550032019615,
0.013479769229888916,
-0.030482087284326553,
-0.04030922055244446,
-0.011209961026906967,
0.14301805198192596,
-0... | -0.059577 |
# Elasticsearch database secrets engine @include 'x509-sha1-deprecation.mdx' Elasticsearch is one of the supported plugins for the database secrets engine. This plugin generates database credentials dynamically based on configured roles for Elasticsearch. See the [database secrets engine](/vault/docs/secrets/databases)... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/elasticdb.mdx | main | vault | [
0.0037301008123904467,
0.025315329432487488,
-0.05695128068327904,
-0.012641314417123795,
-0.07221163809299469,
-0.021240847185254097,
-0.04545557126402855,
-0.03706713393330574,
-0.0002095765812555328,
-0.013816965743899345,
-0.049812719225883484,
-0.00388007122091949,
0.1272609829902649,
... | -0.03139 |
a different path, use the `-path` argument. 1. Configure Vault with the proper plugin and connection information: ```shell-session $ vault write database/config/my-elasticsearch-database \ plugin\_name="elasticsearch-database-plugin" \ allowed\_roles="internally-defined-role,externally-defined-role" \ username=vault \ ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/elasticdb.mdx | main | vault | [
0.05217698588967323,
0.043857771903276443,
-0.06783466786146164,
0.026397040113806725,
-0.047750260680913925,
-0.00226214318536222,
-0.05946137011051178,
0.05585699528455734,
0.03405317664146423,
0.011461986228823662,
-0.04312542453408241,
-0.06592410802841187,
0.08334825187921524,
0.07379... | -0.059593 |
# MongoDB database secrets engine @include 'x509-sha1-deprecation.mdx' @include 'mongodb-ops-manager.mdx' MongoDB is one of the supported plugins for the database secrets engine. This plugin generates database credentials dynamically based on configured roles for the MongoDB database and also supports [Static Roles](/v... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/mongodb.mdx | main | vault | [
-0.020036477595567703,
0.0013520318316295743,
-0.08348295092582703,
0.024510696530342102,
-0.059860844165086746,
-0.020810524001717567,
-0.0590347945690155,
-0.0009990765247493982,
-0.03011048026382923,
-0.014898785389959812,
-0.04711843654513359,
0.007920819334685802,
0.08702407032251358,
... | -0.041687 |
# Couchbase database secrets engine @include 'x509-sha1-deprecation.mdx' Couchbase is one of the supported plugins for the database secrets engine. This plugin generates database credentials dynamically based on configured roles for the Couchbase database. See the [database secrets engine](/vault/docs/secrets/databases... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/couchbase.mdx | main | vault | [
0.00845703762024641,
-0.016283536329865456,
-0.03587371110916138,
-0.04150557518005371,
-0.05216459557414055,
0.03899044916033745,
-0.06919927895069122,
-0.029040036723017693,
0.011757826432585716,
-0.017000114545226097,
-0.04932013526558876,
0.031315963715314865,
0.14606446027755737,
0.01... | -0.100854 |
# MSSQL database secrets engine MSSQL is one of the supported plugins for the database secrets engine. This plugin generates database credentials dynamically based on configured roles for the MSSQL database. See the [database secrets engine](/vault/docs/secrets/databases) docs for more information about setting up the ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/mssql.mdx | main | vault | [
0.000955582654569298,
-0.023370392620563507,
-0.14952996373176575,
0.031025975942611694,
-0.09256020933389664,
0.03809477761387825,
0.003053260501474142,
0.005076308269053698,
-0.014376480132341385,
0.00015522801550105214,
-0.030194707214832306,
-0.033829301595687866,
0.10101653635501862,
... | -0.054943 |
reading from the `/creds` endpoint with the name of the role: ```text $ vault read database/creds/my-role Key Value --- ----- lease\_id database/creds/my-role/2f6a614c-4aa2-7b19-24b9-ad944a8d4de6 lease\_duration 1h lease\_renewable true password wJKpk9kg-T1Ma7qQfS8y username v-vaultuser-my-role-r7kCtKGGr3eYQP1OGR6G-160... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/mssql.mdx | main | vault | [
0.015190364792943,
-0.005753620062023401,
-0.1048414558172226,
-0.0026129179168492556,
-0.081082284450531,
0.03926537558436394,
0.09431667625904083,
-0.017705246806144714,
0.05800600349903107,
0.028882695361971855,
0.0013593494659289718,
-0.02350008673965931,
0.10943716019392014,
0.0642381... | -0.088378 |
# Redis ElastiCache database secrets engine Redis ElastiCache is one of the supported plugins for the database secrets engine. This plugin generates static credentials for existing managed roles. See the [database secrets engine](/vault/docs/secrets/databases) docs for more information about setting up the database sec... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/rediselasticache.mdx | main | vault | [
-0.018186336383223534,
-0.01003055926412344,
-0.13314732909202576,
0.010759936645627022,
-0.0620187483727932,
-0.015322809107601643,
-0.01742323860526085,
-0.011419047601521015,
-0.007291007786989212,
0.004163884557783604,
-0.016796274110674858,
0.005239427089691162,
0.07783067226409912,
0... | 0.000017 |
# Redis database secrets engine Redis is one of the supported plugins for the database secrets engine. This plugin generates database credentials dynamically based on configured roles for the Redis database, and also supports [Static Roles](/vault/docs/secrets/databases#static-roles). See the [database secrets engine](... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/redis.mdx | main | vault | [
-0.023841822519898415,
-0.05863417685031891,
-0.15296627581119537,
0.022849269211292267,
-0.09303946048021317,
-0.02561318315565586,
-0.007589278277009726,
-0.011868438683450222,
-0.03359178453683853,
-0.06946740299463272,
-0.008501404896378517,
0.027372995391488075,
0.1087159663438797,
0.... | -0.020332 |
# Cassandra database secrets engine @include 'x509-sha1-deprecation.mdx' Cassandra is one of the supported plugins for the database secrets engine. This plugin generates database credentials dynamically based on configured roles for the Cassandra database. See the [database secrets engine](/vault/docs/secrets/databases... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/cassandra.mdx | main | vault | [
0.005725243128836155,
0.0031346208415925503,
-0.08286292850971222,
-0.013030704110860825,
-0.1370430290699005,
-0.026320157572627068,
-0.06600707769393921,
-0.00794601533561945,
-0.008852755650877953,
-0.025693444535136223,
-0.045796945691108704,
-0.036596205085515976,
0.1725822538137436,
... | -0.080394 |
# PostgreSQL database secrets engine PostgreSQL is one of the supported plugins for the database secrets engine. This plugin generates database credentials dynamically based on configured roles for the PostgreSQL database, and also supports [Static Roles](/vault/docs/secrets/databases#static-roles). See the [database s... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/postgresql.mdx | main | vault | [
-0.049216460436582565,
-0.020883865654468536,
-0.11408589035272598,
0.035401176661252975,
-0.12758834660053253,
0.01812371425330639,
-0.001208700705319643,
-0.018687892705202103,
0.011496816761791706,
-0.05374583974480629,
-0.0912071168422699,
0.04554133489727974,
0.047990087419748306,
-0.... | -0.056949 |
name of the engine. To enable the secrets engine at a different path, use the `-path` argument. 1. Configure connection to DB without root credentials and enable the rootless workflow by setting the `self\_managed` parameter: ```shell-session $ vault write database/config/my-postgresql-database \ plugin\_name="postgres... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/postgresql.mdx | main | vault | [
0.006700877100229263,
-0.0354451909661293,
-0.09928541630506516,
0.008689182810485363,
-0.08684403449296951,
-0.019661052152514458,
-0.031028086319565773,
0.020181061699986458,
-0.0026005844119936228,
-0.02150815911591053,
-0.04833606630563736,
0.03367520868778229,
0.020630868151783943,
-0... | -0.092777 |
the connection has been configured and IAM authentication is complete, the steps to set up a role and generate credentials are the same as the ones listed above. | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/postgresql.mdx | main | vault | [
-0.02504897117614746,
-0.047247350215911865,
-0.014857818372547626,
-0.012556588277220726,
-0.08777894079685211,
0.04228660836815834,
0.027758844196796417,
-0.1019640564918518,
-0.007528956979513168,
0.06914504617452621,
0.0499698780477047,
-0.08914080262184143,
0.0625309869647026,
0.03268... | 0.070497 |
# HANA database secrets engine HANA is one of the supported plugins for the database secrets engine. This plugin generates database credentials dynamically based on configured roles for the HANA database. See the [database secrets engine](/vault/docs/secrets/databases) docs for more information about setting up the dat... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/hanadb.mdx | main | vault | [
-0.0558570958673954,
-0.04142386093735695,
-0.08040710538625717,
0.014775616116821766,
-0.11695682257413864,
0.04033226519823074,
-0.034827567636966705,
-0.007073245942592621,
-0.05409054085612297,
-0.02872936613857746,
0.023477163165807724,
-0.009420392103493214,
0.07094000279903412,
-0.0... | -0.016607 |
# Oracle database secrets engine -> The Oracle database plugin is now available for use with the database secrets engine for HCP Vault Dedicated on AWS. The plugin configuration (including installation of the Oracle Instant Client library) is managed by HCP. Refer to the HCP Vault Dedicated tab for more information. Th... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/oracle/index.mdx | main | vault | [
-0.06585898250341415,
-0.00467837555333972,
-0.10127163678407669,
-0.021726436913013458,
-0.06535410135984421,
0.030041880905628204,
-0.004654174204915762,
0.030005058273673058,
-0.021767379716038704,
-0.026855196803808212,
-0.010033589787781239,
-0.021235032007098198,
0.07067358493804932,
... | -0.00489 |
capabilities for the plugin binary. 1. Enable the database secrets engine if it is not already enabled: ```shell-session $ vault secrets enable database Success! Enabled the database secrets engine at: database/ ``` By default, the secrets engine will enable at the name of the engine. To enable the secrets engine at a ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/oracle/index.mdx | main | vault | [
0.005573984235525131,
-0.031262654811143875,
-0.10819261521100998,
-0.04327841475605965,
-0.04625751078128815,
-0.02072598598897457,
-0.06450039148330688,
0.016096975654363632,
-0.012571437284350395,
0.0009722778340801597,
0.0241460669785738,
-0.02215876616537571,
0.0313105434179306,
0.052... | -0.091632 |
Configure a static role that creates a dedicated connection to a user in the Oracle database with the `password` parameter. For example: ```shell-session $ vault write database/static-roles/my-role \ db\_name="my-oracle-database" \ username="staticuser" \ password="password" \ rotation\_period="1h" ``` 1. Verify the ne... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/oracle/index.mdx | main | vault | [
0.009083322249352932,
-0.0046325367875397205,
-0.13612277805805206,
-0.004089290741831064,
-0.09985926002264023,
-0.022572265937924385,
0.059325024485588074,
0.010199987329542637,
0.028941811993718147,
-0.0454559363424778,
0.027615632861852646,
-0.021483857184648514,
0.10535107553005219,
0... | -0.066182 |
is deployed on AWS RDS, and uses SSL, see the [connecting with HCP Vault Dedicated using SSL](#connect-with-hcp-vault-using-ssl) example. If the version of Oracle you are using has a container database, you will need to connect to one of the pluggable databases rather than the container database in the `connection\_url... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/oracle/index.mdx | main | vault | [
0.016921522095799446,
0.022441625595092773,
-0.10088472068309784,
-0.055214397609233856,
-0.08719979971647263,
-0.003932260908186436,
-0.025951603427529335,
0.041159067302942276,
0.053896714001894,
-0.0082112280651927,
-0.010014727711677551,
-0.013307778164744377,
0.11827173829078674,
0.02... | -0.120079 |
API](/vault/api-docs/secret/databases) page. | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/oracle/index.mdx | main | vault | [
-0.04483455419540405,
0.03220439329743385,
-0.12881116569042206,
-0.014464359730482101,
0.010331758297979832,
-0.06319382041692734,
-0.027560872957110405,
-0.00640650512650609,
0.01361238956451416,
-0.05391054227948189,
0.027921343222260475,
0.07019630819559097,
0.08260694146156311,
-0.031... | 0.132053 |
# Release notes: Oracle plugin [ce\_repo]: https://github.com/hashicorp/vault-plugin-database-oracle Current version | Edition | Runtime | Code source :------------------: | ---------- | -------- | ----------- `0.13.0` | Enterprise | External | Binary: `vault-plugin-database-oracle\*` `0.10.2` | Community | External | ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/oracle/release-notes.mdx | main | vault | [
0.0032353787682950497,
-0.008257322013378143,
-0.030525069683790207,
-0.07580503076314926,
0.0008409872534684837,
-0.09806609898805618,
-0.04617803543806076,
0.008001435548067093,
-0.05549994856119156,
0.015172787010669708,
0.06679799407720566,
-0.03854851797223091,
-0.022225214168429375,
... | 0.065351 |
# KV secrets engine - version 1 The `kv` secrets engine is used to store arbitrary secrets within the configured physical storage for Vault. Writing to a key in the `kv` backend will replace the old value; sub-fields are not merged together. Key names must always be strings. If you write non-string values directly via ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/kv/kv-v1.mdx | main | vault | [
-0.03315621241927147,
0.055306293070316315,
-0.1339845359325409,
0.01881914585828781,
-0.07499711960554123,
0.012007031589746475,
-0.038251932710409164,
0.033610034734010696,
0.0599873848259449,
-0.044345226138830185,
0.06498727947473526,
-0.048337507992982864,
0.08561292290687561,
-0.0214... | -0.031187 |
# KV secrets engine The `kv` secrets engine is a generic key-value store used to store arbitrary secrets within the configured physical storage for Vault. This secrets engine can run in one of two modes; store a single value for a key, or store a number of versions for each key and maintain the record of them. ## KV ve... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/kv/index.mdx | main | vault | [
-0.03873327746987343,
0.06809037178754807,
-0.04380347207188606,
0.008344942703843117,
0.007340603042393923,
0.004961804021149874,
-0.11528415232896805,
0.01699959672987461,
0.06563639640808105,
-0.05152948945760727,
0.04991818591952324,
0.043199826031923294,
-0.002330778632313013,
-0.0667... | 0.012896 |
# Key/Value v2 plugin The key/value (`kv`) secrets engine stores and versions arbitrary static secrets stored in Vault physical storage. The `kv` v2 plugin uses soft deletes to make data inaccessible while allowing data recovery. When an entry is permanently deleted, Vault purges the underlying version data and marks t... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/kv/kv-v2/index.mdx | main | vault | [
-0.00861175823956728,
0.04130537807941437,
-0.07122091203927994,
-0.00784059427678585,
0.011485499329864979,
-0.020412947982549667,
-0.11321329325437546,
0.00013141993258614093,
0.03340533375740051,
-0.07203620672225952,
0.09353587031364441,
-0.00598605303093791,
0.005268205422908068,
-0.0... | -0.029317 |
# Save random strings to the key/value v2 plugin Use [password policies](/vault/docs/concepts/password-policies) to generate random strings and save the strings to your key/value v2 plugin. ## Before you start - \*\*You must have `read`, `create`, and `update` permission for password policies\*\*. - \*\*You must have `... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/kv/kv-v2/random-string.mdx | main | vault | [
0.006665803492069244,
0.01028645969927311,
-0.0830315500497818,
-0.039420392364263535,
-0.09475559741258621,
0.04567630589008331,
-0.010038593783974648,
-0.0040846350602805614,
0.014650465920567513,
-0.04289230331778526,
0.0228436179459095,
-0.05400089547038078,
0.15267732739448547,
-0.031... | -0.107663 |
\*\*Secret\*\* tab. - Click the eye icon to view the desired key value.  Call the [`/{plugin\_mount\_path}/data/{secret\_path}`](/vault/api-docs/secret/kv/kv-v2#read-secret-version) endpoint ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/kv/kv-v2/random-string.mdx | main | vault | [
0.03554260730743408,
0.08170497417449951,
-0.08069465309381485,
0.017442790791392326,
0.01942518725991249,
-0.02106962352991104,
-0.023723402991890907,
0.04852387681603432,
0.0949716866016388,
-0.02815444953739643,
0.0337141789495945,
-0.07376299053430557,
0.059350885450839996,
0.013800837... | -0.08159 |
# Set up the key/value v2 plugin Use `vault secrets enable` to enable an instance of the `kv` plugin. To specify version 2, use the `-version` flag or specific `kv-v2` as the plugin type: Additionally, when running a dev-mode server, the v2 `kv` secrets engine is enabled by default at the path `demo/` (for non-dev serv... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/kv/kv-v2/setup.mdx | main | vault | [
-0.00908605009317398,
-0.005240944679826498,
-0.10265109688043594,
-0.028837690129876137,
-0.016874676570296288,
-0.0010174637427553535,
-0.1104380190372467,
-0.0059408163651824,
0.015368040651082993,
-0.013885482214391232,
0.0911274179816246,
-0.07057182490825653,
0.03831275552511215,
0.0... | -0.086162 |
the API endpoint path. Escape your policy file and make a `POST` call to [`/sys/policy/{policy\_name}`](/vault/api-docs/system/policy#create-update-policy) with your policy details: ```shell-session $ jq -Rs '{ "policy": . | gsub("[\\r\\n\\t]"; "") }' | curl \ --request POST \ --header "X-Vault-Token: ${VAULT\_TOKEN}" ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/kv/kv-v2/setup.mdx | main | vault | [
0.018848290666937828,
0.09764765948057175,
-0.07057837396860123,
-0.05195903033018112,
-0.03805525228381157,
-0.0076299686916172504,
-0.05056246742606163,
0.03134472668170929,
0.06785259395837784,
0.015246961265802383,
0.008390933275222778,
-0.06032640486955643,
0.06919953972101212,
0.0393... | -0.065562 |
# Upgrade `kv` version 1 plugins You can upgrade existing version 1 key/value stores to version 2 to use versioning. You cannot access v1 plugin mounts during the upgrade, which may take a long time for plugins that contain significant data. ## Before you start - \*\*You must have permission to update ACL policies\*\*.... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/kv/kv-v2/upgrade.mdx | main | vault | [
-0.05195543169975281,
-0.016189880669116974,
-0.05477253347635269,
0.005123084876686335,
-0.04630729928612709,
0.005119364243000746,
-0.1288074105978012,
-0.0036318835336714983,
-0.04002460092306137,
-0.02183176390826702,
0.11062467843294144,
-0.05676441267132759,
0.037264786660671234,
0.0... | -0.073597 |
# Restore soft deleted key/value data You can restore data from soft deletes in the `kv` v2 plugin as long as the `destroyed` metadata field for the targeted version is `false`. - You have [set up a `kv` v2 plugin](/vault/docs/secrets/kv/kv-v2/setup). - Your authentication token has `create` and `update` permissions fo... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/kv/kv-v2/cookbook/undelete-data.mdx | main | vault | [
0.019847525283694267,
0.03230004385113716,
-0.0414615236222744,
0.010618824511766434,
0.002674216404557228,
-0.010720782913267612,
-0.07057704776525497,
-0.01823394000530243,
0.042885154485702515,
-0.0303067397326231,
0.10200432687997818,
-0.008848781697452068,
0.0532730408012867,
0.037876... | -0.06647 |
# Read versioned key/value data Read versioned data from an existing data path in the `kv` v2 plugin. - You have [set up a `kv` v2 plugin](/vault/docs/secrets/kv/kv-v2/setup). - Your authentication token has `read` permissions for the `kv` v2 plugin. Use [`vault kv get`](/vault/docs/command/kv/read) to read \*\*all\*\*... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/kv/kv-v2/cookbook/read-data.mdx | main | vault | [
0.07524779438972473,
0.059584181755781174,
-0.05626834183931351,
-0.016852928325533867,
-0.04758140444755554,
-0.022535834461450577,
-0.049157317727804184,
0.05996141955256462,
0.03335322439670563,
-0.01105287205427885,
0.06553202122449875,
-0.07623263448476791,
0.030127068981528282,
0.042... | -0.079382 |
# Soft delete key/value data Use soft deletes to flag data at a secret path as unavailable while leaving the data recoverable. You can revert soft deletes as long as the `destroyed` field is `false` in the metadata. - You have [set up a `kv` v2 plugin](/vault/docs/secrets/kv/kv-v2/setup). - Your authentication token ha... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/kv/kv-v2/cookbook/delete-data.mdx | main | vault | [
0.03309870883822441,
0.05606615170836449,
-0.0508328452706337,
0.010240035131573677,
-0.005226066801697016,
-0.0291913989931345,
-0.06983533501625061,
-0.024928666651248932,
0.06354384124279022,
-0.019082926213741302,
0.09232652932405472,
-0.005036084447056055,
0.06890912353992462,
0.02932... | -0.07268 |
# Destroy key/value data The standard `vault kv delete` command performs soft deletes. Use the CLI or GUI to permanently delete (destroy) data so Vault purges the underlying data and sets the `destroyed` metadata field to `true`. - You have [set up a `kv` v2 plugin](/vault/docs/secrets/kv/kv-v2/setup). - Your authentic... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/kv/kv-v2/cookbook/destroy-data.mdx | main | vault | [
0.05433114245533943,
0.07568906992673874,
-0.039840180426836014,
-0.03939158469438553,
-0.02082989178597927,
-0.04501626640558243,
-0.060528237372636795,
-0.007593727670609951,
0.05265570804476738,
-0.011650895699858665,
0.060574449598789215,
-0.019163990393280983,
0.07794072479009628,
0.0... | -0.037885 |
# Set max data versions in key/value v2 Limit the number of active versions for a `kv` v2 secret path so Vault permanently deletes (destroys) older data versions automatically. - You have [set up a `kv` v2 plugin](/vault/docs/secrets/kv/kv-v2/setup). - Your authentication token has `create` and `update` permissions for... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/kv/kv-v2/cookbook/max-versions.mdx | main | vault | [
0.06450877338647842,
0.0444561131298542,
-0.03336725011467934,
-0.01644175685942173,
-0.050813060253858566,
-0.011506359092891216,
-0.10606222599744797,
0.0010866824304684997,
0.03147616237401962,
0.0024689596612006426,
0.07502998411655426,
-0.016580205410718918,
0.06237593665719032,
0.052... | -0.061538 |
# Read subkeys for a key/value data path Read the available subkeys on an existing data path in the `kv` v2 plugin. - You have [set up a `kv` v2 plugin](/vault/docs/secrets/kv/kv-v2/setup). - Your authentication token has `read` permissions for subkeys on the target secret path. Use `vault read` with the `/subkeys` pat... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/kv/kv-v2/cookbook/read-subkey.mdx | main | vault | [
0.03611977770924568,
0.037292271852493286,
-0.052234020084142685,
0.004965139087289572,
-0.03693796321749687,
-0.022091340273618698,
-0.02431679144501686,
0.05856702849268913,
0.04146274924278259,
-0.024491071701049805,
0.039716970175504684,
-0.06694528460502625,
0.04909798875451088,
0.022... | -0.012798 |
# Write custom metadata in key/value v2 Write custom metadata to a `kv` v2 secret path. - You have [set up a `kv` v2 plugin](/vault/docs/secrets/kv/kv-v2/setup). - Your authentication token has `create` and `update` permissions for the `kv` v2 plugin. Use [`vault kv metadata put`](/vault/docs/command/kv/metadata) to se... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/kv/kv-v2/cookbook/custom-metadata.mdx | main | vault | [
0.07116450369358063,
0.0332375168800354,
-0.07629271596670151,
-0.013949437998235226,
-0.08648785203695297,
0.0060467165894806385,
-0.06475255638360977,
0.09027348458766937,
0.004216416738927364,
0.006552060600370169,
0.07239352911710739,
-0.10014721006155014,
0.07087182998657227,
0.032629... | -0.038661 |
# Patch versioned key/value data Use the patch process to update specific values or add new key/value pairs to an existing data path in the `kv` v2 plugin. - You have [set up a `kv` v2 plugin](/vault/docs/secrets/kv/kv-v2/setup). - Your authentication token has appropriate permissions for the `kv` v2 plugin: - \*\*`pat... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/kv/kv-v2/cookbook/patch-data.mdx | main | vault | [
0.0018376318039372563,
0.03072681464254856,
-0.029353046789765358,
-0.052370376884937286,
-0.08348743617534637,
-0.011222932487726212,
-0.05943286418914795,
0.03895362839102745,
-0.015361460857093334,
0.004109420347958803,
0.08085400611162186,
-0.06914964318275452,
0.058623578399419785,
-0... | -0.062561 |
# Write new key/value data Write new versions of data to a new or existing data path in the `kv` v2 plugin. - You have [set up a `kv` v2 plugin](/vault/docs/secrets/kv/kv-v2/setup). - Your authentication token has `create` and `update` permissions for the `kv` v2 plugin. The Vault CLI forcibly converts `kv` keys and va... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/kv/kv-v2/cookbook/write-data.mdx | main | vault | [
0.04828546196222305,
0.04804278165102005,
-0.08696725964546204,
0.003432276425883174,
-0.09659039974212646,
0.01990581676363945,
-0.07321038842201233,
0.04820622131228447,
0.036377426236867905,
-0.021675048395991325,
0.08587373793125153,
-0.04627664387226105,
0.06059124320745468,
0.0092137... | -0.060779 |
# Identity secrets engine The identity secrets engine is the identity management solution for Vault. It internally maintains the clients who are recognized by Vault. Each client is internally termed as an `Entity`. An entity can have multiple `Aliases`. For example, a single user who has accounts in both GitHub and LDA... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/identity/index.mdx | main | vault | [
-0.0856253132224083,
-0.04000966250896454,
-0.03711927682161331,
0.02623170241713524,
0.020861009135842323,
-0.02599923685193062,
0.07329540699720383,
-0.016355719417333603,
0.13869920372962952,
-0.0639447495341301,
-0.009118970483541489,
-0.006641389336436987,
0.08233573287725449,
-0.0429... | 0.135131 |
# OIDC identity provider Vault is an OpenID Connect ([OIDC](https://openid.net/specs/openid-connect-core-1\_0.html)) identity provider. This enables client applications that speak the OIDC protocol to leverage Vault's source of [identity](/vault/docs/concepts/identity) and wide range of [authentication methods](/vault/... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/identity/oidc-provider.mdx | main | vault | [
-0.08975936472415924,
0.05044965073466301,
-0.08040153980255127,
0.021505288779735565,
0.017474301159381866,
-0.05517469719052315,
0.047109462320804596,
0.029352273792028427,
0.1001247689127922,
-0.10546880960464478,
-0.03158925101161003,
0.0718092992901802,
0.04005163535475731,
-0.0356861... | 0.08458 |
OIDC authentication methods. This means that they can leverage Vault as a source of identity using the OIDC protocol. See the following links for details on configuring OIDC authentication for other HashiCorp products: - [Boundary](/boundary/tutorials/access-management/oidc-auth) - [Consul](/consul/docs/security/acl/au... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/identity/oidc-provider.mdx | main | vault | [
-0.04699070006608963,
0.0496065616607666,
-0.13328686356544495,
0.009471011348068714,
0.034075167030096054,
-0.08330512046813965,
0.01064218021929264,
0.04919949546456337,
0.07613864541053772,
-0.09237788617610931,
0.019801178947091103,
0.03903503343462944,
0.028098730370402336,
-0.0197956... | 0.065799 |
# Identity tokens Identity information is used throughout Vault, but it can also be exported for use by other applications. An authorized user/application can request a token that encapsulates identity information for their associated entity. These tokens are signed JWTs following the [OIDC ID token](https://openid.net... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/identity/identity-token.mdx | main | vault | [
-0.07978680729866028,
0.04498787596821785,
-0.045048125088214874,
0.006551820319145918,
0.07491152733564377,
-0.044831834733486176,
0.04785911738872528,
0.03475406393408775,
0.11716262251138687,
-0.09396886080503464,
-0.03328050300478935,
0.06287551671266556,
0.02450341172516346,
-0.057891... | 0.134164 |
would be merged with the base OIDC claims into the final token: ```json { "iss": "https://10.1.1.45:8200/v1/identity/oidc", "sub": "a2cd63d3-5364-406f-980e-8d71bb0692f5", "aud": "SxSouteCYPBoaTFy94hFghmekos", "iat": 1561411915, "exp": 1561412215, "color": "green", "userinfo": { "username": "bob", "groups": ["web", "eng... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/identity/identity-token.mdx | main | vault | [
-0.0994780883193016,
0.08949141949415207,
-0.010114341042935848,
0.04059341177344322,
0.0568324439227581,
-0.037115465849637985,
0.016317037865519524,
0.03476595878601074,
0.07519487291574478,
-0.043020036071538925,
0.01449273619800806,
-0.025319717824459076,
-0.02235051803290844,
-0.02269... | 0.074918 |
has one configurable parameter: issuer. The issuer `iss` claim is particularly important for proper validation of the token by clients, and special consideration should be given when using Identity Tokens with [performance replication](/vault/docs/enterprise/replication). Consumers of the token will request public keys... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/identity/identity-token.mdx | main | vault | [
-0.01275204960256815,
0.013859922997653484,
-0.09118752926588058,
0.0203324593603611,
-0.01593676209449768,
-0.06601210683584213,
-0.020396821200847626,
-0.003175091464072466,
0.05496567487716675,
-0.04743766784667969,
0.021550888195633888,
0.00835222378373146,
0.10747472941875458,
0.03750... | 0.040169 |
# Fix different-case entity alias duplicates Fix duplicate identities for entity aliases due to case differences. \*\*You must review different-case entity alias duplicates before enabling forced identity deduplication due to the potential security risk of incorrectly merging distinct aliases\*\*. - You are running Vau... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/identity/deduplication/different-case.mdx | main | vault | [
0.0025225593708455563,
-0.0007649417384527624,
0.048980917781591415,
-0.043885163962841034,
-0.013142365962266922,
-0.09747029095888138,
0.016654524952173233,
-0.008585464209318161,
0.07823513448238373,
-0.045078158378601074,
0.07834212481975555,
0.00039340549847111106,
0.05819748714566231,
... | -0.071359 |
duplicates so the final entry has the union of all permissions granted to the duplicates. We recommend confirming the expected merge behavior \*\*before\*\* enabling deduplication by reviewing the `force\_deduplication` label in the log line to: 1. confirm the identified duplicates are all mergeable. 1. confirm permiss... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/identity/deduplication/different-case.mdx | main | vault | [
-0.015041481703519821,
-0.029419083148241043,
0.013860463164746761,
-0.08028117567300797,
-0.04966142773628235,
-0.06580592691898346,
0.017742767930030823,
-0.028331555426120758,
0.08201678097248077,
-0.06615939736366272,
0.050487641245126724,
0.03722099959850311,
0.06058952584862709,
0.02... | -0.084379 |
# Find and resolve duplicate Vault identities Bugs in Vault versions before 1.19 might lead to duplicate [identities](/vault/docs/concepts/identity) for entities, aliases, and groups. Duplicate identities in the persistent storage of a Vault cluster can cause unexpected behavior as duplicate identities are outside typi... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/identity/deduplication/index.mdx | main | vault | [
0.004570275079458952,
-0.01829957589507103,
0.002604765584692359,
-0.004539342597126961,
0.022107888013124466,
-0.08543777465820312,
-0.043512891978025436,
-0.0699552670121193,
0.07050003856420517,
-0.031029216945171356,
0.06079818680882454,
-0.012790625914931297,
0.06921948492527008,
0.02... | -0.040187 |
fi done < unseal-process.log # Save the rename target information to files for further processing root\_ns="root/" for name in "${!rename\_targets[@]}" do echo ${name//"${root\_ns}"/""} >> rename-targets.txt echo ${rename\_targets["${name}"]} >> rename-details.txt done ``` ## Step 3: Resolve any duplicates If you \*\*d... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/identity/deduplication/index.mdx | main | vault | [
0.018025018274784088,
-0.05063921958208084,
0.0418153814971447,
0.0004868171236012131,
0.041725341230630875,
-0.08271031081676483,
0.03269026800990105,
-0.05552651733160019,
0.048645827919244766,
0.06407388299703598,
0.052107397466897964,
-0.019481761381030083,
0.037424828857183456,
-0.023... | 0.057502 |
# Fix entity and group duplicates Fix duplicate identities for entities and groups targeted for renaming. - You are running Vault 1.19 or later. - You have [deduplication \*\*renaming\*\* targets in your system logs](/vault/docs/upgrading/identity-deduplication). - You have admin permission on the relevant Vault server... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/identity/deduplication/entity-group.mdx | main | vault | [
-0.01529249269515276,
-0.020225847139954567,
0.005547399166971445,
-0.024876218289136887,
-0.03350624814629555,
-0.10672038048505783,
-0.005169151816517115,
-0.0935208797454834,
0.13170833885669708,
-0.03180067613720894,
0.05814289301633835,
0.0004708411288447678,
0.06576930731534958,
-0.0... | -0.076711 |
`sYMXY/entity-case-d82231d2-3716-6b9c-e80d-7d09c0409739` Group | `root/group-case` | Unchanged Group | `root/group-cAsE` | `group-cAsE-9fe86ea0-f80c-1131-5be1-1d6e3b70237f` Group | `root/group-case` | `group-case-32dd070c-c1f8-c796-9a71-15887014b813` Group | `sYMXY/group-case` | Unchanged Group | `sYMXY/group-case` | `... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/identity/deduplication/entity-group.mdx | main | vault | [
-0.022990604862570763,
-0.005205168388783932,
-0.05697011575102806,
-0.0636388510465622,
-0.02583935484290123,
0.010479144752025604,
0.027495358139276505,
-0.038561806082725525,
0.03703145310282707,
0.014950473792850971,
0.12069900333881378,
-0.03332224488258362,
0.03594634309411049,
0.002... | 0.050825 |
# Resolve deduplication impact on ACL policy templates Fix templated ACL policy behavior for entities and groups renamed during identity deduplication. - You are running Vault 1.19 or later. - You have [deduplication \*\*renaming\*\* targets in your system logs](/vault/docs/upgrading/identity-deduplication). - You have... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/identity/deduplication/acl-policy-templates.mdx | main | vault | [
-0.06074941158294678,
0.04526115581393242,
0.010957562364637852,
0.006772142369300127,
0.027067366987466812,
-0.073114313185215,
0.04027977213263512,
-0.08325904607772827,
0.13001850247383118,
-0.03879315406084061,
0.06214355304837227,
0.022824302315711975,
0.05182269588112831,
0.023141909... | -0.052458 |
of policies and template keys against the list of deduplication targets identified in your system logs to determine if the policy will break after duplication. If you identify policies that may break during deduplication, consult with the relevant teams to determine if the policies are still used and if you should addr... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/identity/deduplication/acl-policy-templates.mdx | main | vault | [
-0.05781945586204529,
0.04971202835440636,
0.030319958925247192,
0.00845652911812067,
-0.009560798294842243,
-0.0006489473744295537,
0.05876285582780838,
-0.05429374799132347,
0.03185589239001274,
0.047195348888635635,
0.05798058584332466,
0.012624172493815422,
0.01049375906586647,
-0.0477... | -0.040304 |
templatized ACL policy file that replaces the entity name reference with a reference to the metadata field. For example: ```hcl path "kv/users/{{identity.entity.metadata.old\_name}}/\*" { capabilities = ["read", "create", "update"] } ``` 1. Escape your policy file and make a `POST` call to the [`{namespace}/sys/policy/... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/identity/deduplication/acl-policy-templates.mdx | main | vault | [
-0.0002063232968794182,
0.09803925454616547,
-0.0813089981675148,
-0.038554321974515915,
-0.04040702432394028,
-0.01961863599717617,
0.018837768584489822,
0.014975951053202152,
0.0611233189702034,
0.013950454071164131,
0.007002532482147217,
-0.08320118486881256,
0.09531129896640778,
-0.000... | -0.045468 |
# Resolve deduplication impact on Terraform resource references Fix external reference behavior in Terraform configuration files for entities and groups renamed during identity deduplication. - You are running Vault 1.19 or later. - You have [deduplication \*\*renaming\*\* targets in your system logs](/vault/docs/upgra... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/identity/deduplication/terraform-refs.mdx | main | vault | [
-0.03333074599504471,
0.010173562914133072,
0.030545886605978012,
0.002822142792865634,
0.02290051244199276,
-0.09787483513355255,
0.04492366313934326,
-0.10585951060056686,
0.09064393490552902,
0.019358232617378235,
0.03351086750626564,
-0.0542355552315712,
0.08345610648393631,
-0.0025798... | -0.001592 |
# LDAP secrets engine overview Manage static and dynamic LDAP credentials and integrate with services that implement the LDAP v3 protocol, including OpenLDAP, Active Directory, and IBM Resource Access Control Facility (RACF). Current version | Edition | Runtime | Code source --------------- | --------- | -------- | ---... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/ldap/index.mdx | main | vault | [
-0.02023296244442463,
-0.052553579211235046,
-0.14819589257240295,
-0.025148293003439903,
-0.03984822705388069,
0.0001960206573130563,
-0.023282619193196297,
0.07008036971092224,
-0.07521174103021622,
-0.03625887632369995,
0.035666003823280334,
0.023305227980017662,
0.03732115030288696,
-0... | 0.074624 |
IBM RACF](/vault/docs/secrets/ldap/ibm-racf) - [Use dynamic credentials](/vault/docs/secrets/ldap/dynamic-credentials) - [Check out service accounts](/vault/docs/secrets/ldap/cookbook/account-library/checkout) Short explanations for common problems: - Manage root credentials - [Manually rotate root credentials](/vault/... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/ldap/index.mdx | main | vault | [
-0.04145704582333565,
-0.036713991314172745,
-0.14751508831977844,
-0.01278455276042223,
-0.015326838940382004,
-0.015956321731209755,
-0.03697754070162773,
0.023697523400187492,
-0.03214015066623688,
-0.027685806155204773,
0.06709977239370346,
0.045353371649980545,
0.07299361377954483,
0.... | -0.027962 |
# Manage IBM RACF LDAP credentials Use the LDAP plugin with IBM Resource Access Control Facility (RACF) mainframe security systems to manage authentication and access control in enterprise environments. ## Before you start - \*\*Check your Vault permissions\*\*. You must have permission to enable and configure plugins ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/ldap/ibm-racf.mdx | main | vault | [
-0.03525562211871147,
-0.04459736496210098,
-0.12832428514957428,
-0.04024752229452133,
-0.02346234954893589,
0.025749288499355316,
0.03600635752081871,
0.07046078890562057,
-0.007868831977248192,
-0.019374730065464973,
-0.011943159624934196,
0.029423171654343605,
0.08529789000749588,
0.00... | 0.003996 |
# Create a service account library Create a library of service accounts that users and machines can check out as needed. Vault automatically rotates the account password when clients return the service account to the library. ## Before you start - \*\*Check your Vault permissions\*\*. You must have permission to enable... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/ldap/account-library.mdx | main | vault | [
-0.019044747576117516,
-0.04025396704673767,
-0.10547880083322525,
-0.052322618663311005,
-0.07748246192932129,
0.010072113014757633,
0.003220858285203576,
0.02350269816815853,
-0.001723764929920435,
-0.022724246606230736,
0.005078768823295832,
0.03560388460755348,
0.09296616166830063,
0.0... | -0.100095 |
# Use dynamic credentials with LDAP Use dynamic LDAP credentials and manage LDAP user accounts through LDIF. ## Before you start - \*\*Check your Vault permissions\*\*. You must have permission to enable and configure plugins in Vault. - \*\*You must have an LDAP plugin configured for OpenLDAP or Active Directory\*\*. ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/ldap/dynamic-credentials.mdx | main | vault | [
0.07466588914394379,
-0.036097534000873566,
-0.08019368350505829,
-0.03644895553588867,
-0.05849669501185417,
0.012461534701287746,
-0.00784158706665039,
0.03869963064789772,
-0.029808402061462402,
-0.038162704557180405,
0.012957781553268433,
-0.024987587705254555,
0.06744380295276642,
0.0... | -0.131775 |
# Set up the LDAP secrets plugin Enable and configure an instance of the `ldap` plugin to use with OpenLDAP or Active Directory. ## Before you start - \*\*Check your Vault permissions\*\*. You must have permission to enable and configure plugins in Vault. - \*\*Create an LDAP account for Vault\*\*. We highly recommend ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/ldap/setup.mdx | main | vault | [
0.03201599791646004,
-0.023517264053225517,
-0.09871446341276169,
-0.024809934198856354,
-0.038827139884233475,
0.0013273884542286396,
-0.028071612119674683,
0.03191400319337845,
-0.03859615698456764,
-0.03643498942255974,
-0.0008456798386760056,
0.018923182040452957,
0.09495647996664047,
... | -0.098956 |
# Hash LDAP passwords The LDAP secret engine does not hash or encrypt passwords before modifying values in LDAP, which can lead to plaintext passwords on your LDAP server. - You have permission to update your LDAP server. - You know the data information tree (DIT) assocaited with your `ldap` plugin. We recommend config... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/ldap/cookbook/hash-passwords.mdx | main | vault | [
-0.013626880012452602,
0.020418480038642883,
-0.05391829460859299,
0.024694640189409256,
-0.003354731248691678,
-0.04467539116740227,
0.003009614534676075,
0.013502240180969238,
0.015720807015895844,
-0.0008818329079076648,
0.014157280325889587,
0.014904813840985298,
-0.03829437121748924,
... | -0.073919 |
# Extend a service account lease The LDAP secrets plugin lets clients extend the lease for checked out service accounts as long as the renewal does not violate the maximum TTL of the service account. - You have [set up an `ldap` plugin](/vault/docs/secrets/ldap/setup). - You have [created an LDAP account library](/vaul... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/ldap/cookbook/account-library/extend-lease.mdx | main | vault | [
-0.015149715356528759,
-0.011544089764356613,
-0.04743344709277153,
-0.06929653882980347,
-0.052016716450452805,
-0.02411855384707451,
0.020253973081707954,
-0.029782161116600037,
-0.01215238869190216,
0.0020978974644094706,
0.049077801406383514,
0.08640415966510773,
0.07513446360826492,
0... | -0.093437 |
# Rotate root LDAP credentials on a schedule @include 'alerts/enterprise-only.mdx' You can set the `rotation\_schedule` parameter with an optional rotation window in your LDAP configuration to rotate root credentials on a fixed schedule. If you set the rotation window, Vault stops trying to rotate the credential once t... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/ldap/cookbook/root-credentials/schedule-based-rotation.mdx | main | vault | [
0.02562027983367443,
-0.010343410074710846,
-0.07562144845724106,
-0.03765252232551575,
-0.05676191672682762,
-0.01740245521068573,
-0.04709672927856445,
-0.011231822893023491,
0.061556488275527954,
-0.026168063282966614,
0.029658421874046326,
0.06625393778085709,
0.08453214913606644,
0.03... | -0.133297 |
# Disable LDAP root credential rotation You can temporarily disable root rotation with the [`disable\_automated\_rotation`](/vault/api-docs/secret/ldap#disable\_automated\_rotation) paramter in your plugin configuration. If you use `rotation\_period`, disabling rotation also resets the credential TTL. - You have [set u... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/ldap/cookbook/root-credentials/disable-root-rotation.mdx | main | vault | [
-0.019970320165157318,
0.006557992659509182,
-0.09710536152124405,
-0.055646393448114395,
-0.0837174728512764,
-0.031225033104419708,
-0.08341078460216522,
-0.030433915555477142,
0.04034904018044472,
-0.02362988516688347,
0.0791829526424408,
0.06272975355386734,
0.07436724007129669,
0.0137... | -0.124859 |
# Create static LDAP roles Configure static roles to map names in Vault to LDAP entries and use the rotation settings to manage credentials automatically with the role. - You have [set up an `ldap` plugin](/vault/docs/secrets/ldap/setup). - You have permission to update roles in Vault. - You have permission to make `PO... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/ldap/cookbook/static-credentials/create-static-roles.mdx | main | vault | [
0.023088203743100166,
-0.03082852065563202,
-0.11649652570486069,
-0.06513429433107376,
-0.09891226887702942,
-0.015366582199931145,
-0.02945679984986782,
0.02132970280945301,
-0.04735960438847542,
-0.033323947340250015,
0.012799824588000774,
-0.01533176563680172,
0.14623038470745087,
0.04... | -0.138334 |
# Delete static LDAP roles Vault does not rotate passwords when you delete a static role. We recommend manually rotating the mapped credentials before deleting the role or revoking access to the static role. - You have [set up an `ldap` plugin](/vault/docs/secrets/ldap/setup). - You have permission to update roles in V... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/ldap/cookbook/static-credentials/delete-static-roles.mdx | main | vault | [
-0.012599051930010319,
-0.01123252883553505,
-0.06835004687309265,
-0.04743090644478798,
-0.059688664972782135,
-0.020642515271902084,
0.006061607506126165,
-0.071525938808918,
0.02285822667181492,
-0.01302600558847189,
0.04812265560030937,
0.0165864285081625,
0.13708078861236572,
0.046556... | -0.139542 |
# Transit secrets engine The transit secrets engine handles cryptographic functions on data in-transit. Vault doesn't store the data sent to the secrets engine. It can also be viewed as "cryptography as a service" or "encryption as a service". The transit secrets engine can also sign and verify data; generate hashes an... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/transit/index.mdx | main | vault | [
-0.06691692769527435,
-0.0121547169983387,
0.011967121623456478,
0.01684407703578472,
0.00568773178383708,
-0.01976337470114231,
-0.007509041577577591,
-0.03857937827706337,
0.09462767094373703,
-0.0378604456782341,
0.0037676473148167133,
0.09923814982175827,
0.03434300422668457,
-0.073450... | 0.073348 |
derivation, and convergent encryption - `ed25519`: Ed25519; supports signing, signature verification, and key derivation - `ecdsa-p256`: ECDSA using curve P-256; supports signing and signature verification - `ecdsa-p384`: ECDSA using curve P-384; supports signing and signature verification - `ecdsa-p521`: ECDSA using c... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/transit/index.mdx | main | vault | [
-0.06908212602138519,
0.0032119983807206154,
-0.06570505350828171,
-0.04967483505606651,
0.04154444485902786,
-0.03406303748488426,
0.004591330420225859,
0.06027962267398834,
0.0013105878606438637,
0.005209690425544977,
0.04544805362820625,
0.02423665300011635,
0.08007511496543884,
-0.0247... | 0.099685 |
operation to a new key version; existing values can then be rewrapped against the new key version and will use the version 3 algorithm. - Version 3 uses a different algorithm designed to be resistant to offline plaintext-confirmation attacks. It is similar to AES-SIV in that it uses a PRF to generate the nonce from the... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/transit/index.mdx | main | vault | [
0.0046492465771734715,
-0.02396344393491745,
-0.041497793048620224,
0.018317360430955887,
-0.00004030054697068408,
-0.026292040944099426,
-0.0387701690196991,
-0.03102736547589302,
0.02848007157444954,
-0.05598888918757439,
0.040746863931417465,
0.01927424967288971,
0.036670129746198654,
-... | 0.021002 |
encryptions will use this new key. Old data can still be decrypted due to the use of a key ring. 1. Upgrade already-encrypted data to a new key. Vault will decrypt the value using the appropriate key in the keyring and then encrypt the resulting plaintext with the newest key in the keyring. ```text $ vault write transi... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/transit/index.mdx | main | vault | [
-0.01118806004524231,
0.011838765814900398,
-0.011743154376745224,
0.013951650820672512,
0.01475825347006321,
-0.06257173418998718,
-0.023775964975357056,
-0.062304671853780746,
0.06969330459833145,
0.024691203609108925,
0.027171796187758446,
0.09111136943101883,
0.05669408664107323,
-0.01... | -0.07875 |
Tutorial Refer to the [Encryption as a Service: Transit Secrets Engine](/vault/tutorials/encryption-as-a-service/eaas-transit) tutorial to learn how to use the transit secrets engine to handle cryptographic functions on data in-transit. ## API The Transit secrets engine has a full HTTP API. Please see the [Transit secr... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/transit/index.mdx | main | vault | [
-0.06478408724069595,
-0.0012632067082449794,
-0.06223718076944351,
0.02058238722383976,
-0.026813749223947525,
-0.06558762490749359,
-0.032544203102588654,
-0.016151664778590202,
-0.016814682632684708,
-0.03536278381943703,
-0.01491644699126482,
0.034922175109386444,
0.04135790839791298,
... | 0.127234 |
# Key wrapping for transit key import The "bring your own key" (BYOK) functionality for the transit secrets engine allows users to import keys that were generated outside of Vault into the transit secrets engine. This document describes the process for wrapping an externally-generated key (the target key) for import in... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/transit/key-wrapping-guide.mdx | main | vault | [
0.008040322922170162,
0.03663889318704605,
-0.06247740238904953,
0.010879646055400372,
-0.004921223036944866,
-0.017849141731858253,
0.016055777668952942,
0.04041919857263565,
-0.012518537230789661,
-0.010440338402986526,
0.06203710287809372,
0.029552286490797997,
0.0444447286427021,
-0.02... | 0.044568 |
This involves creating a new RSA public key object with the key returned by transit's `wrapping\_key` endpoint. ```shell-session $ importPubKey -f wrapping\_key.pem -l "vault-transit-wrapping-key" ``` This will create the public key in the HSM with all of the necessary permissions. If you're using a different tool, mak... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/transit/key-wrapping-guide.mdx | main | vault | [
0.03786233067512512,
0.02846190333366394,
-0.10148341208696365,
0.0053360057063400745,
-0.015907764434814453,
0.030376138165593147,
-0.022836783900856972,
-0.017361776903271675,
-0.005796200130134821,
0.05327674746513367,
0.04547416418790817,
-0.04880695044994354,
0.06809946894645691,
-0.0... | -0.060695 |
# Key management secrets engine @include 'alerts/enterprise-and-hcp.mdx' Key management secrets engine requires [Vault Enterprise](https://www.hashicorp.com/products/vault/pricing) with the Advanced Data Protection (ADP) module. The key management secrets engine provides a consistent workflow for distribution and lifec... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/key-management/index.mdx | main | vault | [
-0.035228192806243896,
0.04979817569255829,
-0.03485996276140213,
-0.04769949987530708,
0.02034061774611473,
-0.04906735196709633,
0.04688192903995514,
-0.039219990372657776,
0.0463995561003685,
-0.01367871928960085,
0.03596309572458267,
0.07766410708427429,
0.08917244523763657,
-0.0860707... | 0.152761 |
the key has. If a timeout occurs when distributing a key to a KMS provider, you may need to increase the [VAULT\_CLIENT\_TIMEOUT](/vault/docs/commands#vault\_client\_timeout). 1. Rotate a key: ```shell-session $ vault write -f keymgmt/key/example-key/rotate ``` Rotating a key creates a new key version that contains new... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/key-management/index.mdx | main | vault | [
0.056461483240127563,
0.08764547854661942,
0.00995679572224617,
-0.022878674790263176,
-0.0275993961840868,
-0.003150892909616232,
-0.04536198452115059,
-0.04256116971373558,
0.07122247666120529,
0.058822184801101685,
0.04001360014081001,
0.03523659706115723,
0.10045187175273895,
-0.068987... | -0.040694 |
# AWS KMS @include 'alerts/enterprise-and-hcp.mdx' AWS KMS secrets engine requires [Vault Enterprise](https://www.hashicorp.com/products/vault/pricing) with the Advanced Data Protection (ADP) module. The Key Management secrets engine supports lifecycle management of keys in [AWS KMS](https://aws.amazon.com/kms/) region... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/key-management/awskms.mdx | main | vault | [
-0.002587618539109826,
0.09408025443553925,
-0.04424899443984032,
-0.04590412229299545,
-0.011054017581045628,
-0.008836330845952034,
0.006307038478553295,
-0.03322422876954079,
0.029928475618362427,
0.01737077720463276,
0.007856519892811775,
-0.0346638448536396,
0.11320164799690247,
-0.05... | 0.031318 |
# Azure Key Vault The key management secrets engine supports lifecycle management of keys in named [Azure Key Vault](https://docs.microsoft.com/en-us/azure/key-vault/) instances. This is accomplished by configuring a KMS provider resource with the `azurekeyvault` provider and other provider-specific parameter values. T... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/key-management/azurekeyvault/index.mdx | main | vault | [
-0.028164176270365715,
0.019572755321860313,
-0.03821972385048866,
-0.03272881731390953,
-0.06419160962104797,
0.014118922874331474,
0.006614357233047485,
-0.050794824957847595,
0.07639632374048233,
0.0694139376282692,
0.00450214883312583,
-0.039272528141736984,
0.13744047284126282,
0.0367... | -0.061413 |
# Setup guide - Azure Key Vault To manage the lifecycle of the Azure Key Vault keys, you need to setup the key management secrets engine using `azurekeyvault` provider. ## Setup 1. Enable the key management secrets engine. ```shell-session $ vault secrets enable keymgmt Success! Enabled the keymgmt secrets engine at: k... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/key-management/azurekeyvault/setup.mdx | main | vault | [
0.019073471426963806,
0.03689119219779968,
-0.048969779163599014,
0.016257695853710175,
-0.09668423235416412,
0.025578752160072327,
0.026125064119696617,
-0.04275260493159294,
0.04426845163106918,
0.09970028698444366,
0.044027164578437805,
-0.03486604988574982,
0.13589350879192352,
-0.0329... | -0.063902 |
DNS](https://docs.microsoft.com/en-us/azure/dns/private-dns-overview) integration. From the host that Vault is running on, follow the steps in [Validate that the private link connection works](https://docs.microsoft.com/en-us/azure/key-vault/general/private-link-service?tabs=portal#validate-that-the-private-link-connec... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/key-management/azurekeyvault/setup.mdx | main | vault | [
-0.012567948549985886,
0.012282527051866055,
-0.046841610223054886,
-0.002232000231742859,
-0.05460742861032486,
-0.0112750343978405,
-0.041528861969709396,
-0.07171498239040375,
0.08885814994573593,
0.045090001076459885,
0.0025417425204068422,
0.017282500863075256,
0.06099608540534973,
0.... | -0.042717 |
# GCP Cloud KMS The key management secrets engine supports lifecycle management of keys in GCP Cloud KMS [key rings](https://cloud.google.com/kms/docs/resource-hierarchy#key\_rings). This is accomplished by configuring a KMS provider resource with the `gcpckms` provider and other provider-specific parameter values. The... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/key-management/gcpkms/index.mdx | main | vault | [
-0.0757361426949501,
0.012786516919732094,
-0.0012843675212934613,
-0.06591320782899857,
-0.06773623824119568,
-0.02899155020713806,
0.020038990303874016,
-0.03478023409843445,
0.015545731410384178,
0.007009964436292648,
0.01456992607563734,
-0.031019851565361023,
0.10644270479679108,
-0.0... | -0.051043 |
# Setup guide - GCP Cloud KMS To manage the lifecycle of the GCP Cloud KMS key rings, you need to setup the key management secrets engine using `gcpckms` provider. ## Setup 1. Enable the key management secrets engine. ```shell-session $ vault secrets enable keymgmt ``` 1. Configure the KMS provider resource named, `exa... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/key-management/gcpkms/setup.mdx | main | vault | [
0.0002567008777987212,
0.010591840371489525,
-0.020639920607209206,
-0.03056487813591957,
-0.08981069922447205,
-0.009400409646332264,
0.03320043906569481,
-0.005611651577055454,
0.03582599014043808,
0.05600236728787422,
0.014864242635667324,
-0.02387363277375698,
0.09480166435241699,
-0.0... | -0.050997 |
# SSH secrets engine The Vault SSH secrets engine provides secure authentication and authorization for access to machines via the SSH protocol. The Vault SSH secrets engine helps manage access to machine infrastructure, providing several ways to issue SSH credentials. The Vault SSH secrets engine supports the following... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/ssh/index.mdx | main | vault | [
-0.024110889062285423,
0.08297008275985718,
-0.04243415594100952,
0.011633011512458324,
-0.019263556227087975,
-0.00812594499439001,
-0.07687373459339142,
-0.02547713927924633,
0.02616328001022339,
-0.0665867030620575,
0.008198929019272327,
0.06827457994222641,
0.02869250997900963,
-0.0037... | -0.028224 |
# One-time SSH passwords The One-Time SSH Password (OTP) SSH secrets engine type allows a Vault server to issue a one-time password every time a client wants to SSH into a remote host using a helper command on the remote host to perform verification. An authenticated client requests credentials from the Vault server an... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/ssh/one-time-ssh-passwords.mdx | main | vault | [
0.00013727720943279564,
0.03671257942914963,
-0.023250538855791092,
0.0021168652456253767,
0.012101673521101475,
-0.014883752912282944,
-0.012737181037664413,
-0.06115860864520073,
0.11452686786651611,
-0.06078808754682541,
0.0018835122464224696,
0.043610360473394394,
0.03176279738545418,
... | -0.002638 |
# Signed SSH certificates The signed SSH certificates is the simplest and most powerful in terms of setup complexity and in terms of being platform agnostic. By leveraging Vault's powerful CA capabilities and functionality built into OpenSSH, clients can SSH into target hosts using their own local SSH keys. When using ... | 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.007435219828039408,
0.03847029060125351,
-0.028639744967222214,
-0.01592148467898369,
-0.052026066929101944,
-0.006010477896779776,
-0.02052968181669712,
0.034565843641757965,
0.02311069518327713,
-0.07558528333902359,
0.0004688880580943078,
-0.016502296552062035,
0.09723784774541855,
0... | 0.036457 |
as part of the certificate request to the Vault server. This may have significant impact on third-party systems that rely on an `extensions` field for security-critical information. In those cases, consider using a template to specify default extensions, and explicitly setting `"allowed\_extensions"` to an arbitrary, n... | 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.11477868258953094,
0.09402100741863251,
-0.04170997068285942,
0.008078859187662601,
0.02993072383105755,
-0.061461515724658966,
-0.037062425166368484,
0.010441201739013195,
0.02190515212714672,
-0.08486389368772507,
0.05960053578019142,
-0.02638138271868229,
0.07341795414686203,
0.089498... | -0.108007 |
vault write ssh-host-signer/config/ca \ private\_key="..." \ public\_key="..." ``` Regardless of whether it is generated or uploaded, the host signer public key is accessible via the API at the `/public\_key` endpoint. 1. Extend host key certificate TTLs. ```text $ vault secrets tune -max-lease-ttl=87600h ssh-host-sign... | 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.1319279819726944,
0.04292943328619003,
-0.09905826300382614,
-0.005546934902667999,
-0.017408527433872223,
-0.06288028508424759,
-0.08553074300289154,
0.003408040152862668,
0.020081112161278725,
0.010037921369075775,
-0.013458591885864735,
-0.041332732886075974,
0.08925656229257584,
0.05... | -0.110605 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.