fix: switch jellyfin to use non-deprecated auth mechanism #707
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
imnotjames
changed the title
mvdkleijn
reviewed
Feb 28, 2024
imnotjames
force-pushed
the
fix/jellyfin-use-new-auth
branch
from
a7c0311 to
eff0232
Compare
imnotjames
force-pushed
the
fix/jellyfin-use-new-auth
branch
from
eff0232 to
23ee00d
Compare
|
@imnotjames Happy with merging it without the client version number? |
Yeah, I can't seem to find any reasonable way to fetch it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
fixes #669
switches the authentication mechanism to be the non-deprecated
Authorizationheaderhttps://gist.github.com/nielsvanvelzen/ea047d9028f676185832e51ffaf12a6f
as part of this, switches the jellyfin connectivity test to use
inforather thaninfo/publicbecauseinfo/publicignores all auththis works against a live jellyfin server using the official jellyfin docker image