Join GitHub today
embyupdate: Use Emby API key #2045
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: