Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-7734

NO_PROXY environment variables have no effect in zync-que when connecting to the Admin Portal domain

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 2.10 GA, 2.11.0 GA
    • Zync
    • False
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Hide

      1. Configure some proxy url with HTTP_PROXY or HTTPS_PROXY in zync-que, for example:
      http_proxy: http://server-proxy.some.domain.ch:8080
      https_proxy: http://server-proxy.some.domain.ch:8080
      no_proxy: .some.domain.ch,localhost,.svc.cluster.local
      2. Test zync integration in 3scale by creating / updating a client
      3. Synchronization will fail with logs similar to the attachment (depending on what the proxy returns)

      Show
      1. Configure some proxy url with HTTP_PROXY or HTTPS_PROXY in zync-que, for example: http_proxy: http://server-proxy.some.domain.ch:8080 https_proxy: http://server-proxy.some.domain.ch:8080 no_proxy: .some.domain.ch,localhost,.svc.cluster.local 2. Test zync integration in 3scale by creating / updating a client 3. Synchronization will fail with logs similar to the attachment (depending on what the proxy returns)

      Configuring the environment variables no_proxy and/or NO_PROXY have no effect in zync-que and the proxies configured with HTTPS_PROXY and HTTP_PROXY are applied regardless of the whitelisted domains. This seems to only affect connections towards the Admin Portal domain: no_proxy is effective for the connections to RH-SSO.

        1. zync-que-log.txt
          4 kB

              Unassigned Unassigned
              rhn-support-sillumin Samuele Illuminati (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: