Privileged Remote Access 24.2.4 release notes
3 months ago by ReadMe API
November 19, 2024
Requirements
- Requires Base 7.3.0.
- Requires ECM 1.6.2.
- Requires Integration Client 1.7.5.
- Supports upgrades from PRA 23.2.3+.
- 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.
Issues resolved
Product Area | Description | Resolution |
---|---|---|
Site login | When logging into a failover or clustered appliance, users were sometimes directed to an unavailable page, resulting in an Internal Server error. | Users are now directed to the Status page. |
Site logging | When using SSH to access a site, large warning logs were visible. | Deprecation warnings are no longer shown in production logs, only in debug mode. |
Access console | When attempting Web Jump injection, loading activity would interfere with the expected behavior, particularly in single-page applications. | Web Jump injection now completes as expected. |
Jump Clients | When updating to PRA 24.1.1, Jump Clients updating via Jump Zone Proxy would appear as though they never finished. | Jump Client updates now correctly show completion. |
Jump Approvals | When attempting to respond to a session authorization request when not already logged in, users were directed to their last used page rather than the Jump Approvals page. | Users are now directed to the Jump Approvals page as expected. |
Site login | Daylight saving time would cause time-based one-time password authentication to fail. | TOTP authentication now succeeds regardless of daylight saving time changes. |
Access console | When creating over 50 Shell Jump Items, generic credentials could not be assigned to some of them. | Shell Jump Items can now be assigned generic credentials, even when more than 50 have been created. |
Desktop and web access console | A user was experiencing multiple outages, causing the access console to fail. | |
Access console | Attempting a SQL Tunnel Jump through the access console running on a Windows 11 computer would time out and fail. | An access console running on Windows 11 can now successfully initiate a SQL Tunnel Jump. |
Site login | If a SAML security provider was the only authentication option and Passwordless FIDO2 Authentication was turned off, deactivating the SAML provider would result in a non-functional login button when attempting to log in. | In this scenario, the authentication method now reverts to username and password. |
Access console | Because the Azure SQL architecture differs significantly from traditional Microsoft SQL servers, it was difficult to enable connections to Azure SQL databases through a SQL Server Jump Item. | A SQL Server Jump Item can now be used to connect to an Azure SQL server. |
Access console | The Windows session lock and user login states failed to reflect the current session, causing inconsistencies in permission assignments. | Permissions are now consistent for both session types. |
/login > Reports page | An attempt to view a session recording on a cloud Atlas site would result in an internal server error. | Session recordings can now be viewed. |