Skip to content

Commit

Permalink
approle naming syntax documentation (#19369)
Browse files Browse the repository at this point in the history
Documentation does not currently detail the accepted naming scheme for approle roles, this aims to provide clarity based on customer feedback. https://github.com/hashicorp/vault/blob/main/sdk/framework/path.go#L16-L18 details the regex used.
  • Loading branch information
rowansmithhc committed Feb 27, 2023
1 parent d35be2d commit 538bb79
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion website/content/api-docs/auth/approle.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,8 @@ enabled while creating or updating a role.

### Parameters

- `role_name` `(string: <required>)` - Name of the AppRole. Must be less than 4096 bytes.
- `role_name` `(string: <required>)` - Name of the AppRole. Must be less than 4096 bytes, accepted characters
include a-Z, 0-9, space, hyphen, underscore and periods.
- `bind_secret_id` `(bool: true)` - Require `secret_id` to be presented when
logging in using this AppRole.
- `secret_id_bound_cidrs` `(array: [])` - Comma-separated string or list of CIDR
Expand Down

0 comments on commit 538bb79

Please sign in to comment.