When I attempt to leave the Username field blank (WITHOUT automatic login checked) for the SSH connection type for the Clientless SSL VPN, I am prompted with the following error message:
The clientless VPN connection object may not have an empty login username attribute
However, this is not required for Remote Desktop. I feel that requiring an SSH login username will require me to create separate Clientless SSL VPN connections for each user that I want to allow access to a resource instead of one generic one for a group of users and then have a username prompt like RDP login screen.
Suggestion: Maybe even allow a variable for the username, to fill in the logged in Username in the Portal?
The clientless VPN connection object may not have an empty login username attribute
However, this is not required for Remote Desktop. I feel that requiring an SSH login username will require me to create separate Clientless SSL VPN connections for each user that I want to allow access to a resource instead of one generic one for a group of users and then have a username prompt like RDP login screen.
Suggestion: Maybe even allow a variable for the username, to fill in the logged in Username in the Portal?