by acroyear » Wed Feb 05, 2020 3:01 am
The authentication issue I wrote about 2 years ago still stands as being a larger-scale blocker. So long as the authentication is not oauth2 based, a skill can't access your data to try to interpret it through search mechanisms. For someone to write a wrapper around the server that could remember your username/password and produce it when authenticated by your amazon login (or any other oauth provider like google, apple/itunes, twitter, facebook, a few dozen others), you would have to trust the service provider that was caching it.
So there's 2 sides to getting working. One technical (someone needs to write the oauth wrapper that can produce your password for the subsonic API once you start using the authenticated device). The other more philosophical: will you trust your passwords to this service, because it can't be something you can host yourself. There's no way to make the password encrypted that the provider of the service can't decrypt, because it HAS to be decrypted in order for the skill code to use it to access the API endpoints.
--
Joe Shelby
http://subfiresuite.com/
http://subfireplayer.net/