There was an error while loading. Please reload this page.
Add the client compatibility matrix [#1115] Three places claimed Quick Connect support with no supporting detail, and one of them pointed a reader at the Installation page for "client (Quick Connect) support", which that page does not carry. The narrative already existed on Login Flow; what was missing was which client is which. The mechanism column is read from Jellyfin's own Quick Connect client-support table and is attributed to it, because it is upstream's statement about upstream's clients rather than something measured here. The status column is this project's and says only what has been exercised: the browser redirect round trip, which the end-to-end harness drives against real identity providers. Every Quick Connect row is "not yet verified", which is the honest cell for a round trip the release checklist carries as a manual item and nobody has recorded. The page also says which clients can only LOG IN with Quick Connect and cannot approve a code for another device, because on an SSO-only server that decides whether a TV app can bootstrap itself without a phone or a desktop nearby.