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

Backport of Vault documentation: Re-added missing heading into stable-website #13780

Merged
merged 1 commit into from
Jan 25, 2022
Merged

Backport of Vault documentation: Re-added missing heading into stable-website #13780

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 9 additions & 6 deletions website/content/docs/enterprise/license/autoloading.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.