Plugin: Mobile Web Interface 1.2

[jreichen]

Originally Posted by SageGk

It works from Firefox, logs right in.
From my phone it just keeps prompting me for username and p/w.

It would be nice if I could get to the bottom of this... What kind of phone do you have? Can you post the most recent file in the jetty/logs folder?

[SageGk]

Originally Posted by jreichen

It would be nice if I could get to the bottom of this... What kind of phone do you have? Can you post the most recent file in the jetty/logs folder?

I have a Palm Pre. The last log has this entry:
173.XXX.XXX.XXX - - [17/Sep/2009:22:05:41 +0000] "GET /sagem/m/menu.jsp HTTP/1.1" 401 1387 "-" "Mozilla/5.0 (webOS/1.1; U; en-US) AppleWebKit/525.27.1 (KHTML, like Gecko) Version/1.0 Safari/525.27.1 Pre/1.0"

[alfi33]

I got it working great on both my PC and my trusty ol' BB 8700. No problems with multiple password prompts here....just had to enter in the username/password correctly...doh!

Very handy tool....thanks for your work on this.

[stuckless]

Originally Posted by razrsharpe

in BMT's context.xml file there is no line about authentication = true. I've never been prompted for a password with bmt... one could argue that this not correct and is a bug.

Since I wrote I wrote it... I'll argue that it's by design I don't run security on my web server (but I also don't expose my web server to the world). I think that personal security of the app probably should be handled by the end user, by modifying the context.xml, if they need/want to user/pass security.

[razrsharpe]

Originally Posted by stuckless

Since I wrote I wrote it... I'll argue that it's by design I don't run security on my web server (but I also don't expose my web server to the world). I think that personal security of the app probably should be handled by the end user, by modifying the context.xml, if they need/want to user/pass security.

I figured it was a conscience decision, and also figured the reason for no security was that you were only accessing the webserver locally. I only came across this when i installed the mobile web and sage alert and those apps started asking me for a password... i was like what pw.. where do i set that up... So i went looking and noticed that the bmt context xml was missing the authenticate = true line...

Anyway... I agree security should ultimately be handled by the end user... To make it easier on the xml challenged, maybe add the authenticate = true line and comment it out in the xml file so if people wanted to enable security it would be relatively straight forward to do? the syntax would be correct and people would just need to remove an !.

[stuckless]

Originally Posted by razrsharpe

I figured it was a conscience decision, and also figured the reason for no security was that you were only accessing the webserver locally. I only came across this when i installed the mobile web and sage alert and those apps started asking me for a password... i was like what pw.. where do i set that up... So i went looking and noticed that the bmt context xml was missing the authenticate = true line...

Anyway... I agree security should ultimately be handled by the end user... To make it easier on the xml challenged, maybe add the authenticate = true line and comment it out in the xml file so if people wanted to enable security it would be relatively straight forward to do? the syntax would be correct and people would just need to remove an !.

I'll add an issue for this... I may handle this by adding a panel to the bmt configuration, and allowing the user to enable security from there. (I'll update the xml from the web ui).

[Jason]

Originally Posted by jreichen

Is anybody still having trouble with multiple password prompts? If you are, have you tried the things I suggested?

Duh... it might help if I set the user: pwd correctly...

In any case, would it be possible to add the 'Stream with Orb' to the next release into the options body portion of the Mobile Webserver?

Example: http://mycast.orb.com/orb/data/strea...e-3332331-0%22

-Jason

[jreichen]

Originally Posted by razrsharpe

I figured it was a conscience decision, and also figured the reason for no security was that you were only accessing the webserver locally.

It would be nice to have the option of not requiring login on the local network. I'm not sure if this is a simple configuration option that Jetty already supports or if I would need to code something up.

Originally Posted by razrsharpe

I only came across this when i installed the mobile web and sage alert and those apps started asking me for a password... i was like what pw.. where do i set that up... So i went looking and noticed that the bmt context xml was missing the authenticate = true line...

I didn't even notice. I probably access the web interface or SRE first before going to BMT so I always assumed I didn't get a prompt because I had already logged into another app.

Originally Posted by razrsharpe

Anyway... I agree security should ultimately be handled by the end user...

