Parasoft SOA test - while running API tests REST client through Azure pipeline run , proxy error
hi @benken_parasoft , while running my tests locally I don't get proxy error 407 authentication required , but while running with Agent on server through Azure CICD pipeline, I get error as its running with a common functional IDs and not in my own Id, however other test steps in the testcase like connecting to DB, accessing Kibana , connection to elastic search while Proxy is enabled [before running] is not working and i see that 407 only for proxy error . Screen shots attached
Answers
-
0 -
0 -
0 -
Your screenshots are highlighting "Authorization" headers in your test. Incorrect Authorization would result in HTTP 401 (unauthorized) and not a 407.
In contrast, HTTP 407 means Proxy Authentication failed. This is solved with a Proxy-Authorization header which is not the same as the Authorization header. In SOAtest, you do not explicitly add Proxy-Authorization headers to your clients. Instead, you configure this in preferences under Parasoft > Preferences > Proxy > Proxy Authentication.
0 -
No @benken_parasoft , that is fine for local run but we are running in Azure pipelines and agent will run this through power shell scripts through SOA CLI [command line]
0 -
When we run in Azure pipelines, with an agent running in server, i cannot manually open the Parasoft tool from server machine , update proxy and run, because this may work for me but not for all others running in same agent same machine. Hence there should be some solution of power shell script to involve this proxy bypass through SOA CLI
0 -
The HTTP 407 proxy authentication failures should have nothing to do with Microsoft PowerShell. SOAtest's behavior shouldn't be affected by what type of shell or command interpreter you are using. Instead, the proxy authentication failures likely have to do with what's configured in the OS. By default, SOAtest attempts to use default proxy settings as defined in the OS. If the OS is configured to use a HTTP proxy server then SOAtest will also use it by default.
In SOAtest Desktop you can explicitly disable or configure proxy settings under Parasoft > Preferences > Proxy. Most SOAtest-specific preference settings get saved in the workspace in the file ".metadata/.plugins/org.eclipse.core.runtime/.settings/com.parasoft.ptest.common.eclipse.core.web.prefs". For example, if you wanted to disable "Use system proxy configuration" then this gets saved in this prefs file as "proxy_use_system_proxy_configuration=false". You can copy a prefs file like this into the SOAtest workspace on any machines where you run soatestcli.
0 -
@benken_parasoft pls see the error
0 -
0 -
any help @benken_parasoft
0 -
I have nothing else to recommend. Did you see my last comment? I tried to explain in a bit of detail.
If a proxy is configured on the agent then SOAtest would need to know the username and password for that proxy (not your service endpoint under test). Otherwise, you can try telling SOAtest not to use system proxy settings in case that works. You can configure the proxy settings on some SOAtest Desktop installation then copy the prefs file I mentioned to any hosts where you are running soatestcli.
0