6ddcf (6ddcf) asked a question.
I am trying out an ASA gateway and have run into a problem with it.
When I disable the forwarding feature, SFT works fine. I can simply use the command line to access the server using "sft ssh <server>".
But when I enable forwarding, the "sft ssh <server>" command stops working, and I get an HTTP response code of 403.
I thought it might be an issue with me not being able to connect to the ASA gateway.
But when I use the "connect" button on the ScaleFT web console, I can SFT to the same server without any trouble. I can see the recording of my SSH session in the logs, which shows that my connection to the server is indeed going through the gateway. So, there's no issue with the network connection.
I'm not sure what the issue is. I have been trying to figure this out for two whole days.
Meanwhile, my colleague is able to use both the command line and the web console "connect" button to initiate SFT sessions through the gateway to the same server without any problems.
Hi @6ddcf (6ddcf) , Thank you for reaching out to the Okta Community!
I haven’t been able to locate any similar reports so I ran this by my ASA colleagues and they mentioned that something might be wrong with the client machine and they’ll need the debug logs to investigate.
Please open a case with the Support Team. If you don’t have access to create cases, please reach out to one of your Okta Super Admins to open one for you.
If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you.
Hope my answer helps!
--------------------------------
Ask the experts about Okta Privileged Access