github/pinniped
1
0
Fork 0
mirror of https://github.com/vmware-tanzu/pinniped.git synced 2026-02-14 18:10:17 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix typo in audit-logging.md

Browse Source
This commit is contained in:
Ryan Richard
2024-11-21 11:02:45 -08:00
committed by Joshua Casey
parent 54b35c30da
commit 51ae782135
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
site/content/docs/reference/audit-logging.md
View File

@@ -477,8 +477,8 @@ of this specific token to other systems.
Finally, that ID token is submitted to the workload cluster's Concierge to get a temporary credential which
grants access to that workload cluster. In those logs below, you can see how the `tokenID` can be used
to follow the user's session to another cluster by following the token. This `TokenCredentialRequest` endpoint
s a Kubernetes API, so the `auditID` value from the Concierge pod logs will match the `auditID` value in
the Kubernetes audit logs, allowing them to be correlated.
is a Kubernetes API, so the `auditID` value from the Concierge pod logs will match the `auditID` value in
the Kubernetes audit logs for the same request, allowing them to be correlated.
```json lines
{
@@ -510,6 +510,8 @@ the Kubernetes audit logs, allowing them to be correlated.
As we've seen, a user's entire authentication journey across clusters can be followed by using the
`auditID`, `authorizeID`, `sessionID`, and `tokenID` correlation values to find related audit log events.
The same correlation values could be used to trace a user's journey both forwards and backwards in time
through the logs.
## Watching the audit logs