Privileged Remote Access 25.1.2 release notes

June 10, 2025

🆕New features and enhancements

This is a maintenance release and there are no new features or enhancements.

🛠️Issue resolved

Product areaDescriptionResolution
Jump ClientNon-ASCII characters in Windows Domain names could indirectly cause jump session failures.The product now handles non-ASCII characters in Windows Domain names correctly.
Jump ClientJump Clients that are in Service mode on Linux do not display all of System Information.All System Information now displays regardless of Jump Client mode.
Jump ClientWhen you select the Windows key during screen sharing it has unexpected results.Selecting the Windows key during screen sharing now pops a menu in the correct context.
Jump ClientWeb Jump does not inject credentials if a form is cross-domain.Web Jump credential injection in cross-domain forms works as expected.
Jump ClientJump Clients do not always read local proxy information.Jump clients now correctly read all local proxy information.
Rep consoleCustomer client incorrectly identifies Windows 11 as Windows 10.Operating system is now correctly identified.
Web JumpWhen you attempt to initiate a web jump it intermittently pauses.Web Jumps now perform as expected.
JumpointRDP jumps with non-ASCII characters in the password failed when made through a Linux Jumpoint.RDP jumps with non-ASCII characters in the password now work as expected.
RDP JumpRDP Jumps to older systems such as Windows XP and Server 2003 fails to connect.Corrects built-in RDP Jumps to older systems such as Windows XP and Server 2003. Bring Your Own Tech (BYOT) may still fail.
Security ProviderSAML redirect to console was not working.SAML redirection to console now works as expected.
Security ProviderSome certificates were not being parsed correctly, which results in validation failures.Certificates with unusual date formats now validate correctly.
Email ConfigurationAuto-generated emails from the appliance would fail to send if email authentication was set to userid+password.Auto-generated emails from the appliance work as expected.
Web consoleWeb console logins fail with “Failed to authenticate” message.Authentication failures when multiple identity providers are active is fixed

📝Requirements

  • Requires Base 7.4.0.
  • Requires ECM 1.6.2+.
  • Requires Integration Client 1.7.5.
  • Supports upgrades from 24.2.4 PA+
  • Supports ThinClient Protocol 2.1 and 2.2
  • Supports ECM Protocol 1.6
  • Includes VSC 1.2.9.1

Before upgrading, ensure any SSL certificates used are either from a trusted Certificate Authority, or, for self-signed certificates, the certificate is either trusted on all endpoints or explicitly included in their installation.

©2003-2025 BeyondTrust Corporation. All Rights Reserved. Other trademarks identified on this page are owned by their respective owners. BeyondTrust is not a chartered bank or trust company, or depository institution. It is not authorized to accept deposits or trust accounts and is not licensed or regulated by any state or federal banking authority.