Intekhab Rizvi

Chapter 11 / 28

Accessing Vault Using the Browser-Based UI

HashiCorp Vault For Beginners6 min read

So far, we've been interacting with Vault exclusively using the command line. That’s powerful—but let’s be honest: sometimes, we all appreciate a nice visual interface. In this chapter, we’ll explore the Vault UI, which provides a point-and-click way to manage secrets, auth methods, and more.

Let’s talk about the different ways to access Vault and what the UI is (and isn’t) good for.

Vault provides three primary interfaces:

InterfaceDescriptionBest Use Case
CLIThe command-line interface we've used so far.Day-to-day admin tasks, scripting, automation.
HTTP APIThe most complete way to interact with Vault.Used by applications and integrations.
UI (Web Interface)A browser-based dashboard.Good for exploring, learning, and quick operations.

Important: The Vault UI is the least feature-rich interface. Some advanced features (like AppRole pull-based Secret ID) can only be done via CLI or API.

Enabling and Accessing the UI

The Vault UI is enabled by default in most Vault images if the config has the following line. Have a look at your config file present in side the vault-data/config/vault-config.hcl folder

ui = true

In case you want to disable the UI, simply set it to false in your config file and restart the container using our same docker start command.

ui = false

That’s it. Disabling the UI might be useful in high-security production environments.

Screenshot for “Enabling and Accessing the UI” in chapter 11: Accessing Vault Using the Browser-Based UI

Once your container is running with ui = true, you can access the UI by opening below URL in your browser.

http://localhost:8200

You can login at vault from UI by using the root token you received during vault operator init.

Hands-On – Let’s use the UI to Manage a Secret Engine

Let’s now perform some real operations using the UI. You’ve already done these with the CLI—now let’s repeat them visually.

1. Enable KV Secret Engine at ui-dev

  1. Go to Secrets Engines → Enable new engine
  2. Choose KV
  3. Set Path to ui-dev and let all the value as is.
  4. Click Enable Engine

Done. You’ve created a versioned secret engine at ui-dev.

Screenshot for “1. Enable KV Secret Engine at ui-dev” in chapter 11: Accessing Vault Using the Browser-Based UI

Screenshot for “1. Enable KV Secret Engine at ui-dev” in chapter 11: Accessing Vault Using the Browser-Based UI

\

2. Put a New Value

  1. Click into ui-dev
  2. Click Create secret
  3. Set the “Path for this secret” to sample
  4. Under Secret data, add key: username, value: admin
  5. Add another key: password, value: Vault4Life!
  6. Click Save

You’ve just written data to ui-dev/sample.

Screenshot for “2. Put a New Value” in chapter 11: Accessing Vault Using the Browser-Based UI

3. List All Values

  1. From the “Secret Engines” home page, click on “ui-dev”
  2. You’ll see all paths inside this engine

Screenshot for “3. List All Values” in chapter 11: Accessing Vault Using the Browser-Based UI

Each listed path is a secret entry

4. Read the Value

  1. Now click on the “Secret” tab, you’ll see the key-value pairs
  2. You can copy the values from here for use elsewhere

Screenshot for “4. Read the Value” in chapter 11: Accessing Vault Using the Browser-Based UI

5. Delete a Value

  1. Now go back to the list page
  2. Choose the three-dot menu (⋮) aginst the “Sample” avaliable on the right handside.
  3. Click on “Permanently delete”

Screenshot for “5. Delete a Value” in chapter 11: Accessing Vault Using the Browser-Based UI

6. Disable the Secret Engine

Once you're done experimenting:

  1. Go to Secrets
  2. Find ui-dev in the list
  3. Click the three-dot menu (⋮)
  4. Click Disable

This will completely remove the secret engine and all the secrets under it.

Screenshot for “6. Disable the Secret Engine” in chapter 11: Accessing Vault Using the Browser-Based UI

  • Vault offers CLI, HTTP API, and UI interfaces.
  • The API is the most powerful and flexible.
  • The UI is useful for quick access and exploration but doesn’t support every feature.
  • You can disable the UI in production for tighter security.
  • We practiced enabling and managing secrets visually using the KV v2 engine.

Even though the UI is convenient, remember that anything done through the UI can also be done via API calls—this is important when scaling up or automating Vault in real systems.