| 37043 |
In this release, User Backup from HySecure gateway V5.4 Service Pack 5 will not restore the Custom Web Template used for Reverse Proxy-based Web Applications. |
| 37025 |
User Backup from HySecure gateway V5.4 Service Pack 5 will not restore Schedule Sync for Multi-Site Sync in this release. |
| 36980 |
Native users cannot change their password via Passwordless login when “User must change Password at next logon” is set. |
| 36938 |
In this release, Sites backed up from HySecure gateway version 5.4 Service Pack 2 will not be restored through User Backup. |
| 36932 |
If host entries for host name-based reverse proxy (HBRP) applications are not restored through a user backup due to the exclusion of host file entries in the design, it may lead to NGINX service downtime caused by host resolution failures. Workaround: Administrators can manually add host file entries and restart the NGINX service through SSH for all HySecure gateway nodes. |
| 35925 |
In this release, the change password feature for Google LDAP users will not work through the Management Console and HyLite Portal. |
| 35866 |
In this release, resetting passwords and unlocking accounts through the Self-Service Portal will not be supported for Google LDAP directory users. |
| 35516 |
In this release, an issue has been observed where the Security officer/ Administrator cannot reset the password for LDAP users via the HySecure management console. |
| 35250 |
Incorrect spelling of authenticated during biometric authentication. |
| 35072 |
This release has observed an issue where even “Disabled” devices will be listed when the filter is applied to show only “Enabled” devices. |
| 34906 |
In this release, a timestamp has been added to the command line history. The timestamp will be when this Service Pack is applied for all the commands executed before. |
| 33827 |
HySecure gateway doesn’t allow the identification of different primary/alternate endpoints with different ports used for UDP and TCP. |
| 33424 |
Users cannot access RDP and other types of applications when compression is enabled on the HySecure gateway. |
| 32362 |
In this release, users may be unable to access SSH for specific servers through HyLite Portal. |
| 31036 |
With different authentication and access sites, app access will fail through the App Tunnel Pool. |
| 30948 |
Single Sign On for RDP-based applications will not work if the common account password contains < or & character. |
| 29282 |
In the access filter, when a user tries to delete an access filter policy linked with an ACL, a false admin log of deletion is generated. |
| 29238 |
In this release, the user may get a “Bad NGINX gateway” error intermittently while accessing hostname-based reverse proxy Web apps for the first time through the HyLite Portal. |
| 29196 |
In this release, SSL port change after applying user backup will reflect on the management console, but login will fail on the new port. |
| 29084 |
If applications are filtered based on the Reverse Proxy method, the search prompt will clear once the search is completed. |
| 28920 |
ARS application will not be accessible as a URL rewriting-based reverse proxy application. Although it will be accessible if published as a hostname-based reverse proxy application. |
| 28639 |
Unlocking user accounts is only supported for AD and native HySecure users. |
| 28613 |
If the hostname of the HySecure gateway has been modified, attempting to log in with a FIDO security key as an MFA option will fail to validate and log in. |
| 28246 |
An SMS OTP will be generated when opting for face authentication for MFA during Service Provider-initiated login that redirects to the ADFS server for authentication. |
| 27497 |
The license validation service runs every 100 seconds and updates the license data from the database table; therefore, it may take 105 seconds to reflect new licenses on all nodes. |
| 27495 |
Ensure that HySecure Services and Syncing services are running on all nodes in the dashboard in the HySecure management console before applying the License. The license gets synchronized among nodes and does not revert in case of HA failover. |
| 27303 |
This release does not support FIDO key registration with Firefox on Linux and Mac devices. |
| 27295 |
In this release, users cannot register for FIDO through iOS devices. |
| 27279 |
In this release, if a Web Application Firewall (WAF) exists between the HySecure gateway and the HySecure client, then the Management console will not load. |
| 27095 |
Only activity logs related to app access will be generated in this release, while no activity logs will be generated for app connect. |
| 26925 |
In this release, modifying any Site group reset button will not work. |
| 26635 |
In case values are not configured properly against the phone attribute in AD, OTP is sent to a null mobile number, which may be observed on the HyLite login page. |
| 26634 |
In this release, multiple phone attributes are not supported. Only the first attribute will be used for login if multiple phone attributes are added. |
| 26625 |
After logging in with passwordless authentication, a single sign-on into the assigned application will not work for the user. |
| 26619 |
While navigating back from process path modification in the App Whitelisting rule, the administrator will face an error in displaying the data. |
| 26531 |
In the Allow system context rule of App whitelisting, windir\System32\dllhost.exe path appears twice when the paths are restored. |
| 26234 |
In the remote application launched in the HyLite portal via Chrome/Safari browser, the remote console is not resized while accessing the keyboard. |
| 26130 |
If the password of a common user account contains special characters “&” and “%,” then the password may not save for a Single sign in the HySecure application in the management console. |
| 25924 |
In a remote application launched in the HyLite portal via Chrome/Safari browser, selected data is getting unselected once a user tries to right-click. |
| 25920 |
In a remote application launched in the HyLite portal via the Android browser, the User needs to press multiple times (5-6 times) to delete a single word. |
| 25861 |
The incorrect error message “Invalid inputs” will appear on the HySecure client while logging in with UPN. “If UPN supports username in the client,” is unchecked in Client settings. |
| 25856 |
The error message will appear truncated during session reauthentication if the user enters the wrong OTP value. |
| 25825 |
After applying this hotfix, the Security Officer cannot apply a new Service pack/Upgrade patch if the gateway license has expired. The Security Officer will be able to apply a new Service pack/Upgrade patch after applying for a valid gateway license. |
| 25441 |
If the HySecure gateway cluster is hosted on Hyper-V, both Active and Standby nodes may assume the role of active HySecure gateway. |
| 25425 |
OTP and credentials fields will be briefly visible on the HyLite portal login page. |
| 25277 |
Application launching in a new window via the HyLite portal will not launch in full-screen resolution. |
| 25276 |
VNC access to Mac-based desktops will not work if color depth is set to 8. |
| 25153 |
In this release, if username/password contains special characters “() []; ‘% \” then authentication will fail. |
| 25027 |
In this release, NTP details configured from the HySecure management console will not be synchronized among nodes. The Security Officer must configure NTP for all nodes. |
| 25025 |
Since this release, support for registering users on the License server through the HySecure management console has been removed. |
| 24024 |
In this release, if the administrator sets a native authorization server and enables additional authentication during user login, the user login will fail because of authentication failure. |
| 23785 |
If all device parameters are selected, even if a user logs in from the same browser, a new device ID will be generated every time. |
| 23740 |
The HyLite portal will not be supported on Internet Explorer in this release. Any other browsers can be used for login and application access through the HyLite portal. |
| 23228 |
HySecure gateway stores database backup files in the Standby node; if a cluster does not have a Standby node, the Database will not be backed up. |
| 23202 |
If the user has an existing turbo interface on the gateway, then after upgrading, the ‘Enable ACL Log’ checkbox setting of the turbo interface gets unchecked. By default, this setting remains checked when creating the interface. |
| 23188 |
When a turbo user logs in and, for any reason, the turbo tunnel breaks from the gateway or user side, then turbo applications will not be accessible. |
| 23186 |
If a turbo interface name has special characters “&, %,” and “–“ then the turbo interface may not come up. |
| 23113 |
When a turbo user accesses a turbo application, no corresponding activity log will be stored; hence, the user cannot track turbo application access activity records. |
| 23073 |
The admin can modify the data transfer setting for Turbo users in the global configuration, which affects the "Idle since time" in Turbo Active users. After making changes, the administrator or security officer must manually restart the access control-based service. |
| 23069 |
Users with turbo application access remain logged in as long as their machine is active and connected to the gateway. A handshake between the gateway and client machine keeps the user active, preventing idle timeout. |
| 23068 |
In this service pack, the admin may observe that the upgrade successful message is not displayed while applying the service pack, but the same can be verified from the backend. |
| 22981 |
If MySQL service is down or unreachable, the HA failover feature will not work in this release. |
| 22823 |
Any custom configuration for LoggerDB pruning done from the backend will not synchronize among nodes and needs to be done manually on both Active and Standby nodes. |
| 22486 |
Configuration related to LoggerDB pruning will reset to default if user backup is applied. |
| 20997 |
No Admin log will be generated for database backup generation-related events. |
| 20550 |
Turbo tunnel-based apps are not supported with a server address as the hostname. The administrator can create the same IP address as the server address. |
| 20047 |
Users with ADFS-initiated/SAML Identity provider-initiated logins will not have Turbo IP address pool support. |
| 20031 |
A blank page with an error appears after clicking the Return to App button on the Edit Web VPN Location Block page. |
| 19822 |
As there is no timeout for connection with the site, sometimes the management cluster waits for a long time. The connection is not established, causing other activities to fail. In this situation, the multi-site may stop working. |
| 19802 |
Even after the reporting database is purged, some storage is reserved by the reporting database file. |
| 18614 |
User login fails if the AD user is in over 1000 user groups. |
| 10196 |
The Accops HyLite printer cannot print large files; a HyPrint PDF printer is recommended for large files. |
| 30683 |
To ensure successful user login, administrators in setups upgraded from HySecure 5.4 SP4 LR3 are required to test the connection and submit using the previously configured Azure AD as the SAML IDP. |