Add audit logging for authentication tokens
Open
Nobody has claimed this yet.
1. to develop
enhancement
feature: admin audit
feature: authentication
security
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
We should add audit loggings at least for the following events:
- Creating tokens
- Revoking tokens
- Scope changes
- Renames
- Marking the token to be wiped
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
Start by tracing the authentication-token lifecycle in the server and review the linked HackerOne report for the security context. Done means audit logging covers token creation, revocation, scope changes, renames, and marking a token to be wiped; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authentication, backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100