Set environment variables globally for all apps
Use the Global Environment Variables page to set environment variables that all apps and the Splunk Phantom runtime environment use globally.
- From the Main Menu, select Administration.
- Select Administration Settings > App Environment.
- In the Name field, specify HTTP_PROXY, HTTPS_PROXY, or NO_PROXY depending on the type of proxy connection.
- The Value field for HTTP and HTTPS proxy configurations must include the protocol, hostname or IP address, and port of the proxy server.
Values must be typed using lowercase letters.
For example:<protocol>://<hostname/ip address>:<port>
- The Value field for NO_PROXY configurations must contain the IP, hostname, or domain of the asset.
- The Secret option encrypts the Value field and prevents the field from being displayed.
- The Value field for HTTP and HTTPS proxy configurations must include the protocol, hostname or IP address, and port of the proxy server.
When configuring the system to use an HTTP or HTTPS proxy, Splunk Phantom requires that you except calls to 127.0.0.1 from the proxy list. You must set the environment variable NO_PROXY to 127.0.0.1 to make localhost REST calls without being diverted to the proxy.
You can also apply environment variables to assets individually in the Asset Settings tab for any configured asset. The asset environment variables always take priority over global environment variables.
For apps that use requests, configure both HTTPS and HTTP environment variables to direct all app traffic through the proxy server.
Manage your organization's credentials with a password vault | Add tags to objects in Splunk Phantom |
This documentation applies to the following versions of Splunk® Phantom (Legacy): 4.8, 4.9
Feedback submitted, thanks!