# ISC calling on-perm URLs using Web service connector **URL:** \ **Category:** SHF Discussion and Questions\ **Tags:** identityiq, sailpoint-identity-security\ **Created:** [January 8, 2025, 9:37pm UTC](https://developer.sailpoint.com/discuss/t/isc-calling-on-perm-urls-using-web-service-connector/96267 "2025-01-08T21:37:06Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![venus](https://avatars.discourse-cdn.com/v4/letter/v/35a633/32.png) [@venus](https://developer.sailpoint.com/discuss/u/venus)\ **Post date:** [January 8, 2025, 9:37pm UTC](https://developer.sailpoint.com/discuss/t/isc-calling-on-perm-urls-using-web-service-connector/96267/1 "2025-01-08T21:37:07Z")
> ‼ Please be sure you’ve read the [docs](https://developer.sailpoint.com/idn/docs/) and [API specs](https://developer.sailpoint.com/idn/api/getting-started) before asking for help. Also, please be sure you’ve [searched](https://developer.sailpoint.com/discuss/search?expanded=true) the forum for your answer before you create a new topic. ## Please consider addressing the following when creating your topic: - What have you tried? Add the on-prem hosts to no\_proxy variable in proxy.yaml. Created a Web service application using the on-perm server added to no proxy. - What errors did you face (share screenshots)? **HTTP 407 Proxy Authentication Required** - Share the details of your efforts (code / search query, workflow json etc.)? - What is the result you are getting and what were you expecting? Wondering why even going to the proxy though I have added the server to no proxy list. Any thoughts what I might be missing. We use VA with Proxy architecture for external URLs. ---
**Author:** ![sauvee](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/sauvee/32/23601_2.png) [@sauvee](https://developer.sailpoint.com/discuss/u/sauvee)\ **Post date:** [January 9, 2025, 2:32pm UTC](https://developer.sailpoint.com/discuss/t/isc-calling-on-perm-urls-using-web-service-connector/96267/2 "2025-01-09T14:32:37Z")
Can you show (scrabled of course!) the value in proxy.yaml. If you do a > echo $no\_proxy You will get the value that the system actually uses. If there are no values there, you might need to reboot the VA / ccg. ---
**Author:** ![venus](https://avatars.discourse-cdn.com/v4/letter/v/35a633/32.png) [@venus](https://developer.sailpoint.com/discuss/u/venus)\ **Post date:** [January 9, 2025, 4:21pm UTC](https://developer.sailpoint.com/discuss/t/isc-calling-on-perm-urls-using-web-service-connector/96267/3 "2025-01-09T16:21:23Z")
I did verify that every looks good and I see all IIQ hosts I have added to the list. I checked via env | grep no\_proxy and also docker.env. I did see no\_proxy hosts are listed correctly. I am wondering why ISC is sending request to proxy though I have added the host to no\_proxy property. ---
**Author:** ![sauvee](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/sauvee/32/23601_2.png) [@sauvee](https://developer.sailpoint.com/discuss/u/sauvee)\ **Post date:** [January 10, 2025, 10:36am UTC](https://developer.sailpoint.com/discuss/t/isc-calling-on-perm-urls-using-web-service-connector/96267/4 "2025-01-10T10:36:22Z")
That is really strange. I have not myself seen this behaviour, managing the proxy.yaml should be sufficient. Would it be possible to share (dummy) values you have set? ---
**Author:** ![venus](https://avatars.discourse-cdn.com/v4/letter/v/35a633/32.png) [@venus](https://developer.sailpoint.com/discuss/u/venus)\ **Post date:** [January 10, 2025, 3:16pm UTC](https://developer.sailpoint.com/discuss/t/isc-calling-on-perm-urls-using-web-service-connector/96267/5 "2025-01-10T15:16:44Z")
Here is our proxy.yaml sample https\_proxy: [http://proxy.myorgdomain.com:8081/](http://proxy.myorgdomain.com:8081/) http\_proxy: [http://proxy.myorgdomain.com:8081/](http://proxy.myorgdomain.com:8081/) no\_proxy: [diiq1.myorgdomain.com](http://diiq1.myorgdomain.com),[diiq2.myorgdomain.com](http://diiq2.myorgdomain.com),[diiq3.myorgdomain.com](http://diiq3.myorgdomain.com),[diiq4.myorgdomain.com](http://diiq4.myorgdomain.com) ---
**Author:** ![venus](https://avatars.discourse-cdn.com/v4/letter/v/35a633/32.png) [@venus](https://developer.sailpoint.com/discuss/u/venus)\ **Post date:** [January 10, 2025, 3:27pm UTC](https://developer.sailpoint.com/discuss/t/isc-calling-on-perm-urls-using-web-service-connector/96267/6 "2025-01-10T15:27:10Z")
When I do curl command everything works fine but When I use Web service connector in ISC with the same URLs is not working. ---
**Author:** ![sauvee](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/sauvee/32/23601_2.png) [@sauvee](https://developer.sailpoint.com/discuss/u/sauvee)\ **Post date:** [January 13, 2025, 8:48am UTC](https://developer.sailpoint.com/discuss/t/isc-calling-on-perm-urls-using-web-service-connector/96267/7 "2025-01-13T08:48:34Z")
The only difference I see with our proxy.yaml is that we have the no\_proxy separated by pipes, so in your example would be: > no\_proxy: [diiq1.myorgdomain.com|diiq2.myorgdomain.com|diiq3.myorgdomain.com|diiq4.myorgdomain.com](http://diiq1.myorgdomain.com%7Cdiiq2.myorgdomain.com%7Cdiiq3.myorgdomain.com%7Cdiiq4.myorgdomain.com) Would suggest to give that a shot. ---
**Author:** ![venus](https://avatars.discourse-cdn.com/v4/letter/v/35a633/32.png) [@venus](https://developer.sailpoint.com/discuss/u/venus)\ **Post date:** [January 13, 2025, 9:48pm UTC](https://developer.sailpoint.com/discuss/t/isc-calling-on-perm-urls-using-web-service-connector/96267/8 "2025-01-13T21:48:03Z")
@sauvee - I tried with double quote and also a regex. For example: “\*.example.com”. This works fine for the time being. I will try pipe instead of a comma later and will let update here. ---
**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\ **Post date:** [March 14, 2025, 9:48pm UTC](https://developer.sailpoint.com/discuss/t/isc-calling-on-perm-urls-using-web-service-connector/96267/9 "2025-03-14T21:48:39Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.