xlo9c (xlo9c) asked a question.
Tunneling VNC through Advanced Server Access SSH
I know ASA only supports SSH and RDP. However, I have linux users in my environment and they need to use VNC in order to access the GUI. This was working great for a day. However, we noticed that after we finished the log in process, the logged-in user listed was 'sft-managed' and not the username of the person who just logged in. Then the following morning, the screen was locked and we were asked to log back in but we don't have an sft-managed user on the linux system. We can't input a password even if we try (keeps getting erased). What's worse, rebooting the system or restarting the VNC service doesn't resolve the issue so we are stuck at the log in screen.
Image is not available
Has anyone else experienced this?
Hello @xlo9c (xlo9c) Thank you for reacting out to our Community!
It seems that you have opened a case with Support and working with them to resolve this matter.
Community members help others by clicking Like or Select as Best on responses. Try it today.
How is this even possible to use VNC sessions via the ASA Client?... VNC is not a listed supported application and even if you attempt a RDP session against a Linux ASA server agent the session is denied because ASA client only establishes SSH connections to Linux OS's...
We have been using SSH and tunneling our VNC sessions through the SSH connection. This is a good security practice, but without ASA you have the added benefit of being logged in as your own user. The way we ended up resolving this issue (with ASA) is to disable screen lock. However, ASA is not the right solution for us in this case. We use Okta Verify to authenticate our VPN sessions which also provides encrypted connections. We can then VNC into the private servers without SSH. This requires a slightly more manual approach to server authentication, but the productivity of our engineers is greatly improved without involving ASA.