We intend to use a single RemoteApp (PuTTY) to connect to multiple target devices, depending on the device selected by the user at runtime.
Environment overview
Segura PAM: On-prem
PuTTY is published as a RemoteApp on a Windows RDS Server
Credential scenario:
We use Domain credentials, In the Information tab of the credential:
Device: Active Directory server (for successful password rotation)
Password type: Domain user
Password rotation works correctly using LDAP templates
Session / RemoteApp configuration
PuTTY is published in the RDS Server
In the credential:
Session settings → added the PuTTY RemoteApp
Authentication credential → credential used to log in to the RDS server
Authentication device → RDS server where PuTTY RemoteApp is published
RemoteApp configuration in Segura
Name: PuTTY
Application path: PuTTY executable path on the RDS server
(e.g. C:\Program Files\PuTTY\putty.exe)
Parameters tested (examples):
-ssh [username]@[hostname] -pw [password]
-ssh [USERNAME]@[DEVICE_HOST]
-ssh [USERNAME]@[device_ip]
-ssh [USERNAME]@[host_ip]
None of the above parameters work
Runtime / login flow
User logs in to Segura PAM
User selects their credential
User searches and selects a device
User clicks Start Session
Under RDP, user selects PuTTY RemoteApp
Session launches, but PuTTY shows an error such as:
Unable to open connection to <device_host / device_ip>
Host does not exist
It appears that the target device context (host/IP) is not being resolved or passed to the PuTTY RemoteApp at runtime.
Questions
Is it supported to use one PuTTY RemoteApp to connect to multiple devices, based on the device selected in PAM?
What is the correct way to pass the selected device’s IP/hostname to PuTTY when launched as a RemoteApp?
Are there specific macros, parameters, or RemoteApp limitations we should be aware of in this scenario?
Is an additional configuration required (e.g. segregated parameters, session type, or device binding)?
Any guidance or official documentation references would be highly appreciated.