luxolus/open-vault
2
0
Fork 0
Code Issues 1 Pull requests Releases Activity

docs: small heading fix on 1.10 release notes (#14716)

Browse source
This commit is contained in:
Calvin Leung Huang 2022-03-29 15:24:33 -07:00 committed by GitHub
parent f1aa1ed3af
commit 7ec5e711d0
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
website/content/docs/release-notes/1.10.0.mdx
View file

@ -146,7 +146,7 @@ We will have a fix for this issue in Vault 1.10.1. Until this issue is fixed, yo
When a user has a policy that allows creating a secret engine but not reading it, after successful creation, the user sees a message `n is undefined` instead of a permissions error. We will have a fix for this issue in an upcoming minor release. When a user has a policy that allows creating a secret engine but not reading it, after successful creation, the user sees a message `n is undefined` instead of a permissions error. We will have a fix for this issue in an upcoming minor release.
### »Adding/Modifying Duo MFA method for Enterprise MFA triggers a panic error ### Adding/Modifying Duo MFA method for Enterprise MFA triggers a panic error
When adding or modifying a Duo MFA method for step-up Enterprise MFA using the `sys/mfa/method/duo` endpoint, a panic gets triggered due to a missing schema field. We will have a fix for this in Vault 1.10.1. Until this issue is fixed, avoid making any changes to your Duo configuration if you are upgrading Vault to v1.10.0. When adding or modifying a Duo MFA method for step-up Enterprise MFA using the `sys/mfa/method/duo` endpoint, a panic gets triggered due to a missing schema field. We will have a fix for this in Vault 1.10.1. Until this issue is fixed, avoid making any changes to your Duo configuration if you are upgrading Vault to v1.10.0.