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: Use Emby API key #2045

Closed
mousey opened this Issue Jun 10, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@mousey

mousey commented Jun 10, 2016

Hi All,

In the Emby Library Update plugin, rather than have the user save a Username and Password in the beets config file could beets not use an API key instead?

To me this is more practical than storing my credentials with a 3rd party, it means that if anything untoward happened I only need to reset the API Key inside Emby.

An example of this method can be seen in the Sonarr application. Where the API Key is supplied as the Media Browser Token without needing to check a users Username and Password first:

private string ProcessRequest(HttpRequest request, MediaBrowserSettings settings)
        {
            request.Headers.Add("X-MediaBrowser-Token", settings.ApiKey);
            var response = _httpClient.Post(request);
            _logger.Trace("Response: {0}", response.Content);
            CheckForError(response);
            return response.Content;
        }

@sampsyo sampsyo changed the title from Emby API Key to embyupdate: Use Emby API key Jun 11, 2016

@sampsyo sampsyo added the feature label Jun 11, 2016

@sampsyo

This comment has been minimized.

Show comment
Hide comment
@sampsyo

sampsyo Jun 11, 2016

Member

Good idea!

Member

sampsyo commented Jun 11, 2016

Good idea!

@mousey

This comment has been minimized.

Show comment
Hide comment
@mousey

mousey Jul 6, 2016

#2117 hopefully this will work correctly. User would need to add an apikey value to their config file. If they don't the plugin should still work with the old password method

mousey commented Jul 6, 2016

#2117 hopefully this will work correctly. User would need to add an apikey value to their config file. If they don't the plugin should still work with the old password method

@sampsyo sampsyo closed this in efe6542 Jul 21, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment