pastilhasandClaude Fable 5
05e11f81c9
Provisioning already created each member's Jellyfin account and signed in as them to get a token — its own header says the token exists so "the person's Officer session can already read their library". It was then dropped, because linkJellyfinAccount had nowhere to put it. So every non-owner resolved to no config and got a 503 setup form, asking them to connect a Jellyfin server with a password nobody knows. It reads as a permissions fault and is not one: the grant, the role and the account list were all correct. jellyfin_accounts now carries access_token and device_id, getConfig falls back to the link row when the caller has no registry of their own, and there is no path from there to the owner's token — a member resolving to the owner's credential would read the owner's watch state and every library. POST /_config/:id/provision repairs accounts linked before the column existed. It resets the password to mint, which is free on an account Officer created (random, discarded, known to nobody) and destructive on an adopted one, so adopted accounts are skipped unless includeAdopted says otherwise. Applied on alpha: conceiba and guipinto minted and verified against the live server; fedra and diogo skipped as adopted. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
20 lines
463 B
TypeScript
20 lines
463 B
TypeScript
export {
|
|
listJellyfinServers,
|
|
getActiveJellyfinCredentials,
|
|
getLinkedJellyfinCredentials,
|
|
getJellyfinCredentials,
|
|
createJellyfinServer,
|
|
updateJellyfinServer,
|
|
setActiveJellyfinServer,
|
|
deleteJellyfinServer,
|
|
recordJellyfinProbe,
|
|
} from './queries';
|
|
|
|
export {
|
|
listJellyfinAccounts,
|
|
linkJellyfinAccount,
|
|
setJellyfinAccountToken,
|
|
unlinkJellyfinAccount,
|
|
} from './queries';
|
|
export type { JellyfinServer, JellyfinCredentials } from './queries';
|