We have a requirement to use a PAM solution for connecting into specific devices however we'd like to continue using ASG Remote Desktop which is more user friendly than the PAM web based user interface.
Our PAM solution supports proxying native RDP and SSH client connections so no issues there, the only thing which is a problem is the credentials.
To proxy native protocols our PAM solution requires users to include their username and the unique device ID of what they want to connect to as part of their username, like this: username#device_id
What we want is users to be able to create a private credential for themselves in ASG with the username and password they use for PAM and then we want to create public connection objects which include their unique ID in PAM. I think it would have to be something like an extra field in the ASG connections which when populated automatically append that value to the username provided by the user
The only alternative we have is for every user to create a new credential for every single connection in ASG which is just isn't practical
Thanks
Our PAM solution supports proxying native RDP and SSH client connections so no issues there, the only thing which is a problem is the credentials.
To proxy native protocols our PAM solution requires users to include their username and the unique device ID of what they want to connect to as part of their username, like this: username#device_id
What we want is users to be able to create a private credential for themselves in ASG with the username and password they use for PAM and then we want to create public connection objects which include their unique ID in PAM. I think it would have to be something like an extra field in the ASG connections which when populated automatically append that value to the username provided by the user
The only alternative we have is for every user to create a new credential for every single connection in ASG which is just isn't practical
Thanks