7 Commits

Include renames

Author	SHA1	Message	Date
raucao	faa7bf6146	Revoke device authorizations in place with Turbo Streams ... Revoking a device redirected away from the storage dashboard, which closed the details modal and reloaded the page. Refreshing the affected parts instead keeps the modal open and shows the change where it happened. - Extract the card and the modal's access list into their own components, so either can be re-rendered without touching the modal's open state, and share the group summaries between the components - Derive the app's DOM ids from its client_id (the grouping key) and the device row ids from the authorization, through one helper used by both the templates and the controller - Revoke one of several devices as a Turbo Stream: remove the row and refresh the card behind the modal and the access list - Revoke an app's last device with a redirect, so the dashboard re-renders itself and grouping, sorting and the empty state stay in one place - Fade the removed row out, deferring Turbo's own removal until the animation has ended Part of #254	2026-11-03 17:45:37 +04:00
raucao	f2248ea744	Rework storage dashboard and fix authorization revocation ... - One card per app (grouped by client_id) showing distinct device and category counts; the whole card opens the details modal (with hover and focus highlight) instead of a separate Details button - Details modal: access list styled like the OAuth consent dialog via a shared RsScopeListComponent, plus per-token device, connected date and expiry, each with its own Revoke - "folder" -> "category" in the card, modal, consent dialog and the auth-created notification - Make revoke a real DELETE: it was a GET link that Turbo 8's prefetch-on-hover fired on its own, silently deleting authorizations. Missing or foreign authorizations now return 404 instead of 500. - Move "Launch app" to the app level (GET /services/storage/apps/:client_id/launch); no token id in the URL Part of #254	2026-11-03 12:00:39 +04:00
raucao	eeb399ff83	Document the storage-first launch flow ... Add an explicit spec for the storage-first handoff (remoteStorage spec section 11): launching an app passes only `#remotestorage=<address>`, never an access token. The app then runs the application-first (now PKCE-capable) flow itself. Part of #254	2026-11-03 11:59:51 +04:00
raucao	8fae099c12	Gate remoteStorage by serviceEnabled instead of Flipper ... The admin "Default services" setting writes the LDAP serviceEnabled attribute, but remoteStorage access was also gated behind an unused per-user Flipper flag that nothing ever enabled, so remoteStorage was inaccessible for everyone. Gate remoteStorage on service_enabled? like the other services, and make the admin toggle reflect the LDAP attribute (this also fixes it reading current_user instead of the user being viewed). E-Mail keeps its Flipper gate for now.	2026-10-06 15:10:00 +02:00
raucao	dbbf116c52	Fix RS storage-first auth work in dev, remove token ... See https://github.com/remotestorage/remotestorage.js/issues/900	2025-05-16 15:59:40 +04:00
raucao	ee5c6d86d0	Port RS auth job removal to Solid Queue	2025-05-05 11:07:30 +04:00
Râu Cao	aa399b862a	Allow to launch RS apps from dashboard	2023-11-19 19:10:13 +01:00