Plugin: Jetty Web Server 2.0

[wayner]

Not requiring a password is probably not a good idea if you make your Sage web UI accessible from the internet, and I don't know why you wouldn't want to do this as it is HUGELY useful to be able to set up recordings, etc when away from home. Although I guess another option is to use a VPN on remote devices.

[Fuzzy]

Originally Posted by wayner

Not requiring a password is probably not a good idea if you make your Sage web UI accessible from the internet, and I don't know why you wouldn't want to do this as it is HUGELY useful to be able to set up recordings, etc when away from home. Although I guess another option is to use a VPN on remote devices.

I find placeshifter/miniclient is MUCH more intuitive for remote management.

[wayner]

Originally Posted by Fuzzy

I find placeshifter/miniclient is MUCH more intuitive for remote management.

Perhaps but that doesn't work so well from a corporate computer (where you can't install non-business software or where ports are blocked) or from an iPhone/iPad.

[tmiranda]

Originally Posted by wayner

Not requiring a password is probably not a good idea if you make your Sage web UI accessible from the internet, and I don't know why you wouldn't want to do this as it is HUGELY useful to be able to set up recordings, etc when away from home. Although I guess another option is to use a VPN on remote devices.

I'm writing something that programatically access my Sage server via sagex, and it's not possible to have a user manually enter a password. I wanted to disable the password checking for testing purposes since I can't get the userassword to be accepted in the URL.

From the various responses I am gathering I can't get it to recognize the userassword in the URL but I may be able to disable password checking by editing one of the Jetty xml files.

[EnterNoEscape]

Are you doing this in Java? Have you tried encoding the username and password in base64 in the request header. This code is adapted to your need, but it's based on code that works for communication with the HDMI network encoders which use basic authentication.

String username = "username";
String password = "password";
URL address = new URL("http://server:8080/sagex/api");

URLConnection connection = address.openConnection();
String encodedBytes = DatatypeConverter.printBase64Binary((username + ":" + password).getBytes(StandardCharsets.UTF_8));
connection.setRequestProperty("Authorization", "Basic " + encodedBytes);

Java 8 has a Base64 class for this, but since most users are running Java 7, I would probably not raise the bar. Also I think you can set a username and password for HTTP communication in Java, but it will apply to all communications which is not what I normally want.

[tmiranda]

Originally Posted by EnterNoEscape

Are you doing this in Java? Have you tried encoding the username and password in base64 in the request header. This code is adapted to your need, but it's based on code that works for communication with the HDMI network encoders which use basic authentication.

String username = "username";
String password = "password";
URL address = new URL("http://server:8080/sagex/api");

URLConnection connection = address.openConnection();
String encodedBytes = DatatypeConverter.printBase64Binary((username + ":" + password).getBytes(StandardCharsets.UTF_8));
connection.setRequestProperty("Authorization", "Basic " + encodedBytes);

Java 8 has a Base64 class for this, but since most users are running Java 7, I would probably not raise the bar. Also I think you can set a username and password for HTTP communication in Java, but it will apply to all communications which is not what I normally want.

I'll give that a try over the weekend. http communication is not my strong point!

[EnterNoEscape]

Originally Posted by tmiranda

I'll give that a try over the weekend. http communication is not my strong point!

After working with microcontrollers for so long, I am used to doing things the hard way.

[tmiranda]

Originally Posted by EnterNoEscape

Are you doing this in Java? Have you tried encoding the username and password in base64 in the request header. This code is adapted to your need, but it's based on code that works for communication with the HDMI network encoders which use basic authentication.

String username = "username";
String password = "password";
URL address = new URL("http://server:8080/sagex/api");

URLConnection connection = address.openConnection();
String encodedBytes = DatatypeConverter.printBase64Binary((username + ":" + password).getBytes(StandardCharsets.UTF_8));
connection.setRequestProperty("Authorization", "Basic " + encodedBytes);

Java 8 has a Base64 class for this, but since most users are running Java 7, I would probably not raise the bar. Also I think you can set a username and password for HTTP communication in Java, but it will apply to all communications which is not what I normally want.

This worked! Thank you.

[EnterNoEscape]

Originally Posted by tmiranda

This worked! Thank you.

Glad I could help!

[Fuzzy]

Originally Posted by wayner

Perhaps but that doesn't work so well from a corporate computer (where you can't install non-business software or where ports are blocked) or from an iPhone/iPad.

