Fix Jellyfin authentication for modern installations #6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Autosync fails to refresh Jellyfin libraries when
EnableLegacyAuthorizationis disabled, which is the default setting in modern Jellyfin installations.Root Cause
Autosync uses the legacy
X-MediaBrowser-Tokenheader inherited from Emby. Modern Jellyfin requires theAuthorization: MediaBrowser Token="<key>"header format when legacy auth is disabled.Solution
Updated
JellyfinServer.scan_path(),MediaServerScanner._scan_jellyfin(), and the test connection endpoint to use the modern authentication header format per the official Jellyfin API documentation.Testing
EnableLegacyAuthorization=false(default)EnableLegacyAuthorization=true(backward compatible)Backward Compatibility
The modern header format is accepted by Jellyfin regardless of the legacy auth setting, ensuring backward compatibility.
Reference
Official Jellyfin API Authentication documentation: https://gist.github.com/nielsvanvelzen/ea047d9028f676185832e51ffaf12a6f