How To
Summary
QRadar automatically exposes configured proxy information to apps in the form of environment variables injected at runtime. This allows apps to support any proxy that QRadar is configured with.
Steps
Proxy Values from Environment Variables
QRadar injects a number of environment variables into apps to expose proxy information, libraries such as Python requests and QPyLib will automatically pick up and use the following variables:
https_proxy
http_proxy
no_proxy
Also injected are replicated equivalents which are designed to be manually retrieved and used as proxy variables:
QRADAR_HTTPS_PROXY
QRADAR_HTTP_PROXY
QRADAR_NO_PROXY
Please note that manually setting up the proxy for a Python app is not necessary, QRadar provides the
https_proxy
,http_proxy
, andno_proxy
environment variables which are automatically picked up by Python libraries such as requests and QPyLib. If using another language/framework, check for built in support of these variables - if it is not supported the manual proxy values can be used.
Configuration with nva.conf
The setting APP_PROXY_ENABLED
in the nva.conf
file determines if the following are injected:
https_proxy
http_proxy
no_proxy
If APP_PROXY_ENABLED=true
or APP_PROXY_ENABLED
is not explicitly set the variables are injected, if APP_PROXY_ENABLED=false
they are not injected.
The setting APP_PROXY_ENV_VARIABLES_ENABLED
in the nva.conf
file determines if the following are injected:
QRADAR_HTTPS_PROXY
QRADAR_HTTP_PROXY
QRADAR_NO_PROXY
If APP_PROXY_ENV_VARIABLES_ENABLED=true
or APP_PROXY_ENV_VARIABLES_ENABLED
is not explicitly set the variables are injected, if APP_PROXY_ENV_VARIABLES_ENABLED=false
they are not injected.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
30 March 2021
UID
ibm16437517