---
schema_version: "1"
id: 05bd5465b9bf3ca1a50f7ccea90025acbd55615dad7f68451931e681f8ec7a7b
title: gatewaySettings Entity
collection: tableau
version: next
locale: en-gb
portal_url: https://docs.salesforce.com/tableau/next/en-gb/server/entity_gateway.md
canonical_url: https://help.tableau.com/v0.0/server/en-gb/entity_gateway.htm
source_site: help.tableau.com
content_type: documentation
content_hash: cd16eb89bc45d88404ec97f01dad35a39cdbf4a9368b32d8a4cd42a6687df996
description: Reference for the gatewaySettings entity to configure the Tableau Server gateway via JSON.
---
[Skip to main content](#main-content)

# gatewaySettings Entity

You must configure the gateway settings for the Tableau Server computer.

Use the configuration file template below to create a json file. After you have filled in the options with the appropriate values, pass the json file and apply settings with the following commands:

`tsm settings import -f /path/to/file.json`

`tsm pending-changes apply`

If the pending changes require a server restart, the `pending-changes apply` command will display a prompt to let you know a restart will occur. This prompt displays even if the server is stopped, but in that case, there is no restart. You can suppress the prompt using the `--ignore-prompt` option, but this does not change the restart behaviour. If the changes do not require a restart, the changes are applied without a prompt. For more information, see [tsm pending-changes apply](https://help.tableau.com/v0.0/server/en-gb/cli_pending-changes.htm#pending-changes-apply).

### Gateway settings

The gateway settings in the template below specify the HTTP settings for Tableau Server. We recommend using SSL/TLS. Tableau Server is hard-coded to use port 443 for SSL/TLS. Therefore, if you enable SSL, you do not need to update the gatewaySettings entity.

### Configuration template

Use this template to configure the gateway settings.

**Important:** All entity options are case sensitive.

For more explanation about configuration files, entities and keys see [Configuration File Example](https://help.tableau.com/v0.0/server/en-gb/config_file_example.htm).

{
  "configEntities": {
	 "gatewaySettings": {
	  "\_type": "gatewaySettingsType",
	   "port": 80,
	   "sslRedirectEnabled": true,
	   "publicHost": "localhost"
	 }
	}			
 }

### Configuration file reference

This table includes all of the options that can be included with the `"gatewaySettings"` entity set.

\_type

Required.

Value: `"gatewaySettingsType"`

Do not change.

port

Specifies HTTP port. Default is port 80.

sslRedirectEnabled

Options: `true` or `false`.

publicHost

Specifies host name for http/s service.

trustedIPs

Specifies trusted IP addresses that communicate with Tableau Server. Trusted IP addresses include upstream proxy servers and servers that are used for trusted authentication with Tableau Server. See [Configuring Proxies and Load Balancers for Tableau Server](https://help.tableau.com/v0.0/server/en-gb/proxy.htm) and [Add Trusted IP Addresses or Host Names to Tableau Server](https://help.tableau.com/v0.0/server/en-gb/trusted_auth_trustIP.htm).

If you are running Tableau Server in a cluster then all other nodes of the cluster will automatically be included in the corresponding configuration file that this entity updates. Therefore, if you specify a new value for `trustedIPs`, then you must include the IP addresses for the other nodes in the value.

This option takes a list of strings, which requires passing each IP or host in quotes, separated by a comma (no space) and within brackets. For example: `["192.168.1.101","192.168.1.102","192.168.1.103"]` or `["webserv1","webserv2","webserv3"]`.

trustedHosts

Specifies trusted IP addresses that communicate with Tableau Server. Typically, this value contains a list of upstream proxy servers. The values in trustedHosts are used to determine client request targets.

If you are running Tableau Server in a cluster then all other nodes of the cluster will automatically be included in the corresponding configuration file that this entity updates. Therefore, if you specify a new value for `trustedIPs`, then you must include the IP addresses for the other nodes in the value.

This option takes a list of strings, which requires passing each IP or host in quotes, separated by a comma (no space) and within brackets. For example: `["192.168.1.101","192.168.1.102","192.168.1.103"]` or `["webserv1","webserv2","webserv3"]`.