3.1. Secure Web Terminal Proxy FAQ#

3.1.1. Frequently Asked Questions#

  • Here is a list of common questions about the tool

3.1.1.1. How To Run#

Note

You can execute ….

docker pull swtp/secure-web-terminal:1.0.2

docker run with appropriate arguments

See section on deployment for more details config

3.1.1.2. How many concurrent users can be supported by the system#

Note

This is dependent on the terms of the license and the machine resources that the tools was deployed to.

In general a generic deployment on base hardware can support hundreds of users.

The better the machines resources the more consurrent users the system can support.

3.1.1.3. What Is the limitations on CLI’s that can be used#

Note

In general as long as the CLI is well behaved and dose not require access to certain key mappings that are inherent to a

web browser then there is really no limitation to what kind of CLI can be offered as a service to remote web connect into.

The connection to the host CLI is accessed via a SSH session, so we require that SSH is running on the target host where the cli is located.

3.1.1.4. How Long Do Sessions Last#

Note

The session will last for as long as the user is logged into the system. There is no predefined service timeout.

3.1.1.5. Firewall Ports Access#

Warning

The port that the service listens on in configured in the sshwebproxy.config it currently defaults to 8443

However you can change this to 443 and adjust your firewall rules accordingly

3.1.1.6. Is there a default User for the SSH sessions#

Note

You can confiugre a default user that all users after opening a terminal will log into.

Warning

However we do not recommend using this feature for non-repudiation purposes.

3.1.1.7. How To Block All Serivces#

Note

Login as an admin to the system and got the the “Session Actions” Section and select “Block All”.

This will block all incoming requests for terminal access

Warning

Blocking all will deny any new connections but active connections will still continue to work.

3.1.1.8. How To Block Services#

Note

Login as an admin to the system and got the the “Session Actions” Section and select from the “Deny New Sessions” section to select the service to block access to

3.1.1.9. How To Clear Blocked Services#

Note

Login as an admin to the system and got the the “Session Actions” Section and select from the “Clear Deny Of Services” section to select the service to unblock.

3.1.1.10. How To Close Session By User#

Note

Login as an admin to the system and got the the “Session Actions” Section and input a userid into the “Close By User Id” section to close all session that were opened by a particular user id.

3.1.1.11. What Software Is used For the Terminal Representation#

Note

The terminal that the users log into is a version of xterm.js

3.1.1.12. Limitations on Publickey Use#

Note

Currently the tool only supports the use of public keys without a password.

So in the instance where a password is required for public key, the system wont log users in

It is required that all files have the proper permissions.

All pubkeys should have only user rw for the proxyweb user [sshproxyweb|4609]