vault.internal.dev.socrate.ninja Open in urlscan Pro
51.159.86.116  Public Scan

Submitted URL: https://vault.internal.dev.socrate.ninja/
Effective URL: https://vault.internal.dev.socrate.ninja/ui/
Submission: On March 26 via automatic, source certstream-suspicious — Scanned from FR

Form analysis 1 forms found in the DOM

<form id="shamir" aria-label="shamir form" class="has-top-margin-m">
  <!---->
  <div class="has-bottom-margin-m">
    <!----><!---->
  </div>
  <div class="field">
    <label for="key" class="is-label" data-test-shamir-key-label=""> Unseal Key Portion </label>
    <div class="control">
      <input id="ember16" class="ember-text-field ember-view input" name="key" autocomplete="off" data-test-shamir-key-input="" type="password">
    </div>
  </div>
  <div class="columns is-mobile">
    <div class="column is-narrow">
      <button class="button is-primary" data-test-shamir-submit="" type="submit"> Unseal </button>
    </div>
    <div class="column is-flex-v-centered is-flex-end">
      <!---->
    </div>
  </div>
</form>

Text Content

HCP LINK ERROR

Timestamp

Not available

Error

Not available

Additional information

Check the logs for more information

Close



UNSEAL VAULT



Vault is sealed

Unseal Vault by entering portions of the unseal key. This can be done via
multiple mechanisms on multiple computers. Once all portions are entered, the
root key will be decrypted and Vault will unseal.

Unseal Key Portion

Unseal


Seal/unseal documentation

© 2024 HashiCorp Vault 1.15.6 Upgrade to Vault Enterprise Documentation

The Vault Browser CLI provides an easy way to execute common Vault CLI commands,
such as write, read, delete, and list. It does not include kv v2 write or put
commands. For guidance, type `help`.

Examples:

→ Write secrets to kv v1: write <mount>/my-secret foo=bar

→ List kv v1 secret keys: list <mount>/

→ Read a kv v1 secret: read <mount>/my-secret

→ Mount a kv v2 secret engine: write sys/mounts/<mount> type=kv
options=version=2

→ Read a kv v2 secret: kv-get <mount>/secret-path

→ Read a kv v2 secret's metadata: kv-get <mount>/secret-path -metadata