-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make reception of an empty valid principals configurable based on a role flag. #28466
Conversation
…ole flag. Adds allow_empty_principals, which if true allows valid_principals on credential generation calls to be empty.
CI Results: |
Build Results: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
@@ -170,7 +170,9 @@ This endpoint creates or updates a named role. | |||
|
|||
~> **Note**: In FIPS 140-2 mode, the following algorithms are not certified | |||
and thus should not be used: `ed25519`. | |||
|
|||
- `allow_empty_principals` `(bool: false)` - Allow signing certificates with |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure if the absence of the empty line matters or not. The Vercel step was skipped by the PR build, so I couldn't verify it.
…rp/vault into sgm/allow_empty_principals_flag
Adds allow_empty_principals, which if true allows valid_principals on credential generation calls
to be empty.
Description
What does this PR do?
TODO only if you're a HashiCorp employee
to N, N-1, and N-2, using the
backport/ent/x.x.x+ent
labels. If this PR is in the CE repo, you should only backport to N, using thebackport/x.x.x
label, not the enterprise labels.of a public function, even if that change is in a CE file, double check that
applying the patch for this PR to the ENT repo and running tests doesn't
break any tests. Sometimes ENT only tests rely on public functions in CE
files.
in the PR description, commit message, or branch name.
description. Also, make sure the changelog is in this PR, not in your ENT PR.