| Reference: | https://doc.wallix.com/en/bastion/12.3/rn-en-12.3.2.html |
|---|---|
| Date: | 2026-03-12 |
| Copyright: | © 2026 WALLIX |
Contents
This version includes all the improvements and new features implemented from WALLIX Bastion 12.0 and listed in the sections below.
Following the removal of the DRBD-based High Availability feature in Bastion 12, the eth1 network interface can now be configured and used like any other regular network interface.
No improvement was part of this version.
WALLIX Bastion now supports Kerberos authentication on RDP Proxy primary connection. This provides single sign-on for Active Directory users.
The following features and improvements have been implemented in this version:
Improve the Target groups configuration in WALLIX Bastion. It has been redesigned with a simplified, modern interface. Group configuration is now faster and more intuitive: targets can be added in just a few clicks, deletions are easier, and all actions are performed from a single, unified page.
Improve session history in WALLIX Bastion. The new interface provides clearer and smoother monitoring of activities performed within a session. This redesign makes it easier to identify critical behaviors and delivers a more streamlined user experience.
Increase the password history for WALLIX Bastion and Access Manager local accounts from 15 to 50, preventing reuse of old passwords and enhancing account security.
WALLIX Bastion now offers enhanced Web target administration and analysis, giving teams greater control and visibility. Web session activity can be exported in CSV format, making audits and analysis faster and more efficient. A new notification capability provides real-time monitoring of access to critical Web applications, strengthening security and operational responsiveness. Web access also supports account mapping through transformation rules, expanding authentication options and offering more flexibility in access management.
Web sessions managed with Web Session Manager now include advanced auditing capabilities. These capabilities include session video playback and metadata downloads, which improve traceability, compliance, and analysis of risky behaviors. Web session logs can also be forwarded to SIEM tools, enabling centralized visibility and enhanced incident detection.
The analysis of large files in WALLIX Bastion is now optimized for all sessions supporting file transfers. A new parameter allows configuring the analysis timeout for ICAP server responses, ensuring reliable, complete, and secure transfers even for very large files.
Deprecate the kerberos-password method in favor of the standard kerberos method for Kerberos authentication.
The following features and improvements have been implemented in this version:
The following features and improvements have been implemented in this version:
The following features and improvements have been implemented in this version:
No improvement was part of this version.
The following features and improvements have been implemented in this version:
The new WALLIX Web Session Manager solution provides secure access to web applications using remote browser isolation technology. Users can seamlessly access web targets directly from their browser via WALLIX Bastion, without needing plugins or add-ons. Credential can be injected securely to prevent user accessing them. This new native component integrates seamlessly into the WALLIX Bastion ecosystem. Additionally, administrators can control each session by preventing unauthorized redirections or allowing them and managing common behaviors within a user's web session, such as copy/paste, file upload/download, etc.
To enhance security and simplify access management, API keys can now be linked to profiles. Default profiles have been introduced to ensure a standardized, reliable configuration tailored to each ecosystem with Access Manager (compatibility starting from version WALLIX Access Manager 5.2).
When upgrading to this version, all existing API keys are automatically updated to use the product_administrator profile.
WALLIX Bastion and WALLIX Access Manager now support integration with identity providers using the OpenID Connect (OIDC) standard. This enhancement facilitates centralized user management across the entire ecosystem, streamlining deployment within existing infrastructures. With OIDC, users can enjoy Single Sign-On (SSO), making access more seamless and efficient.
The new WAMUT client is now available for managing Universal Tunneling sessions on your workstation. It features a graphical interface that enhances visibility into the current session state. Additionally, the user workflow is now unified across both WALLIX Bastion and WALLIX Access Manager.
The Seamless Connection feature offers a new mode, which no longer requires admin rights on the user workstation. Users still enjoy the same seamless experience, making Universal Tunneling easy to adopt. This new mode also enhances user experience with fat clients using a static port on the user workstation (like TIA Portal, SoMachine, etc.). To enable the workflow for WALLIX Access Manager users, both WALLIX Bastion and WALLIX Access Manager must be upgraded to versions 12.2 and 5.2, respectively.
A new authentication for SSH proxy users based on FIDO2 hardware is available. Transfer with agent forwarding (SSH proxy to target) is also supported, if the client used supports it.
The following features and improvements have been implemented in this version:
The following features and improvements have been implemented in this version:
API keys can be linked to a non-editable profile, restricting the rights of users logging in with an API key. New default non-editable profiles have been introduced to simplify API key configuration with Access Manager (compatibility starting from version 5.2).
Bastion supports OpenID Connect, enabling seamless authentication with identity providers supporting the standard. This integration enhances security and simplifies user access management. Administrators benefit from streamlined identity federation and improved access control. With Single Sign-On (SSO), users can access Bastion without repeatedly entering credentials.
The RDP session resolution can be enforced by the administrator through the RDP connection policy. This new option facilitates connections to servers and systems that support only a specific resolution, preventing display issues or session crashes.
In network and AD discovery, latency is now measured for each discovered devices and available in the scan job results.
The following features and improvements have been implemented in this version:
Bastion 12 introduces a new system upgrade procedure. As a result, if you have a WALLIX Bastion prior to version 12 and wish to upgrade to Bastion 12, refer to chapter 6 of the Deployment Guide.
Bastion 12 introduces a new minor upgrade process to enhance efficiency and user experience. The new process relies on the wabupgrade account making it easier to upgrade from version 12 to version 12.X. Refer to the Deployment Guide, chapter 7 for detailed instructions.
Bastion 12.0.1 introduces a new default behavior for the “Enable Kerberos” option, enabling it by default which means that NLA Kerberos is now the first attempted authentication method. However, when restoring the backup of a Bastion anterior to 12.0.1, the configuration of authentication mechanisms is not modified. That means that values set for NLA and Kerberos are restored as defined in that backup file. For example, if Enable Kerberos option was disabled, this option remains disabled after the restoration, even if the option is now enabled by default.
Bastion 12.0.1 also introduces new options for RDP target connections. To ensure that the target cannot negotiate an authentication protocol lower than that specified by the connection policy, fallback mechanisms are disabled by default. However, for greater granularity, you can modify fallback mechanisms for connections to RDP targets. The options are:
We strongly encourage you to review your connection policies and make any necessary updates to the fallback mechanism to better suit your needs.
WALLIX follows the Microsoft recommendation to use the domain account for RDP sessions. As a result, WALLIX recommends to use NLA Kerberos authentication when using target account in Active Directory. That means the “Allow NLA NTLM fallback”, “Allow TLS only fallback”, and “Allow RDP legacy fallback” options must be disabled.
When using a local account on a target, Microsoft and WALLIX recommend:
For earlier targets (windows 2003 and older), you must enable the “Allow RDP legacy fallback” option.
The following features and improvements have been implemented in this version:
This version includes all fixes implemented from WALLIX Bastion 12.0 and listed in the sections below.