Dear Valued Partners,

BioStar 2.8.14 is now available from our website. (Download)

Please check the below and keep using the latest version of BioStar 2.

BioStar 2.8.14 includes key features that many customers have been waiting for.

BioStar 2.8.14 Major New Features
- Support new device: IM-120
- Support OpenJDK (version: OpenJDK 15)
- BioStar 2 server performance improvements
- Imporved security vulnerabilities
- Improved for Log4j 2 vulnerability issue (applied: v2.16.0)

New Features & Improvements

1. Supports a new device. (Relevant Article - [BioStar 2] New Product Launch: IM-120 (Multiple Input Extension Module))

  • Input Module (IM-120)

2. Face 1:N Security Level setting support for CoreStation.

3. Applied OpenJDK.

* As of BioStar 2 version 2.8.14, OpenJDK is applied to allow users to use BioStar 2 regardless of the Java version installed on the PC.

4. Added Department, Title, and Telephone to User Column Settings.

5. Improved to be able to enter and modify PIN when using user CSV import. (Relevant Article - [BioStar 2] Enter and Modify PIN When Using User CSV Import)

6. Improved performance by no longer inquiring unnecessary user information when calling API.

7. Improved device search speed using API.

8. Improved Automatic User Synchronization performance.

  • Added missing indexes to database columns used for synchronization.
  • Improved ‘All Devices’ Automatic User Synchronization speed and fixed synchronization errors.
  • Improved ‘Specific Devices’ Automatic User Synchronization speed.
  • Improved to send changes in bulk when using ‘Specific Devices’ Automatic User Synchronization.
  • Added exception handling for null value when retrying after 'Specific Devices' Automatic User Synchronization failed.

9. Improved security vulnerabilities.

  • Applied Log4j 2 v2.16.0.
  • Applied OpenSSL 1.1.1k.
  • Applied jQuery 3.4.1.
  • Improved to check Operator Level and Custom Account Level when using API.
  • Fixed an issue where if the CSV export file contains a formula symbol (=), the formula is applied when the file is executed.
  • Improved to perform CORS check and security check for session ID when connecting to web socket.
  • Prevention for SQL Injection attack.
  • Improved to display error messages (error name, http error code, description) when a server status response error occurs.

10. Updated APIs in Swagger.

  • Updated the description of device Trigger and Action API
  • Added Visual Face Image Upload API. (Relevant Article - [BioStar 2 API] How to Add Visual Face via BioStar 2 New Local API)
  • Fixed an issue where users were not added to the actual device differently from the result returned when adding users to devices using [POST] /devices/{id} /users or [POST] /api/users/export.

11. Improved event log processing performance.

  • Improved event log inquiry speed in MS SQL Server database environment.
  • Improved database processing speed when generating device event logs.
  • Fixed to update only devices with changes in the database when synchronizing device log data.

12. Improved the loading speed of the device menu when restarting the BioStar 2 server with multiple devices connected.

13. Improved device connection speed.

14. Improved performance dealing devices by increasing the default number of device threads.

15. Improved loading speed of the monitoring menu by deleting unnecessary check logic.

16. Improved access group link speed by deleting unnecessary codes.

17. Improved blacklist card synchronization speed.

18. Improved database data processing speed.

19. Improved server performance.

  • Improved to maintain the existing connection without reallocating the client port every time when communicating between the C server and the Java server.
  • Improved to prevent unnecessary function calls according to log level in C server.
  • Improved to reuse objects for encrypt personal data in Java server instead of reallocating them every time.

20. Improved the speed of querying registerable devices using API.

21. 26 bit Wiegand card support for BioStar 1.x to BioStar 2.x Migration Tool. (Relevant Article - [Both BioStars]An Example of DB Migration Steps) 

22. Improved to check the database connection status before proceeding with the BioStar 2 installation.

  • Removed 'Check the database connection' option from the custom installation process.

23. Improved to be able to run Swagger documents locally without a server address. (Relevant Article - [BioStar 2] How to Use Local Swagger (New Local API))

24. Changed the default value of Held Open.

  • Before: 3 seconds
  • After: 10 seconds

25. Changed the device icon of OM-120.

Bug Fixes 

* Major bug fixes are mentioned below. Please check the attached revision note to find the left items. 

1. When using the 'Specific Devices' Automatic User Synchronization option, it did not sync if the user ID contains some symbols (_) (Affects version: v2.7.11).

2. When using the 'Specific Devices' Automatic User Synchronization option, the synchronization logic operated as 'All Devices' when executing Write Smart Card (Affects version: v2.7.11).

3. Chrome autocomplete function was mapped incorrectly in the information input field on the Add User screen (Affects version: v2.7.8).

4. some languages were displayed as question marks in Audit Trail when using MS SQL Server database (Affects version: v2.7.0).

5. When using the Visual Face as a user profile image, it exceeded the allowed size of the profile image and did not sync to devices (Affects version: v2.8.6).

6. When setting the logo image as the home screen for FaceStation F2, the image was not applied in the correct resolution for the device (Affects version: v2.8.6).

7. It was not possible to enter uppercase letters in the server address when using 'Device → Server Connection' (Affects version: v2.7.0).

8. Custom user field data was not reflected in the T&A report (Affects version: v2.8.3).

9. Fixed an issue where key values were exposed when fetching smart card layouts using API. (Affects version: v2.0)

10. The server crashed intermittently.

  • C server crash occurred when database inquiry failed while creating user group cache (Affects version: v2.0).
  • Lock handling was missing in serviceTask JsonResult (Affects version: v2.0).

11. When running ‘Manage Users in Device’ by selecting a device that supports only cards, the status of the user with the enrolled fingerprint was displayed as ‘Different’ (Affects version: v2.0).

12. When generating more than 10 events by selecting ‘Input (Event Name Change)’ in the Trigger & Action settings of CoreStation, it did not work properly. (Affects version: v2.8.8)

13. When using server matching with FaceStation 2's authentication mode set to Card+Face, the face authentication mode did not work after card authentication (Affects version: v2.8.6).

* This modification will be applied to devices with firmware version 1.5.1 or later installed.

14. During ‘All Devices’ Automatic User Synchronization, the access group and door synchronization results were not updated intermittently (Affects version: v2.0).

15. Devices were disconnected when the amount of data was large during Automatic User Synchronization (Affects version: v2.0).

16. When adding a user using API, it was possible to create a user ID with a value not supported by BioStar 2 (Affects version: v2.8.1).

17. When importing users with CSV import, ‘Upload successful’ message was displayed even if there was information that was not updated (Affects version: v2.3.0).

18. When a device that does not support the intelligent slave sent OSDP ID as an invalid value, BioStar 2 initialized the value to 0, updating RS-485 settings and disconnecting the existing RS-485 connection (Affects version: v2.8.10).

19. Even though the server matching is supported, the function was not displayed on the settings of BioStation 2 (Affects version: v2.2.2).

20. When a user has abnormal profile image, the user sync process was not finished properly (Affects version: v2.8.0).