Delivers optional account authentication across Liqa while preserving the existing unauthenticated default.
Adds migrated user and token-revocation storage, cookie and bearer sessions, protected REST/MCP/run-event routes, and operator account/token commands.
Adds browser login, safe session recovery and logout, including authenticated run-event notifications and accessible login states.
Documents opt-in configuration and operations, and adds integrated coverage for provisioning through authentication, run events, logout, deletion and migration persistence.
Validation
All implementation children (#52–#57) are complete with task-specific independent QA evidence attached in Vikunja. Their child MRs #1–#6 were human-merged into the fork integration branch. The browser flow was verified on both same-origin production and the supported Vite setup; the integration journey verifies REST, MCP, events, logout/deletion rejection and migration persistence.
Upstream target base at preparation: d4bb2749828b7a28f787bbd1d611a63eccb2d861
## Summary
Delivers optional account authentication across Liqa while preserving the existing unauthenticated default.
- Adds migrated user and token-revocation storage, cookie and bearer sessions, protected REST/MCP/run-event routes, and operator account/token commands.
- Adds browser login, safe session recovery and logout, including authenticated run-event notifications and accessible login states.
- Documents opt-in configuration and operations, and adds integrated coverage for provisioning through authentication, run events, logout, deletion and migration persistence.
## Validation
All implementation children (#52–#57) are complete with task-specific independent QA evidence attached in Vikunja. Their child MRs #1–#6 were human-merged into the fork integration branch. The browser flow was verified on both same-origin production and the supported Vite setup; the integration journey verifies REST, MCP, events, logout/deletion rejection and migration persistence.
- Epic and child records: https://vikunja.hq.ars9.space/tasks/50
- Server auth QA: https://vikunja.hq.ars9.space/tasks/52
- CLI QA report: https://vikunja.hq.ars9.space/api/v2/tasks/53/attachments/24
- Revocation cleanup QA report: https://vikunja.hq.ars9.space/api/v2/tasks/54/attachments/7
- Browser QA reports: https://vikunja.hq.ars9.space/api/v2/tasks/55/attachments/20 and https://vikunja.hq.ars9.space/api/v2/tasks/55/attachments/23
- Documentation QA report: https://vikunja.hq.ars9.space/api/v2/tasks/56/attachments/25
- Integration QA report: https://vikunja.hq.ars9.space/api/v2/tasks/57/attachments/26
## References
- Source issue: https://git.hq.ars9.space/ars9/liqa/issues/15
- Child MRs: https://git.hq.ars9.space/agent-codex/liqa/pulls/1, https://git.hq.ars9.space/agent-codex/liqa/pulls/2, https://git.hq.ars9.space/agent-codex/liqa/pulls/3, https://git.hq.ars9.space/agent-codex/liqa/pulls/4, https://git.hq.ars9.space/agent-codex/liqa/pulls/5, https://git.hq.ars9.space/agent-codex/liqa/pulls/6
- Fork source head: `ff9a700c8666abf7b9c4f113c94462bf97f6eae2`
- Upstream target base at preparation: `d4bb2749828b7a28f787bbd1d611a63eccb2d861`
- Add account, JWT session, revocation, cookie and bearer handling.
- Protect server surfaces while preserving public health, manifest and disabled mode.
- Add SQLite migration and focused server regression coverage.
- Exercise CLI provisioning through browser/API/MCP auth, run events, logout, and deletion.
- Allow integration coverage to reopen the same file-backed test database.
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.
Summary
Delivers optional account authentication across Liqa while preserving the existing unauthenticated default.
Validation
All implementation children (#52–#57) are complete with task-specific independent QA evidence attached in Vikunja. Their child MRs #1–#6 were human-merged into the fork integration branch. The browser flow was verified on both same-origin production and the supported Vite setup; the integration journey verifies REST, MCP, events, logout/deletion rejection and migration persistence.
References
ff9a700c8666abf7b9c4f113c94462bf97f6eae2d4bb2749828b7a28f787bbd1d611a63eccb2d861