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 |
|---|---|---|---|---|---|
request to Vault. For example: ```sh POST http://127.0.0.1/v1/auth/oci/login/devrole "request\_headers": { "date": ["Fri, 22 Aug 2019 21:02:19 GMT"], "(request-target)": ["get /v1/auth/oci/login/devrole"], "host": ["127.0.0.1"], "content-type": ["application/json"], "authorization": ["Signature algorithm=\"rsa-sha256\"... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/oci.mdx | main | vault | [
0.022849129512906075,
0.07114908844232559,
-0.0977102592587471,
-0.0513584278523922,
-0.00758315809071064,
-0.10565681010484695,
-0.05762634798884392,
-0.010148914530873299,
0.04207959771156311,
-0.028552968055009842,
-0.02012484334409237,
0.000007546298547822516,
0.05402910336852074,
0.01... | -0.06727 |
# Google Cloud auth method The `gcp` auth method allows Google Cloud Platform entities to authenticate to Vault. Vault treats Google Cloud as a trusted third party and verifies authenticating entities against the Google Cloud APIs. This backend allows for authentication of: - Google Cloud IAM service accounts - Google ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/gcp.mdx | main | vault | [
-0.09194072335958481,
0.0007728405180387199,
0.03345786780118942,
-0.09547877311706543,
-0.012647620402276516,
-0.033067211508750916,
0.030773520469665527,
-0.036132898181676865,
0.015711629763245583,
-0.009660136885941029,
0.01794241927564144,
-0.041871871799230576,
0.03986375033855438,
-... | -0.026969 |
ensures that GCP can fetch JWKS [public keys](/vault/api-docs/secret/identity/tokens#read-active-public-keys) and verify the plugin identity token signature. 1. Create a named role: For an `iam`-type role: ```shell-session $ vault write auth/gcp/role/my-iam-role \ type="iam" \ policies="dev,prod" \ bound\_service\_acco... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/gcp.mdx | main | vault | [
-0.04025031253695488,
0.040753792971372604,
-0.018153443932533264,
-0.03710608556866646,
-0.0364900603890419,
-0.05009519308805466,
0.08601135015487671,
0.002226751996204257,
0.04694988951086998,
0.036980040371418,
-0.010683564469218254,
-0.08750133961439133,
0.08752883225679398,
0.0070505... | -0.031584 |
[plugin identity token issuer](/vault/api-docs/secret/identity/tokens#read-plugin-workload-identity-issuer-s-openid-configuration). If there is a trust relationship configured between Vault and GCP through [workload identity federation](https://cloud.google.com/iam/docs/workload-identity-federation), the auth method ca... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/gcp.mdx | main | vault | [
-0.07588516920804977,
-0.0009779860265552998,
-0.00029729597736150026,
-0.003132106736302376,
-0.023737989366054535,
-0.029683997854590416,
0.039331063628196716,
-0.007701469585299492,
0.03782396391034126,
0.05543035641312599,
0.010701039806008339,
-0.0073806107975542545,
0.04875131323933601... | 0.035362 |
aliases can aid in building reusable policies since they are available as interpolated values in Vault's policy engine. Once enabled, the auth response will include the following aliases: ```json [ "project-$PROJECT\_ID", "folder-$SUBFOLDER\_ID", "folder-$FOLDER\_ID", "organization-$ORG\_ID" ] ``` If you are using a cu... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/gcp.mdx | main | vault | [
-0.046549540013074875,
0.026163112372159958,
0.035180822014808655,
-0.060313284397125244,
-0.004828045144677162,
-0.019578738138079643,
0.05674028769135475,
-0.02942120097577572,
0.058917250484228134,
-0.021975789219141006,
-0.02916819602251053,
-0.009174593724310398,
0.10464564710855484,
... | -0.058302 |
error: `Expiration date must be set to no more that 15 mins in JWT\_CLAIM, otherwise the login request returns error "role requires that service account JWTs expire within 900 seconds`. In this case, the user must create a new signed JWT with a shorter expiration, or set `max\_jwt\_exp` to a higher value in the gcp rol... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/gcp.mdx | main | vault | [
-0.0701708123087883,
0.03734058886766434,
0.08183011412620544,
-0.023474011570215225,
0.03461938351392746,
-0.050321295857429504,
-0.021465370431542397,
0.008203035220503807,
0.05954205244779587,
-0.026425719261169434,
-0.006789038889110088,
-0.03701771795749664,
0.06252891570329666,
-0.02... | -0.091039 |
response did not return client token") } // get secret from the default mount path for KV v2 in dev mode, "secret" secret, err := client.KVv2("secret").Get(context.Background(), "creds") if err != nil { return "", fmt.Errorf("unable to read secret: %w", err) } // data map can contain more than one key-value pair, // in... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/gcp.mdx | main | vault | [
-0.04137224331498146,
0.0670129656791687,
-0.00602719746530056,
-0.03013291023671627,
-0.032181400805711746,
-0.07737372070550919,
-0.02759457565844059,
0.1051906943321228,
0.0071543012745678425,
-0.031870678067207336,
0.06046697869896889,
-0.10265736281871796,
0.07734611630439758,
-0.0085... | -0.06664 |
# AWS auth method @include 'x509-sha1-deprecation.mdx' The `aws` auth method provides an automated mechanism to retrieve a Vault token for IAM principals and AWS EC2 instances. Unlike most Vault auth methods, this method does not require manual first-deploying, or provisioning security-sensitive credentials (tokens, us... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/aws.mdx | main | vault | [
-0.006080238614231348,
0.059369660913944244,
-0.04446166381239891,
-0.07696167379617691,
-0.008136903867125511,
-0.027447160333395004,
0.05410117283463478,
0.006849926430732012,
0.10821382701396942,
-0.008313007652759552,
-0.046417638659477234,
-0.021019360050559044,
0.10255342721939087,
-... | 0.059475 |
Vault further requires that this header be one of the headers included in the AWS signature and relies upon AWS to authenticate that signature. While AWS API endpoints support both signed GET and POST requests, for simplicity, the aws auth method supports only POST requests. It also does not support `presigned` request... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/aws.mdx | main | vault | [
-0.010360022075474262,
0.10667545348405838,
-0.06948282569646835,
-0.02850642055273056,
0.00279601919464767,
-0.02318919636309147,
-0.007649248465895653,
0.011064773425459862,
0.07683539390563965,
0.004456432070583105,
-0.0396609827876091,
-0.030488286167383194,
0.08642546832561493,
0.0151... | -0.078159 |
must have an ARN that matches one of the ARNs bound to the role they are attempting to login to. The bound ARN allows specifying a wildcard at the end of the bound ARN. For example, if the bound ARN were `arn:aws:iam::123456789012:\*` it would allow any principal in AWS account 123456789012 to login to it. Similarly, i... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/aws.mdx | main | vault | [
0.012641087174415588,
0.006772052496671677,
-0.030326632782816887,
-0.036981407552957535,
-0.0364348441362381,
-0.027423547580838203,
0.06617337465286255,
-0.05332782864570618,
0.046291109174489975,
-0.030173787847161293,
-0.02629111520946026,
-0.04212335869669914,
0.04310495778918266,
0.0... | 0.023205 |
an instance profile, the corresponding role's trust policy specifies that the principal `"Service": "ec2.amazonaws.com"` is trusted to call AssumeRole. When this is configured, EC2 calls AssumeRole on behalf of your instance, with a RoleSessionName corresponding to the instance's instance ID. Thus, it is possible for V... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/aws.mdx | main | vault | [
0.004437325522303581,
0.05439881980419159,
-0.043036434799432755,
-0.011350581422448158,
0.04003482311964035,
-0.04258667677640915,
0.04821871966123581,
-0.025094512850046158,
0.04497542232275009,
-0.08918120712041855,
-0.01792084239423275,
-0.03490779176354408,
0.13318751752376556,
0.0066... | -0.050539 |
value (via the role\_tag feature). - The iam auth method authenticates AWS IAM principals. This can include IAM users, IAM roles assumed from other accounts, AWS Lambdas that are launched in an IAM role, or even EC2 instances that are launched in an IAM instance profile. However, because it authenticates more generaliz... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/aws.mdx | main | vault | [
0.0051497421227395535,
0.07486321777105331,
-0.0476812943816185,
-0.018920211121439934,
0.03200925514101982,
-0.045311737805604935,
0.06129786744713783,
0.006084366701543331,
0.11235542595386505,
-0.02056133933365345,
0.006764818914234638,
-0.05792529135942459,
0.10766200721263885,
-0.0247... | 0.048089 |
"iam:CreateAccessKey", "iam:DeleteAccessKey", "iam:GetAccessKeyLastUsed", "iam:GetUser", "iam:ListAccessKeys", "iam:UpdateAccessKey" ], "Resource": "arn:aws:iam::\*:user/${aws:username}" } ] } ``` Here are some of the scenarios in which Vault would need to use each of these permissions. This isn't intended to be an exh... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/aws.mdx | main | vault | [
0.03146263584494591,
0.046135276556015015,
-0.07099278271198273,
-0.03333168849349022,
0.007605940103530884,
-0.07355442643165588,
0.024923348799347878,
-0.017028169706463814,
0.08638596534729004,
-0.03076624497771263,
0.003510471200570464,
-0.06424185633659363,
0.0989789366722107,
0.00578... | 0.031311 |
auth engine to use plugin WIF: 1. Ensure that Vault [openid-configuration](/vault/api-docs/secret/identity/tokens#read-plugin-identity-token-issuer-s-openid-configuration) and [public JWKS](/vault/api-docs/secret/identity/tokens#read-plugin-identity-token-issuer-s-public-jwks) APIs are network-reachable by AWS. We reco... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/aws.mdx | main | vault | [
-0.041238874197006226,
0.051149435341358185,
-0.08231418579816818,
0.015672994777560234,
0.0121062733232975,
-0.051561854779720306,
-0.029484422877430916,
-0.002411046763882041,
0.09609091281890869,
-0.009228031150996685,
-0.034058548510074615,
-0.015085912309587002,
0.07799088209867477,
-... | -0.013514 |
correctly with respect to the nonce; if the client stores the nonce on disk it can survive reboots, but could also give access to other users or applications on the instance. It is also up to the operator to ensure that client nonces are in fact unique; sharing nonces allows a compromise of the nonce value to enable an... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/aws.mdx | main | vault | [
-0.04729905724525452,
0.04714643210172653,
-0.030246742069721222,
-0.053312189877033234,
-0.010784374549984932,
-0.015166710130870342,
0.017195018008351326,
0.013312768191099167,
0.10849134624004364,
-0.05418705567717552,
-0.00044645313755609095,
0.05761796608567238,
0.04070419445633888,
-... | 0.036825 |
only the `default` policy; by default, this policy allows only manipulation (revocation, renewal, lookup) of the existing token, plus access to its [cubbyhole](/vault/docs/secrets/cubbyhole). This can be useful to allow instances access to a secure "scratch space" for storing data (via the token's cubbyhole) but withou... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/aws.mdx | main | vault | [
-0.004060759209096432,
0.0763084664940834,
-0.009273560717701912,
0.02559971995651722,
0.026918867602944374,
-0.02520640566945076,
-0.015554131008684635,
-0.03715139999985695,
0.13104663789272308,
-0.02049781009554863,
-0.010833235457539558,
0.015026897192001343,
0.07994365692138672,
-0.06... | 0.029028 |
is desired, `disallow\_reauthentication` should be set explicitly on the role or on the role tag. The `disallow\_reauthentication` option is set per-role, and can also be specified in a role tag. Since role tags can only restrict behavior, if the option is set to `false` on the role, a value of `true` in the role tag t... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/aws.mdx | main | vault | [
-0.013778257183730602,
0.10204823315143585,
0.03371891379356384,
-0.008170388638973236,
0.06763391941785812,
-0.030899524688720703,
0.09285576641559601,
-0.04675447195768356,
0.028809785842895508,
-0.040185846388339996,
0.0704578161239624,
-0.029610536992549896,
0.08843060582876205,
0.0393... | -0.001302 |
be aware of such events. The token issued will still be valid, until it expires. The token will likely be expired sooner than its lifetime when the instance fails to renew the token on time. ### Cross account access To allow Vault to authenticate IAM principals and EC2 instances in other accounts, Vault supports using ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/aws.mdx | main | vault | [
0.03820083290338516,
-0.006547688972204924,
-0.00891989003866911,
-0.02324884943664074,
-0.009268736466765404,
-0.012016145512461662,
-0.00860755518078804,
-0.0006990960682742298,
0.048120271414518356,
-0.018038956448435783,
-0.0008115911623463035,
-0.022314654663205147,
0.08691191673278809,... | 0.008513 |
so: ```shell-session $ vault login -method=aws region=us-west-2 role=dev-role-iam ``` If the region is specified as `auto`, the Vault CLI will determine the region based on standard AWS credentials precedence as described earlier. Whichever method is used, be sure the designated region corresponds to that of the STS en... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/aws.mdx | main | vault | [
0.10277353972196579,
0.04740490764379501,
-0.04591676965355873,
-0.0970628634095192,
-0.06767022609710693,
-0.05281677842140198,
0.019874509423971176,
-0.032688725739717484,
0.05216169357299805,
0.0245036780834198,
-0.027491729706525803,
-0.11281311511993408,
0.04947289079427719,
0.0577821... | -0.060159 |
than one key-value pair, // in this case we're just grabbing one of them value, ok := secret.Data["password"].(string) if !ok { return "", fmt.Errorf("value type assertion failed: %T %#v", secret.Data["password"], secret.Data["password"]) } return value, nil } ``` ```cs using System; using System.Text; using Amazon.Run... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/aws.mdx | main | vault | [
0.001946361269801855,
0.0762510672211647,
-0.1146344467997551,
-0.018102264031767845,
0.009884616360068321,
0.01840784214437008,
0.03916110098361969,
0.038192857056856155,
0.09041190892457962,
0.01641070656478405,
0.04143552482128143,
-0.08620460331439972,
0.1152302622795105,
-0.0121601773... | -0.02822 |
# GitHub auth method @include 'tips/custom-authn.mdx' The `github` auth method can be used to authenticate with Vault using a GitHub personal access token. This method of authentication is most useful for humans: operators or developers using Vault directly via the CLI. ~> \*\*IMPORTANT NOTE:\*\* Vault does not support... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/github.mdx | main | vault | [
-0.015720177441835403,
-0.007269728928804398,
-0.09803707897663116,
-0.04767683520913124,
-0.025125080719590187,
-0.0403628870844841,
0.038466811180114746,
0.04196261242032051,
0.05649319291114807,
-0.05345750227570534,
-0.01812400296330452,
0.052218854427337646,
0.10747220367193222,
-0.02... | 0.040267 |
# RADIUS auth method @include 'tips/custom-authn.mdx' The `radius` auth method allows users to authenticate with Vault using an existing RADIUS server that accepts the PAP authentication scheme. ## Authentication The default path is `/radius`. If this auth method was enabled at a different path, specify `-path=/my-path... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/radius.mdx | main | vault | [
0.03871401026844978,
0.05642511695623398,
-0.137761190533638,
-0.027352238073945045,
-0.004177118185907602,
-0.06342712789773941,
-0.007151468191295862,
0.02498529478907585,
0.04735209047794342,
-0.004749821498990059,
0.021975049749016762,
-0.006600498221814632,
0.06448908895254135,
0.0546... | -0.07515 |
# Kerberos auth method @include 'x509-sha1-deprecation.mdx' The `kerberos` auth method provides an automated mechanism to retrieve a Vault token for Kerberos entities. [Kerberos](https://web.mit.edu/kerberos/) is a network authentication protocol invented by MIT in the 1980s. Its name is inspired by Cerberus, the three... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/kerberos.mdx | main | vault | [
-0.06341063976287842,
0.02724193036556244,
-0.06690265983343124,
-0.12054862827062607,
-0.04614869877696037,
-0.060686659067869186,
0.042545147240161896,
-0.01502204593271017,
0.07786164432764053,
0.02433348260819912,
-0.0034097214229404926,
0.044695548713207245,
0.0562099814414978,
-0.007... | 0.16527 |
Since this is identical to the LDAP auth method, see [Group Membership Resolution](/vault/docs/auth/ldap#group-membership-resolution) and [LDAP Group -> Policy Mapping](/vault/docs/auth/ldap#ldap-group-policy-mapping) for further discussion. ```shell-session $ vault write auth/kerberos/groups/engineering-team \ policie... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/kerberos.mdx | main | vault | [
0.028012452647089958,
0.0724470391869545,
-0.03223341330885887,
-0.06393326073884964,
-0.03347178176045418,
-0.037983059883117676,
0.0538187250494957,
-0.08096683025360107,
0.0023712667170912027,
0.003852368565276265,
-0.0062310886569321156,
-0.04086165502667427,
0.08642062544822693,
-0.00... | -0.063944 |
code](https://github.com/hashicorp/vault-plugin-auth-kerberos) The Vault Kerberos library has a working integration test environment that can be referenced as an example of a full Kerberos and LDAP environment. It runs through Docker and can be started through either one of the following commands: ```shell-session $ ma... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/kerberos.mdx | main | vault | [
0.001742558553814888,
0.04211907833814621,
-0.08139834553003311,
-0.05815933644771576,
-0.0515991635620594,
-0.14374001324176788,
-0.05659136548638344,
0.006659030914306641,
0.000364379258826375,
0.018453184515237808,
0.005329855252057314,
-0.05441245436668396,
0.0357494056224823,
-0.01267... | 0.039137 |
# Token auth method @include 'tips/custom-authn.mdx' ~> \*\*NOTE:\*\* The Token auth method cannot be configured with Vault's built-in [Login MFA](/vault/docs/auth/login-mfa) feature. The `token` auth method is built-in and automatically available at `/auth/token`. It allows users to authenticate using a token, as well... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/token.mdx | main | vault | [
-0.0014607449993491173,
0.03656560927629471,
-0.07046540826559067,
-0.036389291286468506,
-0.013218077830970287,
-0.02060660533607006,
0.023719195276498795,
0.008696629665791988,
0.049836523830890656,
-0.03122100979089737,
0.007166247349232435,
0.005457636434584856,
0.08733779191970825,
0.... | 0.019818 |
# Auth methods Auth methods are the components in Vault that perform authentication and are responsible for assigning identity and a set of policies to a user. In all cases, Vault will enforce authentication as part of the request processing. In most cases, Vault will delegate the authentication administration and deci... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/index.mdx | main | vault | [
0.020399916917085648,
0.04064201936125755,
-0.07625765353441238,
-0.06967321783304214,
-0.004159912001341581,
-0.014842339791357517,
0.02208147943019867,
-0.02204158715903759,
0.08750061690807343,
-0.022474128752946854,
0.014408694580197334,
0.06815347075462341,
0.041013967245817184,
-0.01... | 0.061478 |
# Kubernetes auth method @include 'x509-sha1-deprecation.mdx' The `kubernetes` auth method can be used to authenticate with Vault using a Kubernetes Service Account Token. This method of authentication makes it easy to introduce a Vault token into a Kubernetes Pod. You can also use a Kubernetes Service Account Token to... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/kubernetes.mdx | main | vault | [
0.003969745244830847,
0.026460900902748108,
0.03150460869073868,
-0.0940568596124649,
-0.022075699642300606,
-0.02923286333680153,
0.003995642531663179,
0.004637467209249735,
0.0808282271027565,
-0.0007274716044776142,
-0.03646993637084961,
-0.008155325427651405,
0.07980681210756302,
0.008... | 0.018854 |
and Vault will no longer be able to use the `TokenReview` API. See [How to work with short-lived Kubernetes tokens][short-lived-tokens] below for details on handling this change. In response to the issuer changes, Kubernetes auth has been updated in Vault 1.9.0 to not validate the issuer by default. The Kubernetes API ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/kubernetes.mdx | main | vault | [
0.028732920065522194,
-0.00977396871894598,
0.043494272977113724,
-0.028044020757079124,
-0.008706431835889816,
-0.017220282927155495,
-0.03896871209144592,
-0.0029207465704530478,
0.05821847543120384,
0.009901629760861397,
-0.012333851307630539,
-0.0006652671145275235,
0.06542382389307022,
... | -0.039092 |
to maintain the cluster role bindings on the set of service accounts you want to be able to authenticate with Vault. Each client of Vault would need the `system:auth-delegator` ClusterRole: ```shell-session $ kubectl create clusterrolebinding vault-client-auth-delegator \ --clusterrole=system:auth-delegator \ --group=g... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/kubernetes.mdx | main | vault | [
-0.02974148653447628,
0.030784672126173973,
-0.03937595337629318,
0.004219686146825552,
-0.04063896834850311,
0.019124122336506844,
0.02082502469420433,
-0.024990210309624672,
0.06887723505496979,
0.002523883944377303,
-0.021956531330943108,
-0.08741602301597595,
0.0802537277340889,
-0.012... | 0.054936 |
with JWT for the service account, Vault renders the alias metadata as `env : demo/app`. #### Create a templated ACL policy The `env-tmpl` policy lets applications read their secrets defined in KV v2 secret engine. Use the mount accessor value (`auth\_kubernetes\_bcecb1e1`) from the [`sys/auth`](/vault/api-docs/system/a... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/kubernetes.mdx | main | vault | [
0.010976012796163559,
0.07084555178880692,
-0.074403315782547,
-0.05994359031319618,
-0.04058295115828514,
-0.03264032304286957,
-0.01979779452085495,
0.07475420832633972,
0.1037539690732956,
-0.062472447752952576,
-0.009451504796743393,
-0.11922180652618408,
0.05285437032580376,
0.0080975... | 0.008763 |
# TLS certificates auth method @include 'x509-sha1-deprecation.mdx' The `cert` auth method allows authentication using SSL/TLS client certificates which are either signed by a CA or self-signed. SSL/TLS client certificates are defined as having an `ExtKeyUsage` extension with the usage set to either `ClientAuth` or `An... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/cert.mdx | main | vault | [
0.006213645916432142,
0.0952080562710762,
-0.023803893476724625,
-0.059010010212659836,
-0.0312582291662693,
-0.07342419773340225,
-0.009533930569887161,
0.00934232771396637,
0.07666026055812836,
-0.05469348281621933,
0.032789863646030426,
0.013648553751409054,
0.16211843490600586,
0.05828... | -0.131432 |
the client authentication certificate. This can be omitted if the CA used to issue the Vault server certificate is trusted by the local system executing this command. ```shell-session $ vault login \ -method=cert \ -ca-cert=vault-ca.pem \ -client-cert=cert.pem \ -client-key=key.pem \ name=web ``` ### Via the API The en... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/cert.mdx | main | vault | [
0.031135763972997665,
0.10586390644311905,
-0.08030767738819122,
-0.033003583550453186,
-0.023903880268335342,
-0.06352958083152771,
-0.004083145409822464,
-0.029797879979014397,
0.10801395028829575,
0.0010943043744191527,
0.017740463837981224,
-0.05539662390947342,
0.09128445386886597,
0.... | -0.098644 |
# AliCloud auth method The `alicloud` auth method provides an automated mechanism to retrieve a Vault token for AliCloud entities. Unlike most Vault auth methods, this method does not require manual first-deploying, or provisioning security-sensitive credentials (tokens, username/password, client certificates, etc), by... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/alicloud.mdx | main | vault | [
-0.052258510142564774,
-0.0017424979014322162,
-0.07632652670145035,
-0.0532282292842865,
-0.06020694226026535,
-0.026349587365984917,
0.05261560156941414,
-0.0010668712202459574,
0.08356232196092606,
-0.036592721939086914,
-0.026480544358491898,
-0.005928813945502043,
0.08336573094129562,
... | 0.07134 |
the `login` method can be found found in the [Vault CLI source code](https://github.com/hashicorp/vault-plugin-auth-alicloud/blob/master/tools/tools.go). ## API The AliCloud auth method has a full HTTP API. Please see the [AliCloud Auth API](/vault/api-docs/auth/alicloud) for more details. | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/alicloud.mdx | main | vault | [
0.016746483743190765,
0.03117821365594864,
-0.1191401407122612,
-0.06510670483112335,
0.000333059870172292,
-0.044669169932603836,
-0.007912631146609783,
-0.025250324979424477,
0.06879246234893799,
-0.014678901992738247,
0.029512183740735054,
0.037367258220911026,
0.03726888447999954,
0.00... | -0.009985 |
# SPIFFE auth method @include 'alerts/enterprise-only.mdx' The `spiffe` auth method lets you configure authentication using JWT or x.509 based SPIFFE SVIDs whose trust can be rooted within a configured trust bundle. To use the SPIFFE plugin with x.509 SPIFFE IDs, you must have `tls\_disable` and `tls\_disable\_client\_... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/spiffe.mdx | main | vault | [
-0.017682421952486038,
0.015559944324195385,
-0.10049942135810852,
-0.03108220174908638,
0.015148445963859558,
-0.019838333129882812,
0.01020379364490509,
-0.013810226693749428,
-0.010275124572217464,
-0.09032149612903595,
0.015769993886351585,
-0.034720584750175476,
0.10936484485864639,
0... | -0.078745 |
your Vault listener](/vault/docs/configuration/listener/tcp#tcp-listener-parameters) to accept the header provided by the frontend. 1. Ensure your frontend performs full TLS verification to the client to provide proper authentication security. 1. Ensure a secure connection between your frontend and Vault, ideally with ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/spiffe.mdx | main | vault | [
0.017158418893814087,
0.09816499799489975,
-0.07021532207727432,
-0.05396281182765961,
-0.000528147560544312,
-0.08485305309295654,
-0.03366567939519882,
-0.009088132530450821,
0.04477101191878319,
-0.07744492590427399,
-0.046255629509687424,
-0.04038378223776817,
0.04401334747672081,
0.02... | -0.11527 |
# Cloud Foundry (CF) auth method @include 'x509-sha1-deprecation.mdx' The `cf` auth method provides an automated mechanism to retrieve a Vault token for CF instances. It leverages CF's [App and Container Identity Assurance](https://content.pivotal.io/blog/new-in-pcf-2-1-app-container-identity-assurance-via-automatic-ce... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/cf.mdx | main | vault | [
-0.001174745848402381,
0.0050173415802419186,
-0.03197583556175232,
-0.0472114123404026,
0.04401535540819168,
-0.03862899914383888,
-0.023226916790008545,
-0.014891528524458408,
0.06091131269931793,
-0.02292620576918125,
-0.008273385465145111,
-0.05875145643949509,
0.0928298756480217,
-0.0... | -0.079893 |
(0x2) Serial Number: 3e:a4:f2:d6:ab:df:1c:d1:15:bb:1b:25:f6:5d:60:95:8f:39:39 Signature Algorithm: sha256WithRSAEncryption Issuer: CN=Diego Instance Identity Root CA Validity Not Before: Jun 6 09:12:01 2019 GMT Not After : Jun 5 09:12:01 2022 GMT Subject: CN=Diego Instance Identity Root CA Subject Public Key Info: Publ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/cf.mdx | main | vault | [
0.01070369966328144,
0.01992732100188732,
-0.07234030216932297,
-0.12045564502477646,
0.0033754792530089617,
-0.05124244466423988,
-0.06387656182050705,
0.00264759105630219,
0.034414105117321014,
0.007915130816400051,
0.038110341876745224,
-0.03961712494492531,
0.029748909175395966,
-0.057... | 0.075106 |
by a certificate authority trusted by the CF API. Obtaining such a certificate depends on the specifics of your deployment of Cloud Foundry. ### Maintenance In testing we found that CF instance identity CA certificates were set to expire in 3 years. Some CF docs indicate they expire every 4 years. However long they las... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/cf.mdx | main | vault | [
0.0030507433693856,
0.018444303423166275,
-0.03447085991501808,
-0.020565934479236603,
-0.0009680036455392838,
-0.012964613735675812,
-0.03828238695859909,
-0.013438256457448006,
0.07915659248828888,
-0.017044980078935623,
-0.00784263201057911,
-0.08259492367506027,
0.0756063237786293,
0.0... | -0.100909 |
# Azure auth method The `azure` auth method allows authentication against Vault using Azure Active Directory credentials. It treats Azure as a Trusted Third Party and expects a [JSON Web Token (JWT)](https://tools.ietf.org/html/rfc7519) signed by Azure Active Directory for the configured tenant. This method supports au... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/azure.mdx | main | vault | [
-0.012372951954603195,
0.034828849136829376,
-0.06833795458078384,
0.013243178837001324,
0.008203595876693726,
-0.03517156466841698,
0.02633882686495781,
-0.03028472326695919,
0.07190306484699249,
0.051371559500694275,
0.020496049895882607,
0.02089002914726734,
0.10483753681182861,
0.06697... | -0.009559 |
rotation in Azure: | Permission Name | Type | | ----------------------------- | ----------- | | Application.ReadWrite.All | Application | ## Authentication ### Via the CLI The default path is `/auth/azure`. If this auth method was enabled at a different path, specify `auth/my-path/login` instead. ```shell-session $ vau... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/azure.mdx | main | vault | [
-0.0014008552534505725,
0.01768888346850872,
-0.07453137636184692,
-0.02629498951137066,
-0.03730976581573486,
-0.005417665932327509,
0.028991300612688065,
-0.05673959106206894,
0.045928508043289185,
0.031286537647247314,
0.037181608378887177,
-0.038433726876974106,
0.11722216010093689,
0.... | -0.074771 |
specify either `bound\_service\_principal\_ids` or `bound\_group\_ids` to restrict which Azure identities (service principals or group members) can authenticate to this role. Here's an alternative example using `bound\_group\_ids`: ```shell-session $ vault write auth/azure/role/prod-role \ policies="prod" \ bound\_subs... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/azure.mdx | main | vault | [
0.006280397530645132,
0.055938463658094406,
-0.06822661310434341,
-0.016582179814577103,
-0.016891930252313614,
-0.002044098451733589,
0.05008626729249954,
-0.06249647215008736,
0.058047469705343246,
0.03732507675886154,
-0.00017716782167553902,
-0.030036870390176773,
0.10283762961626053,
... | -0.093628 |
is signed internally by Vault's [plugin identity token issuer](/vault/api-docs/secret/identity/tokens#read-plugin-workload-identity-issuer-s-openid-configuration). If there is a trust relationship configured between Vault and Azure through [workload identity federation](https://learn.microsoft.com/en-us/entra/workload-... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/azure.mdx | main | vault | [
-0.023148074746131897,
0.03105533868074417,
-0.06496437638998032,
0.017112134024500847,
0.006072663702070713,
-0.043393827974796295,
0.03638308122754097,
-0.005711471661925316,
0.11950276046991348,
0.04168274253606796,
-0.013156549073755741,
0.03890134021639824,
0.05052804574370384,
0.1031... | 0.012732 |
secret: %w", err) } // data map can contain more than one key-value pair, // in this case we're just grabbing one of them value, ok := secret.Data["password"].(string) if !ok { return "", fmt.Errorf("value type assertion failed: %T %#v", secret.Data["password"], secret.Data["password"]) } return value, nil } ``` ```cs ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/azure.mdx | main | vault | [
0.009045551531016827,
0.11206762492656708,
-0.10619429498910904,
0.016732104122638702,
-0.04486343637108803,
-0.001978600164875388,
0.0826006829738617,
0.0017256718128919601,
0.038380976766347885,
0.06755338609218597,
0.05883941799402237,
-0.07354672253131866,
0.13004247844219208,
0.026342... | -0.050641 |
# Okta auth method @include 'tips/custom-authn.mdx' The `okta` auth method allows authentication using Okta and user/password credentials. This allows Vault to be integrated into environments using Okta. The mapping of groups in Okta to Vault policies is managed by using the [users](/vault/api-docs/auth/okta#register-u... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/okta.mdx | main | vault | [
0.01553250476717949,
0.07925386726856232,
-0.060228381305933,
-0.04874429479241371,
-0.07552974671125412,
-0.06966650485992432,
0.0001417529274476692,
-0.0021598346065729856,
0.05503753945231438,
0.002028802875429392,
0.028657719492912292,
-0.048748791217803955,
0.0448431521654129,
0.06089... | -0.053089 |
Groups](https://developer.okta.com/docs/reference/api/users/#get-user-s-groups) APIs to authenticate users and obtain their group membership. The [`api\_token`](/vault/api-docs/auth/okta#api\_token) provided to the auth method's configuration must have sufficient privileges to exercise these Okta APIs. It is recommende... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/okta.mdx | main | vault | [
-0.0016244567232206464,
0.07488390058279037,
-0.012339923530817032,
0.028388187289237976,
-0.05896986275911331,
-0.06336957216262817,
-0.012053737416863441,
0.013482152484357357,
0.016884148120880127,
-0.003950675018131733,
0.007767830975353718,
-0.007890532724559307,
0.055019721388816833,
... | -0.008888 |
# SCEP auth method @include 'alerts/enterprise-only.mdx' The SCEP authentication method controls static challenges and Intune authentication methods for clients using the SCEP protocol within given PKI mounts. ## Authentication Do not use the SCEP plugin directly. SCEP mount paths only support [delegated authentication... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/scep.mdx | main | vault | [
0.009910420514643192,
0.0570245198905468,
-0.05308311805129051,
-0.029270300641655922,
0.07551690936088562,
-0.033419735729694366,
0.0016216340009123087,
0.004213743843138218,
-0.009200257249176502,
-0.04699985310435295,
-0.006013928446918726,
-0.006515996530652046,
0.09592199325561523,
0.... | 0.013249 |
# LDAP auth method @include 'tips/custom-authn.mdx' @include 'x509-sha1-deprecation.mdx' The `ldap` auth method allows authentication using an existing LDAP server and user/password credentials. This allows Vault to be integrated into environments using LDAP without duplicating the user/pass configuration in multiple p... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/ldap.mdx | main | vault | [
-0.02971710078418255,
-0.03536232188344002,
-0.04886070638895035,
-0.043263718485832214,
-0.054368339478969574,
-0.017810845747590065,
0.06376495957374573,
-0.014752734452486038,
0.015523918904364109,
-0.06181751564145088,
0.01895342580974102,
0.06126732751727104,
0.08577528595924377,
-0.0... | -0.034868 |
required for Active Directory. ### Binding parameters The LDAP auth method supports the following methods for resolving the user object used to authenticate the end user: - \*\*Search\*\* - Searches the LDAP server directory for the user object based on the provided username. Vault can search in two ways: - Authenticat... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/ldap.mdx | main | vault | [
-0.052534639835357666,
-0.02791796624660492,
-0.10219844430685043,
0.005433481186628342,
-0.08197560161352158,
-0.00617165258154273,
0.029910016804933548,
-0.0025597787462174892,
-0.001073047169484198,
-0.0647568553686142,
0.017862601205706596,
0.02287714183330536,
0.0535011887550354,
-0.0... | -0.035686 |
to establish new LDAP connections to the configured server address. ### Group membership resolution Once a user has been authenticated, the LDAP auth method must know how to resolve which groups the user is a member of. The configuration for this can vary depending on your LDAP server and your directory schema. There a... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/ldap.mdx | main | vault | [
-0.016836870461702347,
-0.0395328663289547,
-0.05747447907924652,
0.06928540766239166,
-0.03235290199518204,
0.005138919688761234,
0.09889696538448334,
0.007220565341413021,
-0.06381788849830627,
-0.044345155358314514,
0.058548491448163986,
-0.02008429728448391,
0.018487635999917984,
-0.00... | -0.01442 |
engine. For example, the following command set the rotation to occur every Saturday at midnight (00:00): ```shell-session $ vault write auth/ldap/config \ ... rotation\_schedule="0 \* \* \* SAT" ... ``` Scheduled root credential rotation can also set a [rotation\_window](/vault/api-docs/auth/ldap#rotation\_window) duri... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/ldap.mdx | main | vault | [
0.0334705226123333,
0.028384875506162643,
-0.08676336705684662,
-0.017491141334176064,
-0.05142749473452568,
-0.005513831507414579,
-0.06517957150936127,
-0.013380915857851505,
0.058694180101156235,
-0.022314926609396935,
0.0059022922068834305,
0.04447690024971962,
0.07241331040859222,
0.0... | -0.074371 |
`memberUid`, `member`, or `uniqueMember` attributes. That search will begin under `ou=Groups,dc=example,dc=com`. - Group names are identified using the `cn` attribute. ```shell-session $ vault write auth/ldap/config \ url="ldaps://ldap.example.com" \ userattr="uid" \ userdn="ou=Users,dc=example,dc=com" \ discoverdn=tru... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/ldap.mdx | main | vault | [
0.0532856360077858,
0.025064632296562195,
-0.07957345992326736,
-0.008031545206904411,
-0.02970293164253235,
-0.023809906095266342,
0.06058637797832489,
-0.014716112054884434,
-0.017543649300932884,
-0.04920965060591698,
0.06420068442821503,
-0.11922405660152435,
0.10656323283910751,
0.004... | -0.087523 |
# Use JWT/OIDC authentication @include 'x509-sha1-deprecation.mdx' @include 'tips/custom-authn.mdx' ~> \*\*Note\*\*: Starting in Vault 1.17, if the JWT in the authentication request contains an `aud` claim (typical case) the associated `bound\_audiences` for the "jwt" role must \*\*exactly\*\* match at least one of the... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/jwt/index.mdx | main | vault | [
-0.011090831831097603,
0.033657826483249664,
-0.0033454420045018196,
-0.060077909380197525,
0.04975210130214691,
-0.07535070180892944,
0.004580366425216198,
-0.030945545062422752,
0.024034854024648666,
-0.1011078953742981,
-0.025286966934800148,
0.004669995047152042,
0.06931484490633011,
-... | -0.103045 |
in the CLI. ```shell-session $ vault login -method=oidc port=8400 role=test Complete the login via your OIDC provider. Launching browser to: https://myco.auth0.com/authorize?redirect\_uri=http%3A%2F%2Flocalhost%3A8400%2Foidc%2Fcallback&client\_id=r3qXc2bix9eF... ``` The browser will open to the generated URL to complet... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/jwt/index.mdx | main | vault | [
0.019165676087141037,
0.023115476593375206,
-0.09638932347297668,
-0.04556918516755104,
-0.011701849289238453,
-0.10791288316249847,
-0.04547543823719025,
0.0003717179351951927,
0.05044711381196976,
-0.06763143092393875,
0.004790810868144035,
-0.012953138910233974,
0.059727732092142105,
0.... | -0.09729 |
\ groups\_claim="https://vault/groups" \ policies=webapps \ ttl=1h ``` This role authorizes JWTs with the given subject and audience claims, gives it the `webapps` policy, and uses the given user/groups claims to set up Identity aliases. For the complete list of configuration options, please see the API documentation. ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/jwt/index.mdx | main | vault | [
-0.11138300597667694,
0.039021752774715424,
0.0038803452625870705,
-0.025519466027617455,
0.012777012772858143,
-0.04979054629802704,
0.03904060274362564,
-0.0022877922747284174,
0.01049831137061119,
-0.04660555720329285,
-0.016393013298511505,
-0.08873975276947021,
0.09703435748815536,
0.... | 0.031026 |
the [API docs](/vault/api-docs/auth/jwt) for more details. | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/jwt/index.mdx | main | vault | [
-0.058812011033296585,
0.016309745609760284,
-0.0631156638264656,
-0.029559509828686714,
0.02611311711370945,
-0.04632122069597244,
-0.04677550122141838,
-0.015489944256842136,
0.02268201671540737,
-0.10366708785295486,
-0.03133111074566841,
0.05718770995736122,
0.04512441158294678,
-0.046... | 0.078497 |
# Use IBM Verify for OIDC authentication The [IBM Verify](https://www.ibm.com/de-de/products/verify-access) identity provider (previously IBM Security Access Manager) returns group membership claims as a space-separated list of strings (e.g. `groups: "group-1 group-2"`) instead of a list of strings. To properly obtain ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/jwt/oidc-providers/ibmisam.mdx | main | vault | [
-0.05290228873491287,
0.026311885565519333,
-0.0850607231259346,
0.034123439341783524,
0.018036896362900734,
-0.03574943169951439,
0.08841058611869812,
0.029642220586538315,
0.07173307240009308,
-0.0763792097568512,
0.06833638995885849,
-0.004549107979983091,
0.08906823396682739,
-0.006426... | -0.026487 |
# Use ADFS for OIDC authentication Configure your Vault instance to work with Active Directory Federation Services (ADFS) and use ADFS accounts with OIDC for Vault login. ## Before you start 1. \*\*You must have Vault v1.15.0+\*\*. 1. \*\*You must be running ADFS on Windows Server\*\*. 1. \*\*You must have an OIDC clie... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/jwt/oidc-providers/adfs.mdx | main | vault | [
0.018619289621710777,
-0.030217133462429047,
-0.08373096585273743,
0.02302444912493229,
0.0008098816033452749,
-0.04185301065444946,
0.018555421382188797,
0.04927938058972359,
0.032231539487838745,
0.01175848487764597,
-0.013742076233029366,
-0.05084335803985596,
0.04825550317764282,
0.049... | -0.081855 |
Attribute store: `Active Directory` - LDAP attribute: `Token-Groups - Unqualified Names` - Outgoing claim type: `Group` [](/img/adfs-oidc-ldapgroupoption.png) ## Step 4: Create a default ADFS role in Vault Use the `vault write` C... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/jwt/oidc-providers/adfs.mdx | main | vault | [
-0.011167032644152641,
0.028671985492110252,
-0.0762934759259224,
0.04779532179236412,
0.059856463223695755,
-0.08426984399557114,
0.05304944887757301,
0.037924084812402725,
-0.02150060422718525,
-0.00463036959990859,
0.07922183722257614,
-0.05103936791419983,
0.06619353592395782,
0.076750... | -0.078042 |
alias: ```shell-session $ vault write identity/group-alias \ name="" \ mount\_accessor=$(cat accessor\_adfs.txt) \ canonical\_id="$(cat group\_id.txt)" ``` 1. Login to Vault as an AD user who is a member of YOUR\_EXISTING\_AD\_GROUP. 1. Read your test value from the KV plugin: ```shell-session $ vault kv list -mount=se... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/jwt/oidc-providers/adfs.mdx | main | vault | [
0.013189002871513367,
-0.010861312970519066,
-0.08980388939380646,
0.07221746444702148,
0.008166265673935413,
-0.07575472444295883,
0.048933785408735275,
-0.005889073014259338,
-0.00209744437597692,
-0.011325223371386528,
0.10245774686336517,
-0.09222832322120667,
0.024179326370358467,
0.0... | -0.085288 |
# Use ForgeRock for OIDC authentication 1. Navigate to Applications -> OAuth 2.0 -> Clients in ForgeRock Access Management. 1. Create new client. 1. Configure Client ID, Client Secret, Scopes and Redirection URIs. - `client ID` - `client secret` - `allowed\_redirect\_uris` should be the two redirect URIs for Vault CLI ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/jwt/oidc-providers/forgerock.mdx | main | vault | [
0.01070593111217022,
0.0818905159831047,
-0.07844370603561401,
-0.02325519733130932,
-0.03511172905564308,
-0.08505100011825562,
0.0004365925560705364,
0.03960492089390755,
0.03823889419436455,
-0.07505839318037033,
-0.05397540703415871,
-0.03806138411164284,
0.0948270633816719,
0.02066238... | -0.072099 |
# OIDC provider list OIDC providers are often highly configurable, and you should become familiar with their recommended settings and best practices. The guides listed below are largely community-driven and intended to help you get started. Corrections and additions may be submitted via the [Vault Github repository](ht... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/jwt/oidc-providers/index.mdx | main | vault | [
-0.07542245090007782,
-0.019285280257463455,
-0.0636417418718338,
0.026692194864153862,
0.034327711910009384,
-0.09151461720466614,
0.019868794828653336,
-0.04845498129725456,
0.009959861636161804,
-0.028841687366366386,
0.032038863748311996,
0.048892244696617126,
0.02518419362604618,
-0.0... | -0.020733 |
# Use Kubernetes for OIDC authentication Kubernetes can function as an OIDC provider such that Vault can validate its service account tokens using JWT/OIDC auth. -> \*\*Note:\*\* The JWT auth engine does \*\*not\*\* use Kubernetes' `TokenReview` API during authentication, and instead uses public key cryptography to ver... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/jwt/oidc-providers/kubernetes.mdx | main | vault | [
-0.06177448853850365,
0.02703009732067585,
0.01903562806546688,
-0.047202304005622864,
-0.02128809317946434,
-0.04991297423839569,
0.015133288688957691,
-0.010256950743496418,
0.14205433428287506,
-0.042123474180698395,
-0.04277288541197777,
0.009385896846652031,
0.05839831754565239,
0.005... | 0.033573 |
public keys. ```bash vault write auth/jwt/config \ jwt\_validation\_pubkeys="-----BEGIN PUBLIC KEY----- MIIBIjANBgkqhkiG9... -----END PUBLIC KEY-----","-----BEGIN PUBLIC KEY----- MIIBIjANBgkqhkiG9... -----END PUBLIC KEY-----" ``` 1. Configure a role and log in as detailed [below](#creating-a-role-and-logging-in). [jwk-... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/jwt/oidc-providers/kubernetes.mdx | main | vault | [
-0.013834873214364052,
-0.0033446396701037884,
-0.025859476998448372,
-0.061953525990247726,
-0.03831595182418823,
-0.022679055109620094,
0.03580182045698166,
0.055372051894664764,
0.0817803293466568,
-0.01989687979221344,
-0.029131677001714706,
-0.03788250312209129,
0.09590399265289307,
-... | 0.000201 |
# Use SecureAuth for OIDC authentication The [SecureAuth](https://www.secureauth.com/) identity provider returns group membership claims as a comma-separated list of strings (e.g. `groups: "group-1,group-2"`) instead of a list of strings. To properly obtain group membership when using SecureAuth as the identity provide... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/jwt/oidc-providers/secureauth.mdx | main | vault | [
-0.00265126652084291,
0.06606365740299225,
-0.0972713753581047,
0.05922912061214447,
0.03455081954598427,
-0.04071500897407532,
0.04584704712033272,
0.012265786528587341,
0.048971232026815414,
-0.06555048376321793,
0.034625910222530365,
-0.03525707870721817,
0.07643196731805801,
0.02510107... | -0.118888 |
# Use Google for OIDC authentication Main reference: [Using OAuth 2.0 to Access Google APIs](https://developers.google.com/identity/protocols/OAuth2) 1. Visit the [Google API Console](https://console.developers.google.com). 1. Create or a select a project. 1. Navigate to Menu > APIs & Services 1. Create a new credentia... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/jwt/oidc-providers/google.mdx | main | vault | [
-0.09629105031490326,
-0.0120003130286932,
-0.02210397459566593,
-0.021643323823809624,
-0.01589340716600418,
-0.0623873732984066,
0.009537596255540848,
0.017903806641697884,
0.03614979237318039,
-0.05730937048792839,
-0.046861354261636734,
-0.025803085416555405,
0.07930201292037964,
-0.04... | -0.083111 |
that has been granted domain-wide delegation of authority in Google Workspace. Required if accessing the Google Workspace Directory API through domain-wide delegation of authority, without using a service account key. The service account vault is running under must be granted the `iam.serviceAccounts.signJwt` permissio... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/jwt/oidc-providers/google.mdx | main | vault | [
-0.06076912581920624,
-0.025812692940235138,
0.008359935134649277,
-0.029034610837697983,
-0.026375791057944298,
-0.06740735471248627,
0.024409104138612747,
-0.06934516131877899,
0.02213282510638237,
-0.0214547086507082,
0.01782350055873394,
-0.004634153097867966,
0.08139950782060623,
-0.0... | -0.116033 |
# Use Azure AD for OIDC authentication ~> \*\*Note:\*\* Azure Active Directory Applications that have custom signing keys as a result of using the [claims-mapping](https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-claims-mapping) feature are currently not supported for OIDC authentication... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/jwt/oidc-providers/azuread.mdx | main | vault | [
-0.008420825935900211,
0.024058837443590164,
-0.11516433209180832,
0.002125462982803583,
-0.023386482149362564,
-0.010672611184418201,
0.04669712111353874,
0.012978299520909786,
0.09657064080238342,
0.060842446982860565,
0.03092961199581623,
-0.0008521222043782473,
0.0868631899356842,
0.04... | -0.10228 |
like: ```json { "\_claim\_names": { "groups": "src1" }, "\_claim\_sources": { "src1": { "endpoint": "https://graph.windows.net...." } } } ``` The OIDC auth method role can be configured to include the user ID in the endpoint URL, which will be used by Vault to retrieve the groups for the user. Additional API permission... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/jwt/oidc-providers/azuread.mdx | main | vault | [
-0.06694173067808151,
0.019321830943226814,
-0.08542832732200623,
0.051253147423267365,
0.008202138356864452,
-0.03400188311934471,
-0.0189913772046566,
-0.023342186585068703,
0.01793067902326584,
0.06403632462024689,
0.030155394226312637,
0.006350742187350988,
0.06619641929864883,
0.09560... | -0.073671 |
# Use Okta for OIDC authentication 1. Make sure an Authorization Server has been created. The "Issuer" field shown on the Setting page will be used as the `oidc\_discovery\_url`. 1. Visit Applications > Add Application (Web). 1. Configure Login redirect URIs. Save. 1. Save client ID and secret. Note your policy will ne... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/jwt/oidc-providers/okta.mdx | main | vault | [
-0.04013948515057564,
0.05729110911488533,
-0.047682084143161774,
0.06302931904792786,
0.00031730264890938997,
-0.05553789436817169,
0.046496398746967316,
0.007756031583994627,
-0.005163851194083691,
0.0042352378368377686,
0.01047463621944189,
-0.07949734479188919,
0.05713025480508804,
0.0... | -0.014078 |
# Use AppRole authentication The `approle` auth method allows machines or \_apps\_ to authenticate with Vault-defined \_roles\_. The open design of `AppRole` enables a varied set of workflows and configurations to handle large numbers of apps. This auth method is oriented to automated workflows (machines and services),... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/approle/index.mdx | main | vault | [
0.010805596597492695,
0.028999673202633858,
-0.06757588684558868,
-0.07001020014286041,
-0.04603265970945358,
-0.062271103262901306,
0.06383398920297623,
0.07325772941112518,
0.023462027311325073,
-0.01812109351158142,
-0.050358422100543976,
-0.04252040758728981,
0.12592892348766327,
0.037... | -0.000639 |
the AppRole against which the other credentials are evaluated. When authenticating against this auth method's login endpoint, the RoleID is a required argument (via `role\_id`) at all times. By default, RoleIDs are unique UUIDs, which allow them to serve as secondary secrets to the other credential information. However... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/approle/index.mdx | main | vault | [
-0.1076204776763916,
0.00828689057379961,
-0.027825674042105675,
-0.02023165300488472,
-0.002844251459464431,
-0.022578086704015732,
0.06997233629226685,
0.005912740249186754,
0.048829931765794754,
-0.02294386550784111,
-0.035761140286922455,
0.0038070811424404383,
0.10510971397161484,
-0.... | 0.040505 |
!= nil { return "", fmt.Errorf("unable to initialize Vault client: %w", err) } // A combination of a Role ID and Secret ID is required to log in to Vault // with an AppRole. // First, let's get the role ID given to us by our Vault administrator. roleID := os.Getenv("APPROLE\_ROLE\_ID") if roleID == "" { return "", fmt.... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/approle/index.mdx | main | vault | [
0.006929770577698946,
0.10669475793838501,
-0.06860947608947754,
0.006932592950761318,
0.022150268778204918,
-0.11097448319196701,
0.023532141000032425,
0.07799498736858368,
0.01053638756275177,
-0.07676750421524048,
0.03499327600002289,
-0.056717582046985626,
0.05099722370505333,
0.049387... | 0.023537 |
= new VaultClientSettings(vaultAddr, authMethod); IVaultClient vaultClient = new VaultClient(vaultClientSettings); // We can retrieve the secret from VaultClient Secret kv2Secret = null; kv2Secret = vaultClient.V1.Secrets.KeyValue.V2.ReadSecretAsync(path: "/creds").Result; var password = kv2Secret.Data.Data["password"]... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/approle/index.mdx | main | vault | [
0.029885606840252876,
0.04705183953046799,
-0.10117805004119873,
0.006895147264003754,
-0.05160583555698395,
0.0063611227087676525,
-0.06502200663089752,
0.059919070452451706,
0.020940374583005905,
-0.040234483778476715,
-0.021691258996725082,
-0.05970622971653938,
0.042585741728544235,
-0... | -0.16181 |
# Best practices for AppRole authentication At the core of Vault's usage is authentication and authorization. Understanding the methods that Vault surfaces these to the client is the key to understanding how to configure and manage Vault. - Vault provides authentication to a client by the use of [auth methods](/vault/d... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/approle/approle-pattern.mdx | main | vault | [
-0.022284191101789474,
0.0307717714458704,
-0.05079566687345505,
-0.04543059691786766,
0.01730792224407196,
-0.04878920689225197,
0.03048253431916237,
0.06530766189098358,
0.09325028210878372,
-0.026676243171095848,
0.02620469219982624,
0.027986953034996986,
0.11873014271259308,
0.03180110... | -0.034807 |
consumer\*\* - This is the final consumer of the secret from Vault. ## Platform credential delivery method To prevent any one system, other than the target client, from obtaining the complete set of credentials (RoleID and SecretID), the recommended implementation is to deliver those values separately through two diffe... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/approle/approle-pattern.mdx | main | vault | [
-0.07583484798669815,
0.07102043926715851,
-0.02702358365058899,
0.00014166950131766498,
-0.01906781643629074,
-0.02227574959397316,
0.05846429616212845,
0.0016328581841662526,
0.012856632471084595,
-0.02925538457930088,
-0.0032225463073700666,
-0.02240598574280739,
0.12544900178909302,
-0... | 0.007892 |
token which is valid for 60 seconds to unwrap. ```shell-session $ vault write -wrap-ttl=60s -force auth/approle/role/jenkins/secret-id Key Value --- ----- wrapping\_token: s.yzbznr9NlZNzsgEtz3SI56pX wrapping\_accessor: Smi4CO0Sdhn8FJvL8XvOT30y wrapping\_token\_ttl: 1m wrapping\_token\_creation\_time: 2021-06-07 20:02:0... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/approle/approle-pattern.mdx | main | vault | [
-0.02044210024178028,
0.07835352420806885,
-0.03488264977931976,
0.02435458078980446,
0.07765662670135498,
-0.0689862072467804,
-0.012246664613485336,
-0.014417354017496109,
0.06811786442995071,
0.004118199925869703,
-0.03560371696949005,
-0.0016687267925590277,
0.018513904884457588,
0.024... | 0.073561 |
### Usage workflow Jenkins needs to run a job requiring some data classified as secret and stored in Vault. It has a master and a worker node where the worker node runs jobs on spawned container runners that are short-lived. The process would look like: 1. Jenkins worker authenticates to Vault 2. Vault returns a token ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/approle/approle-pattern.mdx | main | vault | [
-0.07671438157558441,
0.06018893048167229,
-0.009041168726980686,
0.036200713366270065,
0.0461234524846077,
-0.0632205531001091,
-0.04469400644302368,
-0.04327424243092537,
-0.007134565617889166,
-0.05859534069895744,
-0.06133883818984032,
0.00719827227294445,
0.007175319828093052,
0.00392... | 0.062796 |
zero will allow unlimited uses. For best security, set `secret\_id\_num\_uses` to `1` use. Also, consider changing `secret\_id\_bound\_cidrs` to restrict the source IP range of the connecting devices. ## Anti-patterns Consider avoiding these anti-patterns when using Vault's AppRole auth method. ### CI worker retrieves ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/approle/approle-pattern.mdx | main | vault | [
-0.05842532962560654,
0.06707335263490677,
-0.06390907615423203,
-0.04327451065182686,
-0.04517093673348427,
-0.009885734878480434,
0.004906120244413614,
-0.023475514724850655,
0.001508811372332275,
-0.015903756022453308,
-0.010672290809452534,
0.022747807204723358,
0.06408175826072693,
0.... | 0.060807 |
# Set up login MFA The underlying identity system in Vault supports multi-factor authentication (MFA) for authenticating to an auth method using different authentication types. MFA implementation | Required Vault edition ----------------------------------------- | ----------------------- Login MFA | Vault Community [St... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/login-mfa/index.mdx | main | vault | [
-0.012551908381283283,
-0.012247612699866295,
-0.05709739029407501,
-0.014177467674016953,
0.010411147959530354,
-0.0027244833763688803,
-0.01179070770740509,
-0.004659436643123627,
0.03165695443749428,
-0.032154981046915054,
0.004573005251586437,
-0.019141554832458496,
0.04324762895703316,
... | -0.001815 |
format is consistent for all supported MFA methods, and one can use either of the above two formats. If there are multiple MFA methods that need to be validated, a user can pass in multiple `X-Vault-MFA` HTTP headers. #### Sample request ```shell-session $ curl \ --header "X-Vault-Token: ..." \ --header "X-Vault-MFA: d... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/login-mfa/index.mdx | main | vault | [
-0.0003323316341266036,
0.07735659927129745,
-0.12131638079881668,
-0.06630685925483704,
0.01646542176604271,
-0.009348094463348389,
-0.043315306305885315,
-0.029481353238224983,
0.021667735651135445,
-0.006592070683836937,
0.02599913440644741,
-0.06956261396408081,
0.04774364084005356,
0.... | -0.02804 |
MFA methods, such as PingID, Okta, and Duo, do not require a passcode, the associated credentials will be a list with one empty string. #### Sample payload ```json { "mfa\_request\_id": "5879c74a-1418-1948-7be9-97b209d693a7", "mfa\_payload": { "d16fd3c2-50de-0b9b-eed3-0301dadeca10": ["910201"] } } ``` If an MFA method ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/login-mfa/index.mdx | main | vault | [
-0.10008125007152557,
-0.005890135187655687,
-0.09443134069442749,
-0.012489400804042816,
-0.03562343120574951,
-0.013008392415940762,
-0.03360719233751297,
-0.05723617970943451,
-0.03695569932460785,
-0.003631525207310915,
0.019236750900745392,
-0.12236671894788742,
-0.0021518911235034466,
... | 0.072074 |
write -field=barcode \ /identity/mfa/method/totp/admin-generate \ method\_id=$TOTP\_METHOD\_ID entity\_id=$ENTITY\_ID \ | base64 -d > qr-code.png ``` #### Create login MFA enforcement Capture the LDAP auth method accessor for use in creating a Login MFA enforcement. ```shell-session $ vault auth list -format=json --det... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/login-mfa/index.mdx | main | vault | [
0.023659097030758858,
0.07389918714761734,
-0.10266222059726715,
-0.011311645619571209,
-0.010536978021264076,
-0.014090612530708313,
0.02299770712852478,
0.017735086381435394,
0.006897570565342903,
0.013762579299509525,
0.08254650980234146,
-0.06688529253005981,
0.06463955342769623,
0.033... | -0.055694 |
# Login MFA FAQ This FAQ section contains frequently asked questions about the Login MFA feature. - [Q: What MFA features can I access if I upgrade to Vault version 1.10?](#q-what-mfa-features-can-i-access-if-i-upgrade-to-vault-version-1-10) - [Q: What are the various MFA workflows that are available to me as a Vault u... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/login-mfa/faq.mdx | main | vault | [
-0.005041291005909443,
0.019294491037726402,
-0.01710965856909752,
-0.03383464738726616,
0.08991550654172897,
0.04058057442307472,
-0.006115675438195467,
-0.031560271978378296,
-0.05403729900717735,
-0.0953623428940773,
0.008002987131476402,
-0.027522407472133636,
0.019414110109210014,
0.0... | -0.003749 |
Vault Community Edition, prior to introducing MFA in the Enterprise version. This is now a deprecated feature. Refer to the [deprecation notices](/vault/docs/updates/deprecation) page for detailed product plans around deprecated features. We plan to remove Legacy MFA in 1.11. ### Q: will HCP Vault Dedicated support MFA... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/login-mfa/faq.mdx | main | vault | [
-0.024600565433502197,
0.028898829594254494,
-0.017172109335660934,
-0.030524585396051407,
0.04788845032453537,
0.02982301451265812,
-0.05075424537062645,
-0.03589753434062004,
-0.033223167061805725,
-0.05877099186182022,
0.025138676166534424,
-0.03800401836633682,
0.04236233979463577,
-0.... | -0.011444 |
endpoints, then passing those method IDs to the `identity/mfa/login-enforcement` endpoint. MFA methods supported: TOTP, Okta, Duo, PingID. | | [Okta Auth MFA](/vault/docs/auth/okta) | CLI/API | MFA methods supported: [TOTP](https://help.okta.com/en/prod/Content/Topics/Security/mfa-totp-seed.htm) , [Okta Verify Push](ht... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/login-mfa/faq.mdx | main | vault | [
-0.0503026507794857,
0.054948654025793076,
-0.07509118318557739,
-0.037499070167541504,
0.037674274295568466,
-0.009307419881224632,
0.006446785759180784,
-0.02775001712143421,
0.017036866396665573,
-0.024085158482193947,
0.06981515139341354,
-0.02722744457423687,
0.04005717858672142,
0.02... | 0.022272 |
-the new endpoints yield an ID instead of allowing you to define a name -the new non-TOTP endpoints have a username\_format field instead of username\_format+mount\_accessor fields; see [Templated Policies](/vault/docs/concepts/policies#templated-policies) for the username\_format format. 1. Instead of writing sentinel... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/login-mfa/faq.mdx | main | vault | [
0.02260446734726429,
-0.023072922602295876,
-0.017911074683070183,
-0.02091701701283455,
0.0038132460322231054,
-0.00342135620303452,
0.01751904934644699,
-0.023697596043348312,
0.015127967111766338,
0.02529936097562313,
0.01603793352842331,
-0.06450558453798294,
-0.013806709088385105,
0.0... | 0.038629 |
# Use Active Directory Federation Services for SAML @include 'alerts/enterprise-and-hcp.mdx' Configure your Vault instance to work with Active Directory Federation Services (AD FS) and use AD FS accounts for SAML authentication. ## Before you start - \*\*You must have Vault Enterprise or HCP Vault v1.15.5+\*\*. - \*\*Y... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/saml/adfs.mdx | main | vault | [
0.03496639430522919,
0.0029792592395097017,
-0.08951346576213837,
-0.04518625885248184,
-0.02776332199573517,
0.026051413267850876,
0.03719624876976013,
0.010075590573251247,
0.033993031829595566,
-0.02256348729133606,
-0.014494504779577255,
-0.05603751912713051,
0.0913299173116684,
0.0614... | -0.072712 |
` -SignedSamlRequestsRequired $false ``` ## Step 5: Create a default AD FS role in Vault Use the Vault CLI to create a default role for users authenticating with AD FS where: - `SAML\_PLUGIN\_PATH` is the full path (`/MOUNT\_PATH/NAME`) to your SAML plugin. - `VAULT\_ROLE` is the name of your new AD FS role. For exampl... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/saml/adfs.mdx | main | vault | [
-0.00859755463898182,
-0.06708630174398422,
-0.08533249795436859,
0.0051141828298568726,
-0.01643022894859314,
-0.04902401939034462,
0.06827128678560257,
0.007483948953449726,
-0.01895172894001007,
0.001841963268816471,
0.07763640582561493,
-0.053552933037281036,
0.06566594541072845,
0.094... | -0.085218 |
# Set up SAML authentication @include 'alerts/enterprise-and-hcp.mdx' @include 'tips/custom-authn.mdx' The `saml` auth method allows users to authentication with Vault using their identity within a [SAML V2.0](https://saml.xml.org/saml-specifications) identity provider. Authentication is suited for human users by requi... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/saml/index.mdx | main | vault | [
0.006431872025132179,
0.035558346658945084,
-0.06050742417573929,
-0.05557171627879143,
-0.04990899935364723,
0.0037523899227380753,
0.06611432880163193,
-0.018690722063183784,
0.09408364444971085,
-0.06727632880210876,
0.010607738979160786,
-0.015599259175360203,
0.07670160382986069,
0.06... | -0.070784 |
to TLS-protect the assertion consumer service URLs. A warning will be returned from Vault if any of the configured assertion consumer service URLs are not protected by TLS. #### Configuration for replication To support a single auth method mount being used across Vault [replication](/vault/docs/enterprise/replication) ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/saml/index.mdx | main | vault | [
-0.07814822345972061,
0.0456121526658535,
-0.08774803578853607,
-0.04011248052120209,
0.008923547342419624,
-0.05053478851914406,
0.0025875286664813757,
-0.05334446206688881,
0.08704007416963577,
-0.022710731253027916,
0.02498820051550865,
-0.035185012966394424,
0.12201453000307083,
0.0496... | -0.009226 |
# Link Active Directory SAML groups to Vault @include 'alerts/enterprise-and-hcp.mdx' Configure your Vault instance to link your Active Directory groups to Vault policies with SAML. ## Before you start - \*\*You must have Vault Enterprise or HCP Vault v1.15.5+\*\*. - \*\*You must be running AD FS on Windows Server\*\*.... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/saml/link-vault-group-to-ad.mdx | main | vault | [
0.013752502389252186,
-0.015052038244903088,
-0.0990258976817131,
-0.006917632184922695,
-0.009413630701601505,
-0.0006561868358403444,
0.030736684799194336,
-0.025927888229489326,
0.03421584889292717,
-0.032014984637498856,
0.03547937050461769,
-0.042800258845090866,
0.07640518993139267,
... | -0.07109 |
# Troubleshoot AD FS: Before you start Troubleshooting guidance for solving problems with AD FS and SAML. ## Temporarily enable verbose logging Expanding SAML response data is a \*\*temporary\*\* change. Do not leave verbose logging on in production as SAML responses may contain sensitive information. 1. Enable verbose... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/saml/troubleshoot-adfs/index.mdx | main | vault | [
0.028858931735157967,
-0.009364169090986252,
-0.07040374726057053,
0.05316818878054619,
-0.0014370062854140997,
-0.061051737517118454,
0.012438944540917873,
-0.04873717203736305,
0.03299759700894356,
0.04389948397874832,
0.04355594143271446,
-0.017910227179527283,
0.017712535336613655,
0.0... | -0.086075 |
# AD FS event 320 Troubleshoot problems where your AD FS event logs show error 320. ## Example debugging data AD FS event log shows the following error: ```shell-session The verification of the SAML message signature failed. Message issuer: MyVaultIdentifier Exception details: MSIS7086: The relying party trust 'MyVault... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/saml/troubleshoot-adfs/adfs-event-320.mdx | main | vault | [
0.008911197073757648,
-0.008143983781337738,
-0.06293244659900665,
-0.011128505691885948,
0.003159720916301012,
-0.06971708685159683,
0.06442536413669586,
-0.01784648187458515,
0.005120857618749142,
0.07499178498983383,
0.03312068432569504,
-0.049433086067438126,
0.06042037531733513,
0.082... | -0.087176 |
# Clients cannot connect to Vault: invalid `BoundSubjects` Troubleshoot problems where the debugging data suggests a problem with bound subjects. ## Example debugging data ```json [DEBUG] auth.saml.auth\_saml\_b1886dfe: validating user context for role: api=callback role\_name=default-saml role="{ "token\_bound\_cidrs"... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/saml/troubleshoot-adfs/boundsubjects.mdx | main | vault | [
-0.018536647781729698,
0.029656346887350082,
-0.08074184507131577,
-0.018193069845438004,
-0.07254654914140701,
-0.07851266860961914,
-0.0043005128391087055,
-0.0013332297094166279,
0.021357132121920586,
-0.002940775826573372,
0.008183878846466541,
-0.010468351654708385,
0.04871072620153427,... | -0.049368 |
# Automatic group mapping fails Troubleshoot problems where the debugging data suggests a bad or nonexistent mapping between your Vault role and AD FS the Claim Issuance Policy. ## Example debugging data ```json [DEBUG] auth.saml.auth\_saml\_1d2227e7: validating user context for role: api=callback role\_name=default-sa... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/auth/saml/troubleshoot-adfs/bad-mapping.mdx | main | vault | [
-0.03296812251210213,
-0.004767115227878094,
-0.05406833812594414,
0.011386625468730927,
-0.044696688652038574,
-0.046767473220825195,
0.028394905850291252,
-0.02297982946038246,
0.0043739620596170425,
0.012554471381008625,
0.09195051342248917,
-0.06960976123809814,
0.031999628990888596,
0... | -0.055452 |
# Rollback or downgrade Vault plugins Downgrading a plugin in the catalog affects all uses of that plugin version. Always check the plugin release notes for unsupported transitions before starting your rollback or downgrade. ## Before you start - \*\*To register and downgrade official enterprise plugins, you must have ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/plugins/rollback.mdx | main | vault | [
0.04422089457511902,
-0.021825656294822693,
-0.0024754055775702,
-0.09553168714046478,
-0.011814521625638008,
-0.02868911810219288,
-0.11422538012266159,
-0.044299814850091934,
-0.04591083899140358,
0.02143711782991886,
0.049512263387441635,
0.04141896590590477,
-0.030958686023950577,
0.07... | -0.106615 |
# Register and enable external plugins An external plugin is any authentication or secrets plugin build from external code. Vault pre-registers commonly used external plugins (like `kv`), but you must manually add other external plugins to the Vault plugin catalog before you can use them with your Vault installation. I... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/plugins/register.mdx | main | vault | [
0.00722377048805356,
-0.07523763924837112,
-0.08470424264669418,
-0.027131740003824234,
-0.01598295569419861,
-0.01850927248597145,
-0.06759063154459,
0.03673386201262474,
0.013019345700740814,
-0.012275631539523602,
0.09377341717481613,
-0.02148211933672428,
-0.015333455987274647,
0.07032... | -0.001263 |
# Plugin architecture Plugins are separate, standalone applications with have predefined interfaces and parameters. Vault executes and communicates with plugins over RPC. Plugins do not share memory space with Vault and a crash in the plugin cannot crash the entirety of Vault. ## Plugin registration An important consid... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/plugins/plugin-architecture.mdx | main | vault | [
-0.008999884128570557,
-0.1057356521487236,
-0.0836566761136055,
-0.011232630349695683,
-0.024204956367611885,
0.007378188893198967,
-0.06468623131513596,
0.01093672588467598,
0.0012773218331858516,
-0.012456625699996948,
0.06417779624462128,
0.02792319469153881,
0.008477076888084412,
0.06... | -0.036055 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.