ISC calling on-perm URLs using Web service connector

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

:bangbang: Please be sure you’ve read the docs and API specs before asking for help. Also, please be sure you’ve searched 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.

2

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.

3

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.

4

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?

5

Here is our proxy.yaml sample

https_proxy: http://proxy.myorgdomain.com:8081/
http_proxy: http://proxy.myorgdomain.com:8081/
no_proxy: diiq1.myorgdomain.com,diiq2.myorgdomain.com,diiq3.myorgdomain.com,diiq4.myorgdomain.com

6

When I do curl command everything works fine but When I use Web service connector in ISC with the same URLs is not working.

7

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

Would suggest to give that a shot.

8

@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.

9

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.