Lynx 1.7.2 Release Notes
  • 24 Sep 2024
  • 6 Minutes to read
  • Contributors
  • Dark
    Light
  • PDF

Lynx 1.7.2 Release Notes

  • Dark
    Light
  • PDF

Article summary

Prerequisites

Before installing Lynx 1.7.2, please ensure that the target system(s) meet the following requirements:

  • Windows Server 2012 R2, Windows Server 2016, Windows Server 2019 or Windows Server 2022 (physical or virtual machine).

  • The server on which Lynx 1.7.2 will be installed must be joined to the Active Directory domain that contains the users that will use the solution.

  • Valid SSL certificate - The certificate can be issued by a public certificate authority (for example, Verisign or GoDaddy) or an internal authority (for example, Windows Certificate Services).

  • Microsoft .NET 4.6.1 or greater is installed.

  • License key (available from Identity Automation - please contact your account representative).

  • (OPTIONAL) Microsoft SQL Server 2012, 2014, 2016, 2017, or 2019 (any edition). SQL Server can be installed on the same machine as the Lynx Server software, or on a different machine. Note: For enterprise deployments, Identity Automation recommends the use of a high-availability SQL Server environment. Therefore, for enterprise deployments, you should choose an edition of SQL Server that supports high availability.

  • (OPTIONAL) Will you be using Lynx in conjunction with Identity Automation's ExactAccess (XA) product? If using Lynx with ExactAccess (XA), then Lynx must be installed on the same computer as XA Server. This is because Lynx will use the encryption components that XA Server provides to read and write encrypted data in the database. In addition, you must use a Microsoft SQL Server instance because it is required by the XA Server.

Compatibility with Previous QwickAccess for ThinOS Releases

Product

QwickAccess Package Name

QwickAccess Version

Compatible with Lynx 1.7.2?

QwickAccess for ThinOS 8.5 and 8.6

QwickAccess came embedded in ThinOS 8.5 and 8.6 so there is no separate package

N/A (this version came embedded in ThinOS 8.5 and 8.6)

Yes

QwickAccess for ThinOS 9.0

QwickAccess came embedded in ThinOS 9.0 so there is no separate package

N/A (this version came embedded in ThinOS 9.0)

No

QwickAccess for ThinOS 9.1 MR1

idauto_1.0.1_1_signed.pkg-V1.0.1.1

Version 1.0.1.1

No

QwickAccess for ThinOS 9.1.1 (9.1.4234)

Identity_Automation_QwickAccess_2.0.0.3_3.pkg

Version 2.0.0.3

No

QwickAccess for ThinOS 2208(9.3.2102)

Identity_Automation_QwickAccess_2.0.1.0_3.pkg

Version 2.0.2.1

No

QwickAccess for ThinOS 2211 (9.3.3099)

Identity_Automation_QwickAccess_2.0.3.1.1.pkg

Version 2.0.3.1

No

QwickAccess for ThinOS 2303 (9.4.1141)

Identity_Automation_QwickAccess_2.0.4.1.6.pkg

Version 2.0.4.1.6

Yes

QwickAccess for ThinOS ThinOS 2402 (9.5.1079)

Identity_Automation_QwickAccess_2.1.0.7.pkg

Version 2.1.0

Yes

QwickAccess for ThinOS ThinOS 2411

Identity_Automation_QwickAccess_2.1.1.x.pkg

Version 2.1.1

Yes

Bugs Fixed

Ticket Number

Description

HEALTH-685

PIN is updating on forgot PIN window if user keeps new PIN same as old PIN.

HEALTH-860

User is able to change password through SSPR if old and new passwords are same.

HEALTH-925

Minimum password length functionality was not working as required.

HEALTH-1065

User is able to change password without following password rules when Active Directory's "User must change password at next logon" functionality is checked.

HEALTH-1112

SSPR (Optional/Grace Period) textboxes takes 'zero' as input value.

HEALTH-1183

User is unable to reset password if first character is special character and there is no more special character in the remaining string.

HEALTH-1195

User registered with SSPR cannot change password without complex characters when password complexity is disabled on lynx.

Note: After changing the complexity from AD, we’ve to refresh & save the Global Settings page in Lynx to reflect the changes at Lynx side.

HEALTH-1201

While getting Minimum length of user password, if Domain name is incorrect, the Lynx application was crashing.

HEALTH-1306

Created new AuthServiceResultCode & ProxCardServiceResultCode in Lynx API to handle duplicate password & pin cases.

HEALTH-1133

Fixed SSPR (Optional/Grace Period) textboxes saving with blank value.

HEALTH-1334

