Table of Contents

Version 2.8.14 (V2.8.14.74)

Release

2021-12-15

New Features and Improvements

1. Supports a new device.

2. Face 1:N security level setting support for CoreStation.

3. Applied OpenJDK.

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.

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.

9. Improved security vulnerabilities.

10. Updated APIs in Swagger.

11. Improved event log processing performance.

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.

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.

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

23. Improved to be able to run Swagger documents locally without a server address.

24. Changed the default value of Held Open.

25. Changed the device icon of OM-120.


Bug Fixes

1. Even though the screen saver function is supported, the function was not displayed on the Settings of the X-Station 2 fingerprint model (XS2-ODPB, XS2-OAPB) (Affects version: v2.8.12)

2. 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).

3. 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).

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

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

6. 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).

7. Fake Detection was set to ‘Normal’ instead of the default value (Secure) when resetting after disabling Fusion Matching Mode on FaceStation F2 (Affects version: v2.6.0).

8. 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).

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

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

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

12. The server crashed intermittently.

13. Even after deletion, devices previously used for credential enrollment continued to display in the credential enroll device list (Affects version: v2.0).

14. When BioStar 2 was newly installed and then launched, the migration screen was executed instead of the login screen (Affects version: v2.4.0).

15. 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).

16. When entering an email subject in a language with Unicode applied in the email settings, the text of the email subject was sent in a garbled state depending on the set SMTP server. (Affects version: v2.0)

17. When restoring a backed-up log table, if the log table index and the current log table were different and could not be matched, the table creation failed (Affects version: v2.7.11).

18. 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).

19. If there is a language not supported by BioStar 2 in the local storage language of the browser, it was not possible to enter the BioStar 2 login page (Affects version: v2.0).

20. When creating a user group, an error code occurred on the browser and the user group was not created (Affects version: v2.7.14).

21. 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).

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

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

24. 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).

25. When adding events by selecting 'Input (Event Name Change)' in the device's Trigger & Action settings, the 'Add Event Name' button was cut off if there were many registered events (Affects version: v2.0).

26. 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).

27. 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).

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

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