1.1.0

Release Notes of RPort Server 1.1.0, RPort Client 1.1.0 and RPort Front End/Web UI - 1.1.0-5

Release date: August 2024

RPort Server and RPort Client

Three new APIs have been introduced to support the new Job Status feature area. These are /jobs, /jobs/{job-id} and /jobs/{job-id}/latest. For more information, see the api-docs.
Clients have been updated to support live job output buffer results when using the /jobs/{job-id}/latest API.

Clients no longer report a potential incompatible server warning message on connection disconnect

Much improved handling of clients re-connecting when already connected (due to SSH connection issues)
Tunnels are now properly terminated by the server on client connection disconnect
Clients no longer report connected tunnels when only loading client-side tunnel configuration
OSVersion and OSFullName searches and filters now correctly handled
Existing user sessions deleted when deleting a user
Large job result buffers no longer cause SSH client server connection disconnects

The client send_back_limit is currently ignored for job output buffers. The maximum size of job results is 256000 bytes, which is the maximum size of a golang SSH global request message.
The server is currently rporting an incorrect error message (Invalid Token: too many requests) when the user no longer has a valid session

Added a new Job Status area at the top level. This makes it much easier to view the results of jobs (aka commands and scripts). If clients are also updated to 1.1.0 then it will be possible to see 'live' job output from the running job when viewing the job details via the Job Status area. Users will only be able to see the status and output of jobs that they have started, unless the server configuration (via show_all_jobs_for_permitted_clients) has been updated to allow visibility of all jobs for the clients that the user is permitted to manage.

When running commands/scripts, the job status/progress information has been improved
Improved display of permission values

Clients with no IPv4 addresses could cause the client navigation / selection panel to get stuck on the spinner
Session handling has been improved and a number of bugs fixed (although see Known Limitiations)
Various package updates for security fixes
When selecting clients for multi-job execution, empty brackets no longer shown if no group description
Drag and drop in the Library is working again

Removed sessions (either via expiry or admin revocation) show an incorrect message of Invalid Token: too many requests and the user is not explicitly logged out. However, the user will not be able to interact with the server API any longer. Refresh the browser to be redirected to the login page.

Last updated 3 months ago