Lynx web page crashes if single or multiple spaces are entered in domain name field.

HEALTH-1337

Profile created on old version of Lynx cannot be edited on new version for ThinOS 9.1.1.

HEALTH-1345

Zulu application is unable to move to next state when old and new passwords are same.

New Features and Enhancements


Ticket Number

Description

HEALTH-929

Valid message should prompt on Zulu when license is expired on Lynx server.

Database Update Instructions

Lynx 1.7.2 can be configured to use an embedded database or a Microsoft SQL Server database. If you are using the embedded database, then no further action is required. If you are using a Microsoft SQL Server database, then you must upgrade the database to support Lynx 1.7.2, if you are upgrading Lynx from 1.5.0. Follow these instructions to upgrade your SQL Server database.

  1. After the installation or upgrade to Lynx 1.7.2, open the Windows Services app (services.msc) and find the HealthCast Lynx service in the list.

  2. Stop the HealthCast Lynx service.

  3. Double-click the HealthCast Lynx service to open its property pages.

  4. Click the Log On tab.

  5. Select the This account radio button and enter the credentials for an account that has read and write privileges to the Lynx database on SQL Server.

  6. Click OK.

  7. Next, start SQL Server Management Studio (SSMS)

  8. In SSMS, open the C:\Program Files (x86)\HealthCast\Lynx\CreateDb.sql file.

  9. In the CreateDb.sql file (now opened in SSMS) change the top line from use [YOUR-DATABASE-NAME-HERE] to contain the correct Lynx database name. Typically, this would look like this: use [Lynx] although your database name may be different.

  10. Run the CreateDb.sql file within SSMS.

  11. You will notice several errors that all say that certain objects (tables) are already created. You can safely ignore these errors.

  12. Now start the HealthCast Lynx service which was stopped in Step 2 of these instructions.

  13. The database update is now complete.

Upgrading from Lynx 1.6.x

Lynx 1.7.2 can be upgraded directly from 1.6.x (1.6.0 & 1.6.1) versions without any issue. The upgrade process also do not require any special instruction to update the Lynx database and the data also persists in the existing database.

Steps to upgrade Lynx from 1.6.x:

  • Assuming that we have already Lynx-1.6.x is installed and to upgrade it to Lynx-1.7.2, we have to install the latest Lynx build i.e. Lynx-1.7.2.15 by double clicking on the setup file.

  • It may display a dialog box stating that the reboot is required and we have to click on OK button to move forward, as displayed in the following image.

  • After completing the Lynx-1.7.2 installation we have to restart the HealthCast Lynx service from Services as highlighted in the following image.

  • Then run the Lynx portal in web browser and it displays the current installed version in the top and bottom of the login screen of Lynx.

  • We can also verify the upgraded version from the Control Panel > Program & Features list that the current installed version is changed to 1.7.2.15.

  • So, in this way we can easily upgrade the Lynx from 1.6.x to 1.7.2 version.

     Known Issues:

      No known issues at this time

Upgrading from Lynx 1.5.3

If Lynx 1.5.2 (and below) or 1.5.3.1 or 1.5.3.2 is currently installed on the system, you won’t be able to perform an upgrade to Lynx 1.7.2 without first uninstalling Lynx 1.5.2 (and below), 1.5.3.1 or 1.5.3.2 and removing files/and folders that are left behind after uninstalling.

Please follow the steps below to upgrade from Lynx 1.5.2 or 1.5.3. 

  1. Uninstall Lynx 1.5.2 or 1.5.3 by using Windows Add/Remove Programs (or similar method).

  2. Next, locate the RemoveServiceAndFolder.ps1 file in the package that contains the Lynx 1.7.2 deliverables.

  3. Run the RemoveServiceAndFolder.ps1 file as an administrator.

  4. Now run the Lynx-1.7.2.15-Setup.exe file to install Lynx 1.7.2.

Settings Not Preserved on Upgrade

After upgrading from the 1.5.0 version of Lynx you will need to re-enter the settings that you had previously. This is because the upgrade to Lynx 1.7.2 will not preserve the previous settings. To reapply your previous settings after an upgrade, open the Lynx Admin web app and click the “Settings” tab on the left. Then go through each of the settings tabs and values to ensure they meet your requirements. Make changes as needed. Note that Lynx 1.7.2 now allows you to create settings profiles. Please see the section “Settings Profiles” at the end of this document for more information.

Global End Point Settings

Following setting is currently not working under Global End Point Settings menu:

  1. Password History Count

Supported Versions of QwickAccess for Dell ThinOS:

  • QwickAccess for Dell ThinOS 2.1.1 and above.


Was this article helpful?