open-vault/website/source/api/system/config-ui.html.md

124 lines
2.7 KiB
Markdown
Raw Normal View History

---
layout: "api"
page_title: "/sys/config/ui - HTTP API"
New Docs Website (#5535) * conversion stage 1 * correct image paths * add sidebar title to frontmatter * docs/concepts and docs/internals * configuration docs and multi-level nav corrections * commands docs, index file corrections, small item nav correction * secrets converted * auth * add enterprise and agent docs * add extra dividers * secret section, wip * correct sidebar nav title in front matter for apu section, start working on api items * auth and backend, a couple directory structure fixes * remove old docs * intro side nav converted * reset sidebar styles, add hashi-global-styles * basic styling for nav sidebar * folder collapse functionality * patch up border length on last list item * wip restructure for content component * taking middleman hacking to the extreme, but its working * small css fix * add new mega nav * fix a small mistake from the rebase * fix a content resolution issue with middleman * title a couple missing docs pages * update deps, remove temporary markup * community page * footer to layout, community page css adjustments * wip downloads page * deps updated, downloads page ready * fix community page * homepage progress * add components, adjust spacing * docs and api landing pages * a bunch of fixes, add docs and api landing pages * update deps, add deploy scripts * add readme note * update deploy command * overview page, index title * Update doc fields Note this still requires the link fields to be populated -- this is solely related to copy on the description fields * Update api_basic_categories.yml Updated API category descriptions. Like the document descriptions you'll still need to update the link headers to the proper target pages. * Add bottom hero, adjust CSS, responsive friendly * Add mega nav title * homepage adjustments, asset boosts * small fixes * docs page styling fixes * meganav title * some category link corrections * Update API categories page updated to reflect the second level headings for api categories * Update docs_detailed_categories.yml Updated to represent the existing docs structure * Update docs_detailed_categories.yml * docs page data fix, extra operator page remove * api data fix * fix makefile * update deps, add product subnav to docs and api landing pages * Rearrange non-hands-on guides to _docs_ Since there is no place for these on learn.hashicorp, we'll put them under _docs_. * WIP Redirects for guides to docs * content and component updates * font weight hotfix, redirects * fix guides and intro sidenavs * fix some redirects * small style tweaks * Redirects to learn and internally to docs * Remove redirect to `/vault` * Remove `.html` from destination on redirects * fix incorrect index redirect * final touchups * address feedback from michell for makefile and product downloads
2018-10-19 15:40:11 +00:00
sidebar_title: "<tt>/sys/config/ui</tt>"
sidebar_current: "api-http-system-config-ui"
description: |-
The '/sys/config/ui' endpoint configures the UI.
---
# `/sys/config/ui`
The `/sys/config/ui` endpoint is used to configure UI settings.
- **`sudo` required**  All UI endpoints require `sudo` capability in
addition to any path-specific capabilities.
## Read UI Settings
This endpoint returns the given UI header configuration.
| Method | Path | Produces |
| :------- | :--------------------------- | :--------------------- |
| `GET` | `/sys/config/ui/headers/:name` | `200 application/json` |
### Parameters
- `name` `(string: <required>)`  The name of the custom header.
### Sample Request
```
$ curl \
--header "X-Vault-Token: ..." \
http://127.0.0.1:8200/v1/sys/config/ui/headers/X-Custom-Header
```
### Sample Response
```json
{
"value": "custom-value"
}
```
## Configure UI Headers
This endpoint allows configuring the values to be returned for the UI header.
| Method | Path | Produces |
| :------- | :--------------------------- | :--------------------- |
| `PUT` | `/sys/config/ui/headers/:name` | `204 (empty body)` |
### Parameters
- `name` `(string: <required>)`  The name of the custom header.
- `values` `(list: <required>)` - The values to be returned from the header.
### Sample Payload
```json
{
"values": ["custom value 1", "custom value 2"]
}
```
### Sample Request
```
$ curl \
--header "X-Vault-Token: ..." \
--request PUT \
--data @payload.json \
http://127.0.0.1:8200/v1/sys/config/ui/headers/X-Custom-Header
```
## Delete a UI Header
This endpoint removes a UI header.
| Method | Path | Produces |
| :------- | :--------------------------- | :--------------------- |
| `DELETE` | `/sys/config/ui/headers/:name`| `204 (empty body)` |
### Sample Request
```
$ curl \
--header "X-Vault-Token: ..." \
--request DELETE \
http://127.0.0.1:8200/v1/sys/config/ui/headers/X-Custom-Header
```
## List UI Headers
This endpoint returns a list of configured UI headers.
| Method | Path | Produces |
| :------- | :--------------------------- | :--------------------- |
| `LIST` | `/sys/config/ui/headers` | `200 application/json` |
### Sample Request
```
$ curl \
--header "X-Vault-Token: ..." \
--request LIST \
http://127.0.0.1:8200/v1/sys/config/ui/headers
```
### Sample Response
```json
{
"data":{
"keys":[
"X-Custom...",
"X-Header...",
]
}
}
```