mirrors/vault
1
0
Fork 0
mirror of https://github.com/hashicorp/vault.git synced 2026-05-05 12:26:34 +02:00
Code Issues Projects Releases Wiki Activity

Add note regarding LDAP regression. (#9038)

Browse Source
This commit is contained in:
ncabatoff 2020-05-27 12:29:30 -04:00 committed by GitHub
parent c455a31f07
commit 460db7dad8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 11 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
website/pages/docs/upgrading/upgrade-to-1.4.0.mdx
View File

@ -10,6 +10,8 @@ description: |-
# Overview
This page contains the list of deprecations and important or breaking changes
for Vault 1.3.4 compared to 1.4.0. Please read it carefully.
for Vault 1.3.X compared to 1.4.0. Please read it carefully.
@include 'partials/aws-auth-metadata-issue.mdx'
@include 'partials/ldap-upndomain-issue.mdx'

2
website/pages/docs/upgrading/upgrade-to-1.4.1.mdx
View File

@ -31,3 +31,5 @@ vault write auth/aws/config/identity \
ec2_metadata=account_id,auth_type,instance_id,region \
iam_metadata=account_id,auth_type,client_user_id,canonical_arn,inferred_entity_id,inferred_aws_region
```
@include 'partials/ldap-upndomain-issue.mdx'

6
website/pages/partials/ldap-upndomain-issue.mdx Normal file
View File

@ -0,0 +1,6 @@
## LDAP auth engine and upndomain
Users of the LDAP auth engine with the `upndomain` configuration setting populated
should hold off on upgrading to 1.4.x for now. We are investigating a regression
introduced by [#8333](https://github.com/hashicorp/vault/pull/8333). There is
no Github issue for this bug yet.