Re: DAST API not working with GetResponse failed error after running

We are running Fortify  23.1 as an on premises solution. Docker DAST API does not connect or work in SSC Software security Centre after running CLI script using CLI Config Tool.

We are running Windows Server 2019 on an internal proxied network

C:\ScanCentral_DAST_23.1\ScanCentral_DAST_23.1\ScanCentral DAST - CLI Config Tool\ConfigurationToolCLI>DAST.ConfigurationToolCLI.exe configureEnvironment --mode manage --settingsFile settingsFile.json --outputDirectory ScanCentralDAST
2025-01-22 10:10:21 - Starting DAST.ConfigurationToolCLI, Application Version: 23.1.0.180.
Start processing HTTP request POST https://debricked.com/api/login_refresh
Sending HTTP request POST https://debricked.com/api/login_refresh
Received HTTP response headers after 2119.4782ms - 200
End processing HTTP request after 2153.4104ms - 200
GetResponse failed for https://servername.mysite.co.za/ssc/api/v1/tokens. System.Net.WebException: The remote server returned an error: (503) DNS Fail.
   at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
--- End of stack trace from previous location ---
   at DAST.SSC.SscRESTfulService.GetResponse(HttpWebRequest request)
Failed to get SSCServiceAccountToken

After running the script we get this error DAST API is not working in SSC.

  • 0  

    Technically, you should be able to get the solution working with that error message as long as you defined a proxy in SC DAST Config. All we are doing with the config tool is testing whether the SSC URL and credentials are correct. Ideally, we would like for there NOT to be a proxy between SSC, LIM, SC DAST API and other SC DAST components.

    Can you access the SC DAST API Swagger page?