Syteca 7.14

Syteca 7.14 introduced Workforce Password Management (WPM) — private vaults for end users — and added security controls for SSO auto-create behavior.

​

7.14.30 (Build 7.14.54)

​

Issues fixed

• Windows Clients — only the initial screenshot of the Additional Message window was recorded when the Displaying of an Additional Message on Login was enabled (although all metadata for the whole session was recorded), in certain cases when using a Windows 11 Client computer with Windows 365.
• Windows Clients — same issue as above, in certain cases when using a Windows 11 Client virtual machine after a clean installation of version 7.14 of Syteca.
• Database Management — Archiving & Cleanup could not be started in certain cases when the settings were inherited from a Client group after updating to 7.14, with the error displayed on the Health Monitoring page: “The incoming request has too many parameters. The Server support a maximum of 2100 parameters…”.
• Database Management — Archiving & Cleanup could not be started (either when scheduled or manually) in certain cases when attempting to delete large amounts of sessions after updating to 7.14.10.

​

7.14.20 (Build 7.14.48)

​

New features

• Reports — 5 new “(Grouped)” report types. Available for both the Report Generator and Scheduled Reports. They contain the same data as other report types of the same name, but have all the data grouped into a single grid instead of separate groups, for convenience when exported to MS Excel (XLSX, XLS) formats:
  • Activity Summary Grid Report (Grouped)
  • Clipboard Grid Report (Grouped)
  • Detailed Activity Grid Report (Grouped)
  • Session Grid Report (Grouped)
  • URL Summary Grid Report (Grouped)

​

7.14.10 (Build 7.14.46)

​

Improvements

• SSO authentication — Auto-create control. Adding new users automatically when they attempt to log in for the first time using SSO authentication can now be disabled by deselecting the new Auto-create a Management Tool account for a new user on the first SSO login checkbox. New users are then not able to log in to the Management Tool until an administrator adds them on the User Management page in the usual manner. Furthermore, if this checkbox is selected, new Active Directory users are now automatically added as Active Directory users (instead of as internal users), and are therefore able to log in in the usual manner.
• Database structure optimized. Data migration begins after the Application Server starts up. See Update best practice.

​

Issues fixed

• Application Server — the Syteca Application Server could not be started properly (where the Application Server logs indicated that it was stuck in “Constructed server managed part”, although the EkranServer service was running) in certain cases involving updating, migrating to a different computer, and re-installing the Application Server.
• System updates — the EkranServer service started to consume a significant amount of RAM in certain cases several hours after updating.
• Alert events — the Alerts tab (on the Monitoring Results page) was not loading the data in certain cases when using the PostgreSQL database.

​

7.14 (Build 7.14.36)

​

New features

• Workforce Password Management (WPM) — introduced. The new Workforce Password Management functionality is now available, to enable all PAM users (users of the Syteca Connection Manager) to create their own private WPM secrets, hidden from other users unless specifically shared with them:
  • A new administrative PAM User Access permission has been added to enable PAM users who do not have the Management Tool Access permission to be granted limited access (to the Password Management page only).
  • PAM users can now click the new Add Secret button in the Syteca Connection Manager to log in to the Management Tool and create their own WPM secrets in their new WPM folder.
  • After logging in, they can add (and manage) their own WPM secrets in their new WPM folder called “My Secrets (<username>)”.
  See Workforce Password Management.

​

Improvements

• Client Management — AD group exclusion for Secondary Authentication. Active Directory user groups can now be specified to exclude all the users in these groups from needing to log in using Secondary User Authentication on a Windows Client computer (or Client group). Allows administrators to save time instead of entering multiple usernames to exclude each user in each Active Directory group individually.

​

Issues fixed

• Syteca logs — the Application Server and Management Tool log files could not be downloaded in certain cases (e.g. when the log file was larger than 100 MB).
• Using secrets — an “Extension error” was displayed in Google Chrome when using a Web account secret (despite the secret working correctly).
• Client sessions — after clicking the Play button for a Client on the Client Management page, the Client sessions were not filtered (by the Where filter) for the Client on the Monitoring Results page that opens.
• Scheduled Archiving & Cleanup — Cleanup operations ran despite the Auto-Cleanup Options being set to Never in certain complex cases involving inheriting settings from multiple Client groups.
• Scheduled Archiving & Cleanup — some sessions were not deleted by scheduled Cleanup operations in certain cases.
• Forensic Export History — did not display any exported sessions after updating to version 7.9 of Syteca.
• Migration Tool — after using the Syteca Migration Tool (to migrate data from the Firebird database to the PostgreSQL database), it was not possible to view the screenshots in the Session Player that were initially recorded to the Client offline cache during migration.
• Additional message on login (Windows) — a blank screen was displayed instead of the pop-up window containing the additional message, when this option was enabled (until the user re-logged in).

​

Related component release

This release also included Master Panel 1.5.5 (Build 1.5.5.2) with improved SSO authentication. See Master Panel changelog. This release also included API Data Connector 1.7 (Build 1.7.164) with updated .NET Runtime compatibility. See Data Connector changelog.

​

Related