VoxCommando

Help and Support (Using VoxCommando) => Bug Reports => Topic started by: leepingdiablo on April 18, 2020, 03:24:51 PM

Title: JRiver authentication failure
Post by: leepingdiablo on April 18, 2020, 03:24:51 PM
Hello,

I'm a new user and having a problem authenticating with JRiver Media Center 26 (the latest version).

The username and password (and the connection test) work OK. The problem is how the JRiver token is handed internally by the Vox Commando plugin.

Observe that the token value returned by JRiver is 8 characters long:

GET http://htpc:52199/MCWS/v1/Authenticate (http://htpc:52199/MCWS/v1/Authenticate)

<Response Status="OK">
<Item Name="Token">gN8Qq6iX</Item>
<Item Name="ReadOnly">0</Item>
<Item Name="PreLicensed">0</Item>
</Response>


From the JRiver logs, however, the Token value given by Vox Commando is 10 characters long, padded out with 2 extra zero characters: 00.

0007922: 14052: Sharing Plugins: CHTTPListenerWorker::HandleRequest: TCP: 127.0.0.1: GET: http://localhost:52199/MCWS/v1/Authenticate (http://localhost:52199/MCWS/v1/Authenticate)
0007922: 14052: Sharing Plugins: JRWebService::Process: Start
0007922: 14052: Sharing Plugins: JRWebService::Process: URL: /MCWS/v1/Authenticate
0007922: 14052: Sharing Plugins: JRWebService::Process: Finish (0 ms)
0007922: 14052: Sharing Plugins: VHTTPMessage::Write: Wrote 198 bytes
0007922: 14052: Sharing Plugins: CHTTPListenerWorker::HandleRequest: TCP: 127.0.0.1: GET: http://localhost:52199/MCWS/v1/Playlists/List?Token=gN8Qq6iX00 (http://localhost:52199/MCWS/v1/Playlists/List?Token=gN8Qq6iX00)
0007922: 14052: Sharing Plugins: VHTTPMessage::Write: Wrote 0 bytes
0007922: 14052: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)


This fails with a 401 Unauthorized so no XML data can be transferred.

I tried digging around in the plugin's configuration but I think the bug is hard-coded in a binary. Thanks for your help!
Title: Re: JRiver authentication failure
Post by: jitterjames on April 18, 2020, 07:03:57 PM
Hi leepingdiablo.

Welcome to the VoxCommando Forum.

Thanks for bringing this to my attention.  I don't use JRiver personally and the plugin was developed quite some time ago.

I'm guessing that something has probably changed in the JRiver api in one of the updates they've made over the years.

I'll look into it and see what I can do to fix it.
Title: Re: JRiver authentication failure
Post by: jitterjames on April 19, 2020, 12:31:02 PM
I think you were right about the extra characters.  The format of the authentication XML must have changed and it was no longer parsing properly.

Please try to replace the JRiver dll found in Voxcommando\plugins\JRiver folder with the attached file and let me know if it works for you.

Also see notes on replacing VC DLL with downloaded versions:
https://voxcommando.com/mediawiki/index.php?title=Unblock_DLL
Title: Re: JRiver authentication failure
Post by: leepingdiablo on April 19, 2020, 05:53:11 PM
That did the trick, jitterjames. Thank you!