Dear Valued Partners,
BioStar 2.9.0 is now available on our website. [Download]
Please review over and keep using the latest version of BioStar 2.
New Features & Improvements
1. Supports BioStation 3
We would like to welcome you all to check out our latest device New Product Introduction: BioStation 3
2. Supports user information partial update - Supporting device: BioStation 3 v1.0.0 [Relevant Article]
3. Improved extraction of images used for visual face credentials [Relevant Article]
New facial template algorithms applied
4. Simplified visual mobile face enrollment process [Relevant Article]
5. Supports visual face import -Enrolls visual face when the file name of the image matches the user ID [Relevant Article]
6. Supports visual face migration [Relevant Article]
2.9.0 Version extracts visual face template from existing (saved) visual face template to match with new algorithms.
The user can check the facial template usability straight from BioStar 2; no need to check from the device.
7. Device added supporting Fingerprint LFD - Supporting device: BioLite N2 v1.5.0
- BioLite N2 now has a software-based LFD system supporting Fingerprint LFD. [Relevant Article]
8. Improved door open logs [Relevant Article]
- User can see detailed information for “Door Unlocked” events.
- Affected on all firmware, the error code from the device will be sent to BioStar 2 event log, this event log can not be found in device log.
- BioStar 2 Version 2.9.0 now allows the user to know the exact reason for the cause of device synchronization failure.
In previous versions, the alert message for device synchronization was simply stating “Sync Error.”
Now, with BioStar 2 Version 2.9.0, it shows alert messages with clear reasoning for device synchronization failure.
After checking the reason for Sync Error, users will now be able to fix the problem at hand and use BioStar 2 and devices properly.
If you need help with finding out the full capacity of the device you are currently using, please visit SUPREMA Website : [Product] -> [Hardware] section to find out more details about your device in the “Specification” section of each device as shown below.
10. Improved security vulnerabilities
- Improved Unquoted Service Path Vulnerability
- Improved Clickjacking vulnerability
- Improved minor vulnerabilities
The Chrom browser’s security policy has made the CSV import path be stated as a “fake path”,
which has caused confusion for some users questioning if their files have been selected properly or not.
So, we have now edited the error message being shown in the path part of CSV import.
Previous Versions (shown below)
BioStar 2 Version 2.9.0 (shown below)
2.1. QR/Barcode having the same card ID as a CSN or Wiegand card being authenticated while using ‘Server matching’ with X-Station 2 (Affects version: v2.8.11)
2.2. Operators with privilege rights to edit user information couldn’t edit due to not having email setting edit privilege rights (Affects version: v2.8.14)
2.3. Event logs are not being stored in the database, although the logs are shown in the ‘Real-time Monitoring’ menu. (Affects version: v2.8.6)
2.4. Visitor’s fingerprint enrollment failing from the ‘Visitor’ menu (Affects version: v2.8.14)
2.5. BioStar 2 not running properly due to incorrect MSSQL table constraints (Affects version: v2.8.5)
2.6. When issuing mobile access card via CSV import, the phone number, which is supposed to be a non-required field component, changes to the required field (Affects version: v2.7.12)
2.7. Visual face not being synchronized to devices intermittently (Affects version: v2.8.12)
2.8. When ‘Automatic User Synchronization’ is set to all device, and a particular device failed to synchronize, other devices that don’t need synchronization gets user information. (Affects version: v2.8.6)
2.9. User group not related to the action of ‘Batch Edit’ also being synchronized to devices that belongs to other components (Affects version: v2.8.14)
2.10. BioStar 2 abnormally occupying memory when manually locking and releasing a door (Affects version: v2.0.0)
2.11. The visual face enrollment page not showing any strings when the browser language is set to a language that the enrollment page does not support (Affects version: v2.8.5)
2.12. BioStar 2 shows success as a result when uploading a user having a card ID even if the user already exists in BioStar 2 (Affects version: v2.8.9)
2.13. Devices supporting ‘Extended Auth Mode’ intermittently not displaying auth modes correctly (Affects version: v2.8.6)
2.14. BioStar 2 not finding the correct port being used when checking for licenses (Affects version: v2.7.11)
2.15. Unassigned ‘Mobile Access Cards’ being sorted in a descending order in BioStar 2 running with MariaDB (Affects version: v2.8.7)
2.16. Video logs being recorded shorter than the configured settings (Affects version: v2.5.0)
2.17. ‘Mobile Access Card’ issue page not following the ‘Date Format’ settings when its set as mm/dd/yyyy or dd/mm/yyyy (Affects version: v2.8.9)
2.18. User information CSV Export displaying expiry date on ‘Mobile Access Cards’ that does not have any expiry date (Affects version: v2.8.9)
2.19. ‘Enroll’ and ‘Search’ buttons intermittently disappear from the ‘Visitor’ menu when enrolling a visitor (Affects version: v2.8.7)
2.20. Error message indicating the maximum number of face credentials displaying incorrect number value (Affects version: v2.8.6)
2.21. BioStar 2 API Swagger not displaying Unicode characters for response (Affects version: v2.8.14)
2.22. When ‘Mobile Access Cards’ gets imported through CSV, only up to 100 cards are shown, and the rest are deleted, although the CSV contains more than 100 cards information (Affects version: v2.7.12)
2.23. Result of the ‘Muster Status’ on print and CSV having different time zones (Affects version: v2.8.6)
2.24. Wiegand card ID accepts only 32 characters when it should accept up to 78 characters (Affects
2.25. Authentication succeeds even when the authentication failed to pass the global ‘Anti-pass back’ check (Affects version: v2.8.11)
2.26. X-Station 2 firmware files not displaying correctly on the firmware upgrade page (Affects version: v2.8.12)
2.27. Image and video logs are not being displayed when accessing the ‘Monitoring’ menu without accessing the ‘Video’ menu’ first (Affects version: v2.7.0)
2.28. Event logs not displaying when a custom operator sets a filter from the ‘Event Log’ menu as more than 1,000 user groups (Affects version: v2.8.3)
2.29. Video logs are not being displayed when accessing BioStar 2 using a domain URL (Affects version: v2.6.0)
2.30. Card not being able to be re-used as an arm/disarm card or assigned to a user when the card was registered as an arm/disarm card for an ‘Intrusion Alarm Zone’ even when the zone itself gets deleted