Skip to main content

​
Turn the right Windows Client into a jump server, without standing up a separate jump-server product

The jump-server pattern is universal in privileged-access architecture: administrators connect to a controlled, monitored intermediary box, then from there connect to production systems - with the production credentials never touching their workstation. Syteca’s PAM Connection Manager turns an existing Windows Client into a jump server - by selecting one checkbox in the Client configuration. Same agent already monitoring user activity is now also brokering credential-less remote-account access using account secrets from Syteca’s PAM module. One product, same license, no second deployment to maintain.
Use the Syteca PAM Connection Manager when you need to:
  • Provide credential-less access to production systems - admins use the jump server, secrets stay in Syteca.
  • Avoid a separate jump-server product like Delinea Connection Manager.
  • Apply unified monitoring to admin access - the same Syteca Client recording activity is also brokering the connection.
Pair it with PAM secrets for the credential vault that feeds this Connection Manager.
Applies to Windows and Linux Clients only. macOS Clients can’t be used as Syteca PAM Connection Manager hosts.

​
Where to find it

The Enable the Syteca PAM Connection Manager checkbox lives on the Editing Client / Editing Client Group page, on the Properties tab, in the Client Mode section.

​
What enabling it does

When the checkbox is selected, the Windows Client computer becomes a PAM Connection Manager host - usable as a jump server for remote access using account secrets. Users connect to the Windows Client, then from there can launch sessions to remote machines using credentials stored in Syteca without those credentials being exposed in their own RDP client or session. For the full configuration of the jump-server side - what kinds of secrets it can broker, which users can use it, how the session-launch UI works - see Jump server configuration. That desktop experience is Windows-only; on a Linux Client, this same checkbox instead enables the PAM Connection Manager for Linux - a command-line (pacm) equivalent for SSH and terminal sessions.

​
Choosing the right host

For multi-user PAM Connection Manager deployments, use a Windows Server operating system as the host. Windows Server supports multiple concurrent sessions, which is required if two or more users will use the Syteca Desktop Connection Manager simultaneously on the same Client computer.Workstation Windows editions (Windows 11, 10) limit concurrent sessions and are suitable only for single-user PAM Connection Manager hosts.

PAM secrets

The credential vault feeding the PAM Connection Manager.

Jump server configuration

Configuring the jump-server side of the integration (Windows).

PAM Connection Manager for Linux

The command-line equivalent for Linux SSH and terminal sessions.

Windows Clients

Full Windows Client documentation.

ACB

Programmatic access to PAM secrets - complementary to the Connection Manager UI flow.