# default securegateway.conf with samples for configuration of Splunk Secure Gateway App

[setup]
# Set address of the Spacebridge service.  By default it is set to prod.spacebridge.spl.mobi
spacebridge_server=http.us-west-2.spacebridge.splunkcx.com

# This controls the log_level for application logs, by default this is set to INFO
# If you need more detailed logs set to DEBUG
log_level = INFO

# Set the request timeout in seconds seen at the async request level.  Default 15s
# async_timeout = 15

# This setting controls the interval in which the Search Head will query if it is the Captain in a SHC
# The Splunk Secure Gateway App currently processes all requests through the Captain in a SHC
cluster_monitor_interval = 300

# Enable cluster mode.  If enabled, the modular inputs will run on every member of the SHC.  Disabled, it will only run
# on the captain.
cluster_mode_enabled = false

mtls = false

[client]
# Set the request timeout in seconds seen at the client level.  Default 30s
request_timeout_secs = 30

[websocket]
# When a websocket disconnects reconnection code retries with exponential back-off to a maximum value
# The reconnect_max_delay is the maximum reconnection delay in seconds, default is 60s
reconnect_max_delay = 60

[subscription]
# The subscription_manager_modular_input will run for a period defined by the manager_lifetime_seconds configuration before restarting the process
# The default lifetime is 3600s
manager_lifetime_seconds = 3600

# The subscription_manager_modular_input will poll new subscription requests from clients at an interval defined by the manage_interval_seconds
# The default interval is 0.1s.  If the Search Head instance is not performant this may be an option to reduce API calls to the host.
manager_interval_seconds = 0.2

# [dashboard]
# The dashboard_list_max_count setting will limit the number of dashboards returned in the dashboard list API
# If the dashboard list is timing out on clients this a helpful setting to limit the returned dashboards
# This is primarily a setting you would set while debugging an issue
# dashboard_list_max_count = 10000

# [proxyConfig]
# If set, Splunk Secure Gateway App sends all HTTP requests through the proxy server that you specify.
# No Default.  Example formats:
# http_proxy = http://user:password@proxyIP:proxyPort
# http_proxy = user:password@proxyIp:proxyPort,
# http_proxy = http://proxyIp:proxyPort
# http_proxy = proxyIp:proxyPort

# If set, Splunk Secure Gateway App sends all HTTPS requests through the proxy server that you specify.
# No default.  Example formats:
# https_proxy = http://user:password@proxyIP:proxyPort
# https_proxy = user:password@proxyIp:proxyPort,
# https_proxy = http://proxyIp:proxyPort
# https_proxy = proxyIp:proxyPort

# If set, allows registration attempts for a particular user to be validated using a webhook service.
# If this service returns a 200 status code, registration will continue. Otherwise registration will fail.
# The username is passed as a query parameter to the webhook as a GET request. Example formats:
# [registration]
# registration_webhook_url=https://hostname:port/endpoint
# webhook_verify_ssl= true