What's New in Connect 2026.3

Version: 2026.3.1.4

Release Date: October 14, 2026

See the complete Connect 2026.3 Release Notes.

New Features

There are currently no new features for this release.

Security Updates

This release strengthens Connect’s upload validation, image processing, authentication error handling, response security headers, logout and cache behavior, and hostname protection.

Existing Customers Upgrading

Una actualización normal restaura la configuración existente de Tomcat. Esto preserva los puertos del cliente, SSL y la configuración de autenticación, pero también significa que la nueva protección de nombre de host en el server.xml empaquetado no se aplica automáticamente.

To enable it, stop the Alteryx Connect service and back up C:\Program Files\AlteryxConnect\conf\server.xml (or the equivalent path for a custom installation). Edit the existing file. Do not replace the whole file, as it may contain customer-specific settings:

In the existing <Engine> opening tag, change only defaultHost to invalid.invalid:
```
<Engine name="Catalina" defaultHost="invalid.invalid">
```

Dentro de ese Engine, antes del Host localhost existente, agrega:

<Host name="invalid.invalid" appBase="blocked-webapps"
      deployOnStartup="false" autoDeploy="false">
  <Valve className="org.apache.catalina.valves.ErrorReportValve"
         showReport="false" showServerInfo="false" />
</Host>

Inside the existing <Host name="localhost" ...>, add an alias for each hostname Tomcat receives and add the error-report Valve if it is not already present:
```
<Alias>connect.example.com</Alias>
<Valve className="org.apache.catalina.valves.ErrorReportValve"
       showReport="false" showServerInfo="false" />
```
Keep all other existing entries inside that Host. Add the alias as a real XML element—not inside a comment. Use only the hostname, not https://, a port, or a path.
Separately, to match the new packaged HTTPS-redirect configuration, add transportGuaranteeRedirectStatus="308" to the existing LockOutRealm opening tag, retaining its other settings:
```
<Realm className="org.apache.catalina.realm.LockOutRealm"
       transportGuaranteeRedirectStatus="308">
```
Esta configuración no convierte por sí sola una instalación solo HTTP en una instalación HTTPS.

Save the file and restart the service. Without steps 1–3, an upgraded installation should continue to operate, but the new Tomcat hostname protection will not be active. Step 4 applies the separate HTTPS-redirect setting included in this patch.

Nuevos clientes que instalan este parche

Una instalación nueva ya contiene la nueva protección de Tomcat. Antes de que los usuarios accedan a Connect a través de un nombre DNS, detén el servicio y añade ese nombre dentro del Host localhost en C:\Program Files\AlteryxConnect\conf\server.xml:

<Alias>connect.example.com</Alias>

Restart the service. Without the alias, localhost access works, but requests using the unconfigured hostname may return 404. Do not change defaultHost back to localhost.

Reverse-Proxy or Load-Balancer Deployments

Configure an alias for the hostname that the proxy sends to Tomcat. If the proxy replaces the public hostname with an internal one, add the internal hostname as an alias too.

If the immediate proxy connects to Tomcat from a non-local IP address, add that IP to the existing [global] section of C:\Program Files\AlteryxConnect\ac_work\alteryx_connect.properties. For example, if Tomcat sees the proxy as 10.20.30.40:

connect.trusted-proxies=127[.]0[.]0[.]1|::1|0:0:0:0:0:0:0:1|10[.]20[.]30[.]40

Replace 10.20.30.40 with the actual proxy IP; retain the loopback entries. This setting accepts an IP-matching regular expression, not a DNS hostname or an end-user IP. Direct-access installations, or proxies connecting from loopback, need no change. If a non-local proxy is not configured, valid logins can still succeed, but auditing and IP-based login controls may identify multiple users by the shared proxy IP.

Cambios de comportamiento que puedes esperar

New attachment and diagram uploads may be rejected if they exceed the configured limit or have an unsupported, mismatched, or unsafe file type. Existing stored files are not bulk-modified.
Las imágenes recién guardadas se procesan para eliminar los metadatos. Las imágenes inusuales pueden ser rechazadas o aparecer ligeramente diferentes.
Los mensajes de inicio de sesión fallido revelan menos información.
Attachment downloads are no longer intended to remain in the browser cache for one year, so repeated downloads may use more network traffic.
Las instalaciones HTTP siguen siendo compatibles; el parche no requiere un nuevo certificado SSL.

En esta sección: