Bug Summary:
After enabling the audit log feature only events related to chats, and settings are written to the audit log. The audit log should include any action from the user that touches an API endpoint.
Originally created by @gaby on GitHub (Mar 5, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/11196
# Bug Report
---
## Installation Method
Docker
## Environment
- **Open WebUI Version:** 0.5.18
- **Operating System:** Ubuntu
- **Browser (if applicable):** Chrome
**Confirmation:**
- [ ] I have read and followed all the instructions provided in the README.md.
- [ ] I am on the latest version of both Open WebUI and Ollama.
- [ ] I have included the browser console logs.
- [ ] I have included the Docker container logs.
- [ ] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.
## Expected Behavior:
The audit log introduced in https://github.com/open-webui/open-webui/pull/10860 should include auth events. For example: success login, failed login, logout
## Actual Behavior:
Auth events never show in the log
## Description
**Bug Summary:**
After enabling the audit log feature only events related to chats, and settings are written to the audit log. The audit log should include any action from the user that touches an API endpoint.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @gaby on GitHub (Mar 5, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/11196
Bug Report
Installation Method
Docker
Environment
Confirmation:
Expected Behavior:
The audit log introduced in https://github.com/open-webui/open-webui/pull/10860 should include auth events. For example: success login, failed login, logout
Actual Behavior:
Auth events never show in the log
Description
Bug Summary:
After enabling the audit log feature only events related to chats, and settings are written to the audit log. The audit log should include any action from the user that touches an API endpoint.