-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
embyupdate: Allow direct configuration of user ID for private users #4402
Labels
feature
features we would like to implement
Comments
sampsyo
changed the title
embyupdate.py does not work if admin user is private
embyupdate: Allow direct configuration of user ID for private users
Jul 7, 2022
Sounds very reasonable! Any chance you could try putting together a PR to show how this would work? |
I happened to encounter this recently. I'm happy to submit a PR for this. |
shoriminimoe
added a commit
to shoriminimoe/beets
that referenced
this issue
Aug 26, 2023
Adds a `userid` config option for the `embyupdate` plugin. When the `userid` is provided, the Emby user lookup is bypassed. This avoids a failure to get the user ID for private users. Closes: beetbox#4402
3 tasks
Louson
pushed a commit
to Louson/beets
that referenced
this issue
Sep 26, 2023
Adds a `userid` config option for the `embyupdate` plugin. When the `userid` is provided, the Emby user lookup is bypassed. This avoids a failure to get the user ID for private users. Closes: beetbox#4402
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the embyupdate.py plugin, if the admin user listed in the beets config is hidden from login screens, the embyupdate plugin will fail and not find the username.
I am using an API key, which is server wide so the username does not really matter. Therefore the get_user function should just return the user provided in the beets config
We should also allow for the emby user ID (string/hash) to be supplied directly from the beets config to avoid this situation.
can this change be made please?
The text was updated successfully, but these errors were encountered: