-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Update Docs For Bound Audience Explanation #30519
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
Conversation
CI Results: |
Build Results: |
c08640f
to
3c4c325
Compare
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.
LGTM, if we remove the changelog entry.
FYI: you can skip all the Vault CI checks if you prefix your git branch with docs/
.
Sounds good. I'll keep that in mind for the next doc update. Added the "no changelog" entry for this PR for now. |
Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>
Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>
* update docs for more clarity around bound audiences * more updates * update changelog * Delete changelog/30519.txt * Update website/content/docs/auth/jwt/index.mdx Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com> * Update website/content/api-docs/auth/jwt.mdx Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com> --------- Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>
* update docs for more clarity around bound audiences * more updates * update changelog * Delete changelog/30519.txt * Update website/content/docs/auth/jwt/index.mdx Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com> * Update website/content/api-docs/auth/jwt.mdx Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com> --------- Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>
* update docs for more clarity around bound audiences * more updates * update changelog * Delete changelog/30519.txt * Update website/content/docs/auth/jwt/index.mdx * Update website/content/api-docs/auth/jwt.mdx --------- Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>
* update docs for more clarity around bound audiences * more updates * update changelog * Delete changelog/30519.txt * Update website/content/docs/auth/jwt/index.mdx Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com> * Update website/content/api-docs/auth/jwt.mdx Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com> --------- Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>
* update docs for more clarity around bound audiences * more updates * update changelog * Delete changelog/30519.txt * Update website/content/docs/auth/jwt/index.mdx Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com> * Update website/content/api-docs/auth/jwt.mdx Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com> --------- Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>
Description
This PR updates our JWT documentation to clearly specify that the bound audience must exactly match the bound claim stored in Vault for successful authentication when using the JWT login method.
TODO only if you're a HashiCorp employee
backport/
label that matches the desired release branch. Note that in the CE repo, the latest release branch will look likebackport/x.x.x
, but older release branches will bebackport/ent/x.x.x+ent
.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.