* docs: correct auth jwt role requirements
* remove upgrade guide to be added in separate PR
* Revert "remove upgrade guide to be added in separate PR"
This reverts commit 6554d3ff63623a329b0d93f7143d95cd3f19b3e6.
* update required details for bound audience
* Apply suggestions from code review
Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>
* fix formatting to match the existing format of the file
* add 1.16 known issues
* add 1.17 upgrade guide note
---------
Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>
* add adfs link
* add adfs and update index
add the adfs link in the index.mdx
add the file adfs.mdx
* Update docs-nav-data.json
Add the link to ADFS documentation
* add adfs-oidc-ldapgroupoption.png
image for the documentation adfs.mdx
* Update docs-nav-data.json
Updated from the last version of the file and adding adfs link
* suggested edits
* Update the file adfs.mdx
* Update adfs.mdx
Change auth/adfs/config to auth/<YOUR_OIDC_MOUNT_PATH>/config
* Update website/content/docs/auth/jwt/oidc-providers/adfs.mdx
* Corrected typo adfs.mdx
We had 2x step3 so I changed to have step 3 and step 4
---------
Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>
Co-authored-by: Yoko Hyakuna <yoko@hashicorp.com>
* add docs for configuring jwt validation pubkeys for vso and update jwt auth docs to mention key rotation
Co-authored-by: Tom Proctor <tomhjp@users.noreply.github.com>
* Update JWT docs to not recommend `-path` for `vault write
`-path` is valid for `vault login`, but not for `vault write` leading to confusion when trying to log in to using the JWT backend using the CLI.
* Update website/content/docs/auth/jwt/index.mdx
---------
Co-authored-by: tjperry07 <tjperry07@users.noreply.github.com>
Co-authored-by: Violet Hynes <violet.hynes@hashicorp.com>
* docs/oidc: change user type recommendation for Google workspace integration
* Update website/content/docs/auth/jwt/oidc-providers/google.mdx
Co-authored-by: Calvin Leung Huang <1883212+calvn@users.noreply.github.com>
The operations are handled identically, but ~85% of the references were
POST, and having a mix of PUT and POST was a source of questions.
A subsequent commit will update the internal use of "PUT" such as by
the API client and -output-curl-string.
* Rework 1.21 content into one heading and add note at top
* Add notes about extended k8s token duration
* Add example of ClusterRoleBinding for using client JWTs
* website: bump to docs-page prerelease, support hidden pages
* website: switch to hidden pages approach for docs and api-docs
* website: remove temporary fix for hidden pages, and related check
* website: fix content structure issue with docs/auth/jwt
* website: bump to latest pre-release
* website: bump to stable docs-page, w next-mdx-remote bump
* website: bump to latest markdown-page
