IBM QRadar SOAR: Configuring HTTP Proxy settings: Difference between revisions

From Wiki
Line 25: Line 25:




  <nowiki>manageAppHost proxy --http-proxy-url=http://proxy.corp.com:8080 --https-proxy-url=http://proxy.corp.com:8080 --no-proxy=<IP_SOAR>,<IP_SOAR_APP>,localhost,127.0.0.1,localhost.localdomain,corp.com,10.0.0.0/8</nowiki>
  <nowiki>manageAppHost proxy --http-proxy-url=http://proxy.corp.com:8080 \
  --https-proxy-url=http://proxy.corp.com:8080 \
  --no-proxy=<IP_SOAR>,<IP_SOAR_APP>,localhost,127.0.0.1,localhost.localdomain,corp.com,10.0.0.0/8</nowiki>
   
   



Revision as of 17:54, 27 November 2025

Configure proxy o main host

1) Connect to CLI, using resadmin user

2) Run command

sudo resutil configset -key proxyhost -s <ip address>
sudo resutil configset -key proxyport -i <port>


sudo systemctl restart k3s

Configure proxy on app host

3) Edit file /etc/systemd/system/k3s.service.env

and set

HTTP_PROXY=http://proxy.corp.com:8080 
HTTPS_PROXY=http://proxy.corp.com:8080
NO_PROXY=<IP_SOAR>,<IP_SOAR_APP>,localhost,127.0.0.1,localhost.localdomain,corp.com,10.0.0.0/8


manageAppHost proxy --http-proxy-url=http://proxy.corp.com:8080 \
   --https-proxy-url=http://proxy.corp.com:8080 \
   --no-proxy=<IP_SOAR>,<IP_SOAR_APP>,localhost,127.0.0.1,localhost.localdomain,corp.com,10.0.0.0/8

restart daemons

sudo systemctl daemon-reload
sudo systemctl restart k3s

Ver também