Archived
Run the real Carl UI with Authentik and retained private household data #4
No Assignees
No due date set.
Dependencies
No dependencies set.
Reference: KofTwentyTwo/carl#4
Reference in new issue
Block a user
Bring up Carl's normal branded QQQ UI against its retained private database with an actual Authentik client and explicitly approved verified account mapping. The owner selects their own account as initial administrator; exact verified subject binding must come from the real identity service. The dedicated Carl client has not yet been created.
The configured Authentik service and existing cluster administration endpoint are currently unreachable from the workstation. Restore authorized connectivity, provision Carl's dedicated client with supported redirects/scopes, configure protected secrets privately, and bind the approved identity through current household/domain permissions. Recheck private record ownership/grants before exposing imported data.
Acceptance: actual authenticated login/logout, real navigation/dashboards/import review over the same retained domain state, negative/unmapped/revoked access checks, and truthful configured model/provider state. Do not use fixture sign-in, fabricated household records, test-provider endpoints or scripted AI responses as the working UI. Real model connection and provider qualification remain separately required.
No personal data, identity subjects, credentials or private infrastructure addresses should be posted in this issue. Carl application setup belongs here; any independently reproduced generic authentication/runtime defect belongs upstream.