Visual theme and sign-in with Authentik #19
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
MassiveDynamic/kataba!19
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "development"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #16
Closes #4
Summary
Theme (#16, ADR-0010): semantic Tailwind tokens with light/dark, a Light/Dark/System switch stored in a cookie, logo and icons, Inter, Lucide, and tiles for categories and guides.
Sign-in (#4, ADR-0009): Auth.js with Authentik and JWT sessions. The role is derived from the groups claim at each sign-in, and permission checks read it from the database.
Evidence
src/auth/role.test.ts. Admin wins over author; a user in neither group is a viewer. A missing or malformed claim and an unset group variable both grant nothing.error parsing connection string, format must be 'mariadb://…'After: the sign-in round trip against Authentik completes. The User row is saved with the role derived from groups, and the name and Sign out show in the Titlebar.
tsc,eslint, 19/19 tests pass.next build:/remains a partial prerender, with the account area streamed in.Merge Danger
Door: two-way, apart from the migration
The migration creates the
Usertable. Rolling back the code is cheap, but the table and the users in it remain.Blast Radius: deployment
The deployment needs
AUTH_SECRET,AUTH_AUTHENTIK_*,KATABA_*_GROUP, andprisma migrate deploy. The Authentik app must allow<origin>/api/auth/callback/authentikas a redirect URI. Open follow-ups:🤖 Generated with Claude Code