luxolus/open-vault
2
0
Fork 0
Code Issues 1 Pull requests Releases Activity
open-vault/website/source/guides/upgrading/upgrade-to-0.6.3.html.md
Seth Vargo c5665920f6
Standardize on "auth method" 
This removes all references I could find to:

- credential provider
- authentication backend
- authentication provider
- auth provider
- auth backend

in favor of the unified:

- auth method
2017-10-24 09:32:15 -04:00

1.4 KiB
Raw Blame History

layout page_title sidebar_current description
guides Upgrading to Vault 0.6.3 - Guides guides-upgrading-to-0.6.3 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 Backend Successfully Activated Allows Active Duty

Previously, when a new Vault node was taking over service in an HA cluster, all audit backends 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 backend 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.