Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

auth/ldap: add known issue to 1.9 notes about alias names #14325

Closed
wants to merge 2 commits into from
Closed

auth/ldap: add known issue to 1.9 notes about alias names #14325

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b4219af
auth/ldap: add known issue to 1.9 notes
jasonodonnell Mar 1, 2022
58f3b03
Clarify note
jasonodonnell Mar 1, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 4 additions & 0 deletions website/content/docs/release-notes/1.9.0.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -117,3 +117,7 @@ As called out in the documentation, Vault does not make backwards compatible gua
## Feature Deprecations and EOL

Please refer to the [Deprecation Plans and Notice](/docs/deprecation) page for up-to-date information on feature deprecations and plans. An [FAQ](/docs/deprecation/faq) page is also available to address questions concerning decisions made about Vault feature deprecations.

## Known Issues

- There is a known issue with LDAP auth alias names changing in 1.9. This occurs if the LDAP auth method is in two different ways: `binddn` is not set and/or `upndomain` is set. If templated policies were depending on the older style alias names, those policies should be updated to use `alias.metadata.name`, which now stores the username. At this time there are no other known workarounds.