oxidecomputer / oxidecomputer/omicron
request log entries should include more authn, authz info
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
The top-level "info" log messages that we emit for completed HTTP requests should include:
- a list of authn schemes tried
- details about authn (what scheme was used; maybe the user's external_id? we already have the actor, which includes the silo user id and silo id)
- a list of authz checks completed and their results
This would make it much easier to debug authn/authz issues. This information is all already available in trace-level log entries but it's a pain to reconstruct.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the top-level info log messages emitted for completed HTTP requests, then trace the existing trace-level authn and authz log entries that contain the requested information. Define the fields and their contents from those existing entries, and verify that completed-request logs include the schemes tried, authentication details, and authorization results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, authentication, authorization, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100