
lsr4m (lsr4m) asked a question.
Hi,
I'm trying to create a SFTP connection within okta workflow module and getting "detected connection failure" error. I've checked that the Okta URL is in the whitelist to connect to the SFTP server but unable to find out the issue (no logs on okta and server side). Does anyone know what could be the problem here ?

You have probably already done this but double check your settings using the following Authorization guide. If you are using a domain address try the IP of the SFTP server instead.
https://help.okta.com/wf/en-us/content/topics/workflows/connector-reference/sftp/overview/authorization.htm
More SFTP connector documentation can be found here: https://help.okta.com/wf/en-us/content/topics/workflows/connector-reference/sftp/sftp.htm
Yep, i've tried with the IP as well but no luck. I wonder how can i troubleshoot this since the error message is not very user friendly and the SFTP server logs shows no incoming request from Okta instance IP (Okta URL translates into 2 Ips interchangeably).
Additionally, i land into the same error when i try with invalid credentials so i'm guessing okta is unable to identify the host or some other issue i'm not aware of.
The (500) makes me think this is server related so if you don't see anything in the logs on the server perhaps this is a proxy or firewall causing the error.
If leveraging the IP address provides the same responses it is not going to be DNS (Problem with Okta identifying the host). Is this an on-prem solution you are trying to reach? If so, the proxy/firewall mention is likely the cause. If it isn't getting through the border to the desired destination you wouldn't see logs at the destination. Note: on-prem connectivity is considered unsupported.
Hi Tim - yes, it's an on-premise solution. If i understand you correctly, okta can't connect to on-premise SFTP server ? Is there any other solution to this problem ?
@lsr4m (lsr4m) -- It's not that we cannot technically connect to an on-prem it is just going to be residing behind layers of security at your company borders. Anything from a firewall, proxy, load balancer, or other "traffic analyzer" solutions could potentially cause failure points and Okta Support isn't equipped to troubleshoot these on-prem based problems that are not really "Workflows" issues.
We are also not going to recommend an on-prem device be publicly exposed because most of them are not really designed to be (which increases security risk if they are).
With the cloud-based services their API's are already publicly facing and they have already implemented (and are responsible for) their own security mechanisms. These endpoints with the correct Auth allow access w/o any sort of security device configuration on your end.
As I stated. On-prem is not supported. However, it is possible to get it working but you would be fully responsible for the setup and your own security. The following is a list of IPs & Domains that Okta leverages (The IP's are broken out by cell). It is likely possible your security team could allow this traffic through and NAT (or some other routing option) the traffic to the API endpoint of your on-prem device.
https://help.okta.com/en-us/content/topics/security/ip-address-allow-listing.htm