To debug this kind of issues, you would first capture the request sent by the webservice plugin by configuring the log level in the log4j conf file. Then, if everything looks fine, you can try this same request from a tool such as SOAPUI and see what you get. You might see in the headers if it's the proxy that answered with an http 401 or the target web server.
I asked to remove any kind of block rule from the proxy/firewall, but I obtain the same answer.
Do you know if there is any known issue with webservice on ars 7.1 sp2?
has this issue been resolved, I am facing the similar issue for one of the WSDL while consuming. Any help here is appreciated.
I am also facing the same issue, are you able to fix it??
I am on Remedy V7.6.