Skip to content

Update audit-logging.mdx #291

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Feb 24, 2025
Merged

Update audit-logging.mdx #291

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c2e2b73
Update audit-logging.mdx
kbrwn Dec 23, 2024
3bfe635
Update description
samkim Feb 22, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 13 additions & 1 deletion pages/authzed/concepts/audit-logging.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,7 +76,7 @@ This is an example policy that grants the necessary permissions to write to a Fi
"Resource": "EXAMPLE_FIREHOSE_ARN"
}
]
}
}
```

[Kinesis]: https://aws.amazon.com/kinesis
Expand Down Expand Up @@ -126,3 +126,15 @@ Using the web dashboard, navigate to the Permission System's settings page to fi

Audit logging is configured using command-line flags.
See the full list of flags in the [Extenders section](extenders#flags).

### Tokens in Audit Logs

To identify which token was used for a request, look up its SHA-256 hash in the audit log's metadata.
Each request's `token_hash` field contains the hashed value of the original token used.

Example of generating a SHA-256 hash:

```bash
$ python3 -c "import hashlib; print(hashlib.sha256('<authzed-token>'.encode()).hexdigest())"
> 2ffb5caf16962e4371bc036d8de2a99dfcea1ae70091ef2953d633a88d05321a
```
Loading