Bugzilla – Bug 5887
JHB unresponsive after enabling password protection in SC7
Last modified: 2008-11-17 14:22:25 UTC
r727 cannot cope with SC7 enforcing username/password authentication. Network debugging messages show SC7 replying to Jive HTTP requests with status 401 --which is good and proper-- but there appears to be no way to configure the username & password for the JHB device, even after a factory reset.
Best bug candidate. Richard asks for Dean's comments on how this should be handled.
Dean, please comment on the UI needed.
To fix this we'll need to add a sequence of name and password entry screens on Jive when the HTTP request to SC is authenticated.
A quick glance at SlimDiscoveryApplet, Comet, HttpPool, and RequestHttp suggests that all those classes may need modification to support utilizing HTTP Basic authentication for requests to SC7. It looks like most APIs want multiple args to describe a server, e.g. jive.net.SocketHttp(jnt, "192.168.1.1", 9000, "slimserver") RequestHttp(sink, 'GET', 'http://192.168.1.1:9000/xml/status.xml') I think it might be cleaner to refactor those so that instead of host/IP and port, you'd pass objects representing known web servers. Setup would create a web server object in the jnt tables that represents the current SqueezeCenter host, so those method calls would look like -- nil means use the default web server (SC7 host) jive.net.SocketHttp(jnt, nil, "slimserver") -- added an arg. Again, nil means default SC7 host RequestHttp(sink, 'GET', nil, '/xml/status.xml') Using references to a new web server class would mean that, going forward, Jive wouldn't have to keep adding new args to HTTP-related methods in order to support additional options (https, timeouts, whatever else might be desired).
Punting on this to 7.0
FYI, the behavior has changed a bit. I had JHB/r1096 working fine with an SC7 install that did not have password auth enabled. I shut that instance down, started SC7 on another host with password auth on, and while the JHB was responsive, it found no players, and I could not use the Music Source settings menu. Just as I was going to file a new bug, I figured it might be related to this one. Disable password auth on SC7 and all's well w/ JHB.
It's unlikely this will make the 7.0 release, but we must fix this in 7.0.1.
Reset priority
*** Bug 7483 has been marked as a duplicate of this bug. ***
*** Bug 7541 has been marked as a duplicate of this bug. ***
Here are some logs from the Duet Receiver if you need them. Shiksa happens to be the slimserver on my network Mar 18 12:44:57 (none) user.info jive: (Comet.lua:589) - Comet {shiksa}: _handshake error: HTTP/1.1 401 Unauthorized Mar 18 12:44:57 (none) user.warn jive: (Comet.lua:890) - Comet {shiksa}: handleAdvice state=CONNECTING Mar 18 12:44:57 (none) user.info jive: (NetworkThread.lua:246) - NOTIFY cometDisconnected: Comet {shiksa}, 0 Mar 18 12:44:57 (none) user.info jive: (SlimServer.lua:398) - SlimServer {shiksa} disconnected Mar 18 12:44:57 (none) user.info jive: (NetworkThread.lua:246) - NOTIFY serverDisconnected: SlimServer {shiksa}, 0 Mar 18 12:44:57 (none) user.info jive: (Comet.lua:923) - Comet {shiksa}: advice is retry, connect in 3.626 seconds
What's the status on this one. I want to enable password protection for remote access, but still need to use my controller.
This is on my list of bugs to fix soon.
Fixed in jive 7.0.1 r2281. At the moment this does not check if the username/password have been entered correctly, I have opened bug 7879 to fix this in a future release.
I'd love to test this but I updated my Controller this morning and got r2269. How can I install r2281?
r2287 finally showed up and everything seems to be working fine (after struggling for 4 hours with the controller not being able to update).
(In reply to comment #16) > r2287 finally showed up and everything seems to be working fine (after > struggling for 4 hours with the controller not being able to update). > Marking bug as Closed.
*** Bug 8160 has been marked as a duplicate of this bug. ***