2024-09-30 09:19:55 +00:00
|
|
|
Unseal Key 1: RtovEr6q8xNSaCImqaWpp002PphC+o/AwZm9sOmbK1Vg
|
|
|
|
Unseal Key 2: teEUylJ1EzNRB4ZJuUTwFaK4BA3xOt9KUhcSIVKXi0TF
|
|
|
|
Unseal Key 3: 8wZmMJJ6TqCjB5/RDXbqJC6t0+MHJBjm+CdIu0db59eV
|
|
|
|
Unseal Key 4: mYNQzPMnxNRqGwFylLgLsFD2eeL1GmAD6y75SjTsaXUm
|
|
|
|
Unseal Key 5: kPBl+CC6HGNXho3XrBAvl4gnYU381P5wZ9SnurenUKTU
|
2021-10-12 19:36:06 +00:00
|
|
|
|
2024-09-30 09:19:55 +00:00
|
|
|
Initial Root Token: s.GqPbY2ceIiaxiuMKj3QserDL
|
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.
|
|
|
|
|
2024-09-30 09:19:55 +00:00
|
|
|
Vault does not store the generated root key. Without at least 3 keys to
|
|
|
|
reconstruct the root key, Vault will remain permanently sealed!
|
2021-10-12 19:36:06 +00:00
|
|
|
|
|
|
|
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.
|