Bugzilla – Bug 2892
Can't login via CLI
Last modified: 2006-01-30 12:42:21 UTC
I'm unable to login successfully via the CLI when SlimServer has Password Protection enabled. I'm using the command: login malgre test i.e. username = malgre and password = test. This login works OK via the web interface. The server responds with: login malgre ****** but then immediately drops the connection. I've enabled d_cli and this produces the output below. 2006-01-27 10:55:08.0256 CLI: Accepted connection from 192.168.0.50:3698 (1 active connections) 2006-01-27 10:55:09.8880 CLI: Parsing command: Found command, value [login] 2006-01-27 10:55:09.8881 CLI: Parsing command: Found param [1], value [malgre] 2006-01-27 10:55:09.8881 CLI: Parsing command: Found param [2], value [System.Byte[]] 2006-01-27 10:55:09.8881 CLI: Processing command [login] 2006-01-27 10:55:09.8883 CLI: Response: login malgre ****** 2006-01-27 10:55:09.8884 CLI: Sending response... 2006-01-27 10:55:09.8885 CLI: No more messages to send to 192.168.0.50:3698 2006-01-27 10:55:09.8887 CLI: Closed connection with 192.168.0.50:3698 (0 active connections) Tested with 6.2.2, v2006-01-27
fred, is this supported? should I stop bouncing to you because you already read this stuff? :)
Well this should work and is supported and works here. The log gives a hint as to what may be going wrong: "CLI: Parsing command: Found command, value [login] CLI: Parsing command: Found param [1], value [malgre] CLI: Parsing command: Found param [2], value [System.Byte[]]" So the CLI gets the login and malgre parts but received "System.Byte[]" for password, which does not match, and you're logged out [What is missing is a message that states the login is wrong, I'll add that]. "System.Byte[]" does not sound like a Perl construct but googling it reveals it seems to be a Virtual Basic construct... Could there be a little problem on the sender side? Please try it using a telnet connection and let us know if it still fails when you type "test" as password. HTH
My apologies, I was confused by the fact that the debug output didn't log any error. I've found the cause of the problem - closing the bug as invalid. Malcolm