A regular SSH connection is done over TCP port 22. However in most corporate environments, only ports 80 and 443 are open to the internet (for HTTP and HTTPS respectively). This means that is it not possible to use a tool like putty to open an SSH session to a server on the internet when inside a corporate environment. In this case, port 80 or 443 could be repurposed for SSH assuming the corporate firewall allows this.
However, if this server is also hosting JEE webapps, then it is very difficult (and could be impossible) to get an interactive SSH session to such a server from a corporate environment. This is where SSHW steps in. It is designed to offer interactive SSH sessions from a JEE container alongside any other webapps that may be deployed on the server.
The alternative is to use a web SSH client, but do you trust them with your root passwords?
Simply take the latest WAR file from the releases page and deploy it to your Tomcat instance on your server. It may also work with other JEE containers, however I have only performed testing with Tomcat v7 and v8.
It will install itself as the root context sshw. So if your tomcat instance is on your local machine and running on the default port 8080, the URL will be http://localhost:8080/sshw.
I make no guarantees about the security of this app. Use at your own risk. I am still evaluating the security of it. It does use Spring Security for A&A, so the password transfer mechanism should be secure. Also, it should use secure websockets via WSS if on a HTTPS link. I have not tested this yet. I recommend you setup your JEE container to use HTTPS and access it through the resulting HTTPS link.
Not really! It works as intended, but there is a fair bit of tidying up and testing to do.