2022-01-27 10:08:00 +00:00
|
|
|
Unseal Key 1: Tbel8zdD7vS8g1bSUaW5Q+8KS3No+sNVrqGKodiPGJ57
|
|
|
|
Unseal Key 2: vioPM3fJJ8hitlBq7NuzsrlKCiHRo7dKkJXuskNJlERP
|
|
|
|
Unseal Key 3: T0JJT7ATamUa+Quk9VDWb2WvstQ3W7rGUC+CgJbZHo2v
|
|
|
|
Unseal Key 4: fC8m3accpSLsVhK3u3OA1kpsoUuXTp11xZcJolvu8uvo
|
|
|
|
Unseal Key 5: YfFun6w9cihqYDGak7c5Q1ZQxafI1vJ0B/d/XJqaUygC
|
2021-10-12 19:36:06 +00:00
|
|
|
|
2022-01-27 10:08:00 +00:00
|
|
|
Initial Root Token: s.90scV8c059y8IelnA33YAs6C
|
2021-10-12 19:36:06 +00:00
|
|
|
|
|
|
|
Vault initialized with 5 key shares and a key threshold of 3. Please securely
|
|
|
|
distribute the key shares printed above. When the Vault is re-sealed,
|
|
|
|
restarted, or stopped, you must supply at least 3 of these keys to unseal it
|
|
|
|
before it can start servicing requests.
|
|
|
|
|
|
|
|
Vault does not store the generated master key. Without at least 3 key to
|
|
|
|
reconstruct the master key, Vault will remain permanently sealed!
|
|
|
|
|
|
|
|
It is possible to generate new unseal keys, provided you have a quorum of
|
|
|
|
existing unseal keys shares. See "vault operator rekey" for more information.
|