Support API key authentication #23
Merged
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
|
Please merge this code in soon! The whole point of generating an API key is to use it. |
Support also authenticating with an API key -- since this is seperate from device tokens, choose to authenticate with one if a device name is not set. Fixes jellyfin#19
s-t-e-v-e-n-k
force-pushed
the
support-api-key-auth
branch
from
ecccf0c to
ef8b616
Compare
Sorry, I totally missed the merge conflict here, fixed that. |
iwalton3
approved these changes
Jan 21, 2024
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.
Support also authenticating with an API key -- since this is seperate from device tokens, choose to authenticate with one if a device name is not set.
Fixes #19