upstream/vault
1
0
Fork 0
mirror of https://github.com/hashicorp/vault.git synced 2026-06-09 08:55:13 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 11

added missing title (#13775)

Browse source
This commit is contained in:
Loann Le 2022-01-25 10:19:10 -08:00 committed by GitHub
parent 1f20ad96dc
commit 3b1ad52182
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
website/content/docs/enterprise/license/autoloading.mdx
View file

@ -4,27 +4,30 @@ page_title: License Autoloading
description: An overview of license autoloading.
---
# License Autoloading
Prior to Vault 1.8, Vault Enterprise would be licensed using special binaries
that contained embedded licenses, or via a license written into Vault storage
using the [PUT sys/license API](/api/system/license#install-license).
As of Vault 1.8 those options still exist but are deprecated, and the recommended
mechanism for managing licenses is called License Autoloading. New clusters are
mechanism for managing licenses is called License Autoloading. New clusters are
required to use the autoloading method.
License Autoloading can be done using one of these mechanisms, in decreasing order
of priority (i.e. `VAULT_LICENSE` takes precedence over `VAULT_LICENSE_PATH`, which
takes precedence over `license_path` in config.)
* [VAULT_LICENSE environment variable](/docs/commands#vault_license)
* [VAULT_LICENSE_PATH environment variable](/docs/commands#vault_license_path)
* [license_path in config](/docs/configuration#license_path)
- [VAULT_LICENSE environment variable](/docs/commands#vault_license)
- [VAULT_LICENSE_PATH environment variable](/docs/commands#vault_license_path)
- [license_path in config](/docs/configuration#license_path)
Nodes within a cluster should be consistently licensed. All nodes in a cluster
should use autoloading, or none should. If autoloading is used, all nodes should
use the same license string. Warnings will be written to the log when there
are discrepancies.
If autoloading is used, any existing stored license will be ignored. The presence
If autoloading is used, any existing stored license will be ignored. The presence
of a stored license in conjunction with an autoloaded license will also result in
logged warnings. Once a migration to autoloading is completed, it is recommended to use
logged warnings. Once a migration to autoloading is completed, it is recommended to use
the [DELETE API](/api/system/license#delete-license) to remove the stored license.