Migrate auth + data fetching to client-side (keycloak-js + PKCE) #54
Labels
No labels
domain:backend
domain:devops
domain:frontend
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo_admin/pal-e-docs-app#54
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Type
Feature
Lineage
Implements #52. Depends on convention-sveltekit-spa (issue #51).
Repo
forgejo_admin/pal-e-appUser Story
As pal-e-app I want to authenticate via keycloak-js + PKCE and fetch data client-side with Bearer tokens so that I have no server secrets and work as a true SPA.
Context
pal-e-app currently uses Auth.js with server-side Keycloak OIDC sessions and loads all data via +page.server.ts files. This migration converts to keycloak-js client-side auth and client-side fetch() with Bearer tokens, following the proven pattern from mcd-tracker-app. Full spec in #52.
File Targets
Create:
src/lib/keycloak.ts,src/lib/api-client.tsModify: All +page.svelte files, +layout.svelte, QuickJot.svelte
Remove: All +page.server.ts, src/auth.ts, hooks.server.ts, signin/, signout/, api/ routes, src/lib/api.ts
Acceptance Criteria
Test Expectations
npm run checkpasses (no type errors)npm run buildsucceedsConstraints
Checklist
Related