a3dfde5cec
* conversion stage 1 * correct image paths * add sidebar title to frontmatter * docs/concepts and docs/internals * configuration docs and multi-level nav corrections * commands docs, index file corrections, small item nav correction * secrets converted * auth * add enterprise and agent docs * add extra dividers * secret section, wip * correct sidebar nav title in front matter for apu section, start working on api items * auth and backend, a couple directory structure fixes * remove old docs * intro side nav converted * reset sidebar styles, add hashi-global-styles * basic styling for nav sidebar * folder collapse functionality * patch up border length on last list item * wip restructure for content component * taking middleman hacking to the extreme, but its working * small css fix * add new mega nav * fix a small mistake from the rebase * fix a content resolution issue with middleman * title a couple missing docs pages * update deps, remove temporary markup * community page * footer to layout, community page css adjustments * wip downloads page * deps updated, downloads page ready * fix community page * homepage progress * add components, adjust spacing * docs and api landing pages * a bunch of fixes, add docs and api landing pages * update deps, add deploy scripts * add readme note * update deploy command * overview page, index title * Update doc fields Note this still requires the link fields to be populated -- this is solely related to copy on the description fields * Update api_basic_categories.yml Updated API category descriptions. Like the document descriptions you'll still need to update the link headers to the proper target pages. * Add bottom hero, adjust CSS, responsive friendly * Add mega nav title * homepage adjustments, asset boosts * small fixes * docs page styling fixes * meganav title * some category link corrections * Update API categories page updated to reflect the second level headings for api categories * Update docs_detailed_categories.yml Updated to represent the existing docs structure * Update docs_detailed_categories.yml * docs page data fix, extra operator page remove * api data fix * fix makefile * update deps, add product subnav to docs and api landing pages * Rearrange non-hands-on guides to _docs_ Since there is no place for these on learn.hashicorp, we'll put them under _docs_. * WIP Redirects for guides to docs * content and component updates * font weight hotfix, redirects * fix guides and intro sidenavs * fix some redirects * small style tweaks * Redirects to learn and internally to docs * Remove redirect to `/vault` * Remove `.html` from destination on redirects * fix incorrect index redirect * final touchups * address feedback from michell for makefile and product downloads
38 lines
1.5 KiB
Markdown
38 lines
1.5 KiB
Markdown
---
|
|
layout: "docs"
|
|
page_title: "Upgrading to Vault 0.6.3 - Guides"
|
|
sidebar_title: "Upgrade to 0.6.3"
|
|
sidebar_current: "docs-upgrading-to-0.6.3"
|
|
description: |-
|
|
This page contains the list of deprecations and important or breaking changes
|
|
for Vault 0.6.3. Please read it carefully.
|
|
---
|
|
|
|
# Overview
|
|
|
|
This page contains the list of deprecations and important or breaking changes
|
|
for Vault 0.6.3. Please read it carefully.
|
|
|
|
## LDAP Null Binds Disabled By Default
|
|
|
|
When using the LDAP auth method, `deny_null_bind` has a default value of
|
|
`true`, preventing a successful user authentication when an empty password
|
|
is provided. If you utilize passwordless LDAP binds, `deny_null_bind` must
|
|
be set to `false`. Upgrades will keep previous behavior until the LDAP
|
|
configuration information is rewritten, at which point the new behavior
|
|
will be utilized.
|
|
|
|
## Request Size Limitation
|
|
|
|
A maximum request size of 32MB is imposed to prevent a denial of service attack
|
|
with arbitrarily large requests.
|
|
|
|
## Any Audit Device Successfully Activated Allows Active Duty
|
|
|
|
Previously, when a new Vault node was taking over service in an HA cluster, all
|
|
audit devices were required to be active successfully to take over active
|
|
duty. This behavior now matches the behavior of the audit logging system
|
|
itself: at least one audit device must successfully be activated. The server
|
|
log contains an error when this occurs. This helps keep a Vault HA cluster
|
|
working when there is a misconfiguration on a standby node.
|