Issues with ssh connections made with a service launching SecureCRT becoming disconnected.

Products

• CA Privileged Access Manager - Cloakware Password Authority (PA)
• CA Privileged Access Manager (PAM)
• CA Privileged Access Manager - Server Control (PAMSC)

Issue/Introduction

SecureCRT is used because multiple connections may be made, with each on on a separate tab in SecureCRT.  It was observed that doing a Filter on the Access page, to find another system to be used, all the existing connections were disconnected.

Environment

Release : 4.0.X / 4.1.X

Component : PRIVILEGED ACCESS MANAGEMENT

SecureCRT 

Cause

The problem is related to an issue with dynamic ports specified in the Ports field of the Service.  In this case the field contained 22:*, with the * specifying dynamic ports.  When using a Service configured like this any refresh of the Access page will break the connections, i.e. Filter or clicking the Reset button.

Resolution

The problem was resolved by changing the Ports field to specify 22:22233 instead of 22:*.  Any upper range port can be used, but this one definitely worked in the test environment.  No problems were observed with multiple SecureCRT sessions with the Service configured in this way, but you should test in your own environment to be sure.