I agree the user should be able to change it. However, IMHO it should be "secure by default". I had no idea my server was running an app that did not require authentication.

[SageGk]

Originally Posted by SageGk

I have a Palm Pre. The last log has this entry:
173.XXX.XXX.XXX - - [17/Sep/2009:22:05:41 +0000] "GET /sagem/m/menu.jsp HTTP/1.1" 401 1387 "-" "Mozilla/5.0 (webOS/1.1; U; en-US) AppleWebKit/525.27.1 (KHTML, like Gecko) Version/1.0 Safari/525.27.1 Pre/1.0"

jreichen. does this log entry tell us anything? I have been playing with my router settings, but still cant get passed the login prompt from my cell phone.

[jreichen]

It doesn't tell me a lot. It has a 401 HTTP error code which means Jetty is responding to the browser and telling it that it needs to prompt the user for a login or that the last login was incorrect. Are you using 'sage' for the user and 'frey' for the password? Is there anything else in the log directory besides that message?

What would be helpful is a log of the conversation taking place between the client and server, which is why I was hoping you could do it with Live HTTP Headers. I might need to add more logging to the server side to help with troubleshooting. Or, perhaps enabling the DEBUG line in JettyStarter.properties and restarting Sage would print more to SageTV's log.

I think you might be the first user trying a Palm Pre so I don't know if that has anything to do with it. It looks like the browser is similar to the iPhone's (AppleWebKit). I've seen the problem a couple of times on my iPhone but it's never lasted long enough for me to look into it.

[doncote0]

Thank you for this!

Excellent. Got it working with my router, iPhone and dyndns.org

Wish I knew how to timeshift properly with Orb...

Anyone have any ideas?

[doncote0]

Set it to 3 minutes and that might have fixed the problem. I'll play with it some more.

[jreichen]

SageGK,

Can you verify that you are using sage/frey for your user/pwd, and entering it in all lowercase? Sometimes the UI on mobile devices automatically capitalizes the first letter.

[SageGk]

Originally Posted by jreichen

SageGK,

Can you verify that you are using sage/frey for your user/pwd, and entering it in all lowercase? Sometimes the UI on mobile devices automatically capitalizes the first letter.

yes, im positive that im entering it correctly. Username: sage p/w:frey I can't understand why it isn't working. I'll try to get the whole log to you, gonna take me a while to edit my IP out of it though.

Edit:I PM'd todays log to you.

[voorhees]

I upgraded the web interface to the Jetty version 2.25 this last weekend. I have now noticed that when using the Mobile Web Interface, when I select "Home" on the main "Menu" page under the "Media Center" options I get the message:

Message: java.lang.NoClassDefFoundError: net/sf/sageplugins/webserver/UIContextTranslator

Every other page so far works fine except for this one. Actually that is the page I use the most. Any ideas?

Thanks.

[jreichen]

Are you using the latest version of the mobile web interface? Try upgrading it. I think that will fix your problem.

[voorhees]

Originally Posted by jreichen

Are you using the latest version of the mobile web interface? Try upgrading it. I think that will fix your problem.

jreichen,

Thanks for the reply. I am using v1.2 (see attached image).

I did some playing around and noticed that I get the error message if something is recording, and it functions correctly if nothing is recording. It did not do this prior to upgrading the web interface to v2.25.

[jreichen]

It's something with the classpath. I removed the reference to that class from version 1.2. The class is in nielm_sagewebserver.jar, which is no longer available if you're running nielm's web interface in Jetty.

Try this:

1. Shut down SageTV
2. Delete the jetty/webapps/SageWebApp folder
3. Start SageTV

[voorhees]

I also get the error if the SageTV is playing something (TV, music, etc.). So, both while recording and playing. But if SageTV is is not doing anything I do not get the error.

Thanks.

[voorhees]

Originally Posted by jreichen

It's something with the classpath. I removed the reference to that class from version 1.2. The class is in nielm_sagewebserver.jar, which is no longer available if you're running nielm's web interface in Jetty.

Try this:

1. Shut down SageTV
2. Delete the jetty/webapps/SageWebApp folder
3. Start SageTV

Looks like we posted at the same time.

Gave that a try, and that fixed it. Everything works great again. Thanks so much for your help and for the hard work on the great app.