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

A normal upgrade restores the existing Tomcat configuration. This preserves customer ports, SSL, and authentication settings, but it also means the new hostname protection in the packaged server.xml is not automatically applied.

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">
```

À l'intérieur de ce moteur, avant l'hôte localhost existant, ajoutez :

<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" />
```
Conserver toutes les autres entrées existantes à l'intérieur de cet hôte. Ajouter l'alias comme un véritable élément XML, et non à l'intérieur d'un commentaire. Utiliser uniquement le nom d'hôte, pas https://, un port ou un chemin.
Séparément, pour correspondre à la nouvelle configuration de redirection HTTPS packagée, ajoutez transportGuaranteeRedirectStatus="308" à la balise d'ouverture existante LockOutRealm, en conservant ses autres paramètres :
```
<Realm className="org.apache.catalina.realm.LockOutRealm"
       transportGuaranteeRedirectStatus="308">
```
This setting does not, by itself, turn an HTTP-only installation into an HTTPS installation.

Enregistrer le fichier et redémarrer le service. Sans les étapes 1 à 3, une installation mise à niveau devrait continuer à fonctionner, mais la nouvelle protection du nom d'hôte Tomcat ne sera pas active. L'étape 4 applique le paramètre de redirection HTTPS distinct inclus dans ce correctif.

New Customers Installing This Patch

A fresh installation already contains the new Tomcat protection. Before users access Connect through a DNS name, stop the service and add that name inside the localhost Host in 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.

Changements de comportement à prévoir

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.
Les images nouvellement enregistrées sont traitées pour supprimer les métadonnées. Les images inhabituelles peuvent être rejetées ou apparaître légèrement différentes.
Les messages d'échec de connexion divulguent moins d'informations.
Attachment downloads are no longer intended to remain in the browser cache for one year, so repeated downloads may use more network traffic.
Les installations HTTP restent prises en charge ; le correctif ne nécessite pas de nouveau certificat SSL.

Dans cette section: