Symantec Privileged Access Management

Expand all | Collapse all

SSH access via CAPAM_2.8.3.02

Jump to Best Answer
  • 1.  SSH access via CAPAM_2.8.3.02

    Posted 10-04-2017 09:15 AM

    Hi there!


    I'm facing a similar issue to the one posted in:

    Tech Tip - CA Privileged Access Manager: Issue with SSH access to Solaris via CA PAM 2.8.2  


    Not against a Solaris box but a Ubuntu Linux one, although Resolution says it was going to be fixed in 2.8.3 release, I'm running CAPAM_2.8.3.02 but the issue persist.



      SSH applet opens and shows ""Connected to server running SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.8".

      But then no login prompt is ever displayed, turning into timeout.


      CAPAM_2.8.3.02 (Web and Java client)


      Ubuntu 14.04 x86_64 devices with SSH applet enabled.

      SSH-2.0 OpenSSH_6.6.1p1




    - For both Web (browser) and Java client, cache has been cleared

    - Successful SSH access from other Linux boxes has been tested. From:

       Ubuntu 14.04.5 3.13.0-129-generic x86_64
       SSH-2.0 OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.8, OpenSSL 1.0.1f

    - ~/CAPAMClient/logs.log output:
    SSHInteractiveClient.fatalDisconnect() : 'Disconnected, reason: Exception caught when processing RX pkt'     syserr [Switchboard]
    SSH2Transport.disconnectInternal() : 'disconnect: Exception caught when processing RX pkt'     syserr [Switchboard]



    Any suggestion(s) would be much appreciated.

  • 2.  Re: SSH access via CAPAM_2.8.3.02

    Posted 10-04-2017 09:34 AM



    Is this an attempt to use password management to SSH to server automatically?


    Mike P

  • 3.  Re: SSH access via CAPAM_2.8.3.02

    Posted 10-04-2017 09:51 AM

    Hi Michael, thanks for replying.

    No, it is a simple SSH from the SSH CA PAM applet expecting the login prompt from the target in order to provide credentials.



  • 4.  Re: SSH access via CAPAM_2.8.3.02
    Best Answer

    Posted 10-04-2017 10:47 AM

    Hello, If you are indeed at, please got to and download and then apply patch This appears to be closer to your problem than the old Solaris connect issue. If the problem persists with, please open a support case and if possible attach the client log after going to the Config > Diagnostic section, scroll down to the "Applet Log Level” section, set the log level to Debug and hit the Submit button. Reproduce the problem and then set the log level back to Error.