upstream/vault
1
0
Fork 0
mirror of https://github.com/hashicorp/vault.git synced 2026-06-08 16:24:51 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 9

Update OIDC docs (#9599)

Browse source 
Clarify that verbose logging is to the server logs.
This commit is contained in:
Jim Kalafut 2020-07-27 08:51:59 -07:00 committed by GitHub
parent 2897ec67e1
commit f145c66d22
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
website/pages/docs/auth/jwt.mdx
View file

@ -230,7 +230,7 @@ EOF
`cat jwt.json | jq -r .access_token | cut -d. -f2 | base64 -D`
- As of Vault 1.2, the [`verbose_oidc_logging`](/api/auth/jwt#verbose_oidc_logging) role
option is available which will log the received OIDC token if debug-level logging is enabled. This can
option is available which will log the received OIDC token to the _server_ logs if debug-level logging is enabled. This can
be helpful when debugging provider setup and verifying that the received claims are what you expect.
Since claims data is logged verbatim and may contain sensitive information, this option should not be
used in production.