Perhaps, but placeshifter doesn't need to be 'installed'- you can just copy the folder onto a thumbdrive and run it from there - and i have it set to i believe port 21, so the work firewall lets it through thinking it's an FTP site.

I wouldn't burden myself with an iPhone - so that solves that problem.. :-)

[NetworkGuy]

Originally Posted by Fuzzy

Perhaps, but placeshifter doesn't need to be 'installed'- you can just copy the folder onto a thumbdrive and run it from there

I did not know that. That is really useful.

[Fuzzy]

Originally Posted by NetworkGuy

I did not know that. That is really useful.

Yeah, I think most the computers I use at work have a copy of placeshifter sitting in C:\Temp somewhere.

[waynedunham]

Originally Posted by Fuzzy

Yeah, I think most the computers I use at work have a copy of placeshifter sitting in C:\Temp somewhere.

You're lucky. I'm retired 3 years now, but at my work they had so much trouble with people infecting the network with virus/spyware infected USB drives they disabled the USB ports on our computers. Just an FYI here, the IT department (a Municipality network) was so bass-ackwards this was their ham handed (gee, I don't know how things work) way of "fixing" the problem.

We had to get them to unlock our USB ports because we had a USB device we had to have access to. I was a FireFighter and our AED (Automatic External Defibrillator) devices used a USB connection to download the data after every use so we could send that information in with our reports on the incident.
Of course that was before just about everything used the USB ports. Our monochrome laser printers still used a printer port (how quaint!) and all our keyboards and mice plugged into their respective PS2 ports (also quite quaint)

[wayner]

Even if you do have access to USB ports you may find that the IP ports are blocked at work so you may not be able to use placeshifter unless you route it through port 80 or something similar, assuming that you could even do that.

[Fuzzy]

Originally Posted by wayner

Even if you do have access to USB ports you may find that the IP ports are blocked at work so you may not be able to use placeshifter unless you route it through port 80 or something similar, assuming that you could even do that.

Yeah, like I said, i host placeshifter as port 21. Works great. That, combined with RDP as port 80, and I've got essentially full access to my home from just about any internet connected device.

[Taddeusz]

Originally Posted by Fuzzy

Yeah, like I said, i host placeshifter as port 21. Works great. That, combined with RDP as port 80, and I've got essentially full access to my home from just about any internet connected device.

I found this neat web based remote gateway called Guacamole, now Apache Guacamole (incubating), that is wonderful for getting around port restrictions and being secure via TLS. Doesn't work as well as a native RDP client but works well enough for most tasks from any browser.

[tmiranda]

Originally Posted by Fuzzy

Yeah, like I said, i host placeshifter as port 21. Works great. That, combined with RDP as port 80, and I've got essentially full access to my home from just about any internet connected device.

Just be careful. I know for a fact that where I work you risk getting fired for running unauthorized software.

[hb4]

Having trouble logging into the Jetty Web Server.

Installed Jetty Web Server Plugin and am able to access from the Sage Server PC using (server LAN IP):8080/apps/ using the Plugin user and password, and can access the Web User Interface.

Logging in from the WAN using (Wan IP):8080/sage/ I get the login screen, to which I post the same user and password and I get:

HTTP ERROR 401

Problem accessing /sage/. Reason:

UNAUTHORIZED

Powered by Jetty://

So, I know I've made it through Port Forwarding and the Windows Firewall; any reason why the login fails?

[tvmaster2]

Originally Posted by hb4

Having trouble logging into the Jetty Web Server.

Installed Jetty Web Server Plugin and am able to access from the Sage Server PC using (server LAN IP):8080/apps/ using the Plugin user and password, and can access the Web User Interface.

Logging in from the WAN using (Wan IP):8080/sage/ I get the login screen, to which I post the same user and password and I get:

HTTP ERROR 401

Problem accessing /sage/. Reason:

UNAUTHORIZED

Powered by Jetty://

So, I know I've made it through Port Forwarding and the Windows Firewall; any reason why the login fails?

same problem here, started a few weeks ago - can't isolate why, but it's likely got something to do with partially rebuilding my SageTV Properties and my wiz.bin files. Is it possible a JAVA update broke it?

[hb4]

I don't understand 90% of what's in the forum, but here's a post that might shed some light. Unfortunately, the file structure mentioned in the thread does not match what I have. Probably a V7 vs V9 kinda thing.