Skip to content

Bug Fixes (AHS-HF-5427-GU0005)

  1. All Realms were visible if user access HyLite Portal without URI (Multitenancy Environment) - In previous build, if multitenancy environment is set up and user access HySecure gateway through IP address or hostname instead of URI then user was able to see all the configured realms. In this build, we have fixed this issue, now user won’t be able to see the list of realms and will be provided error message as “Please enter correct URL provided by your organization”. To ensure that user is not able to see any realms, administrator need to enable below configurations in Settings > Global > Server. • Enable automatic realm detection • Don’t allow login if realm detection fails

  2. In earlier build, there was no minimum length for database admin’s password while changing it from management console or OS console. Now, database admin’s password must be at least 16 characters while changing from management console/OS console.

  3. LINUXPROID agent which will work with Desktop Agents and Desktop agent type HyID policy.

  4. Hosted application is visible with multiple app icons in HyLite Portal.

  5. Special character support in SMTP server and SMS gateway password field.

    Character Name Character Name Character Name
    ! Exclamation , Comma [ Left bracket
    ” Double quote - Minus \
    # Number sign (hash) . Full stop ] Right bracket
    $ Dollar sign / Slash ^ Caret
    % Percent : Colon _ Underscore
    & Ampersand ; Semicolon ` Grave accent (backtick)
    ’ Single quote < Less than { Left brace
    ( Left parenthesis = Equalsign " "
    ) Right parenthesis > Greater than } Right brace
    * Asterisk ? Question mark ~ Tilde
    + Plus @ At sign

  6. On some setups which were upgraded from HySecure gateway V5230 to HySecure gateway V5427 using upgrade patch, device profile was appearing with blank name while creating endpoint security access control.

  7. Unable to modify IP Address in case of Network type application.

  8. Login failure in application using Accops Directory Server as authentication method.

  9. HyLite plugin for device ID/EPS was not working. So, if administrator had configured HyLite plugin for device ID/EPS then user from Chromium based browsers i.e., Google chrome and new Microsoft Edge were not able to login.

  10. In earlier build, users were not able to access HyLabs based desktops.

  11. If device was getting approved by external API, then username column used to have log detail instead of username for that log entry.

  12. If authentication had authorization server different than authorization server then user was not being asked OTP even if HyID policy was present for the user.

  13. Users were getting error “Server refused connection” while accessing application which was published with hyphen in hostname.

  14. Unable to rename Anonymous authentication domain name.

  15. Registered users search with authentication server was not working.

  16. Removed non-working entities in Multi Site Sync.

  17. Internal Server Error while configuring Site preferences in Multi Site sync.

  18. Removed traffic routing option “block the traffic”. For a turbo tunnel type application, traffic routing was set to “block the traffic” by default which resulted into application not being accessible.

  19. Incorrect active session time and total session time were reported for some users in user report.

  20. On some specific setups, duplicate user profile were created because of ‘None’ value in authorization server.

  21. Enter button not working while submitting OTP in HyLite portal for login.