Differences

This shows you the differences between two versions of the page.

--- en:how_to_configure_one_device_legacy_mode [2018/04/03 09:26]
jypark created [How to configure One Device(Legacy) Mode]
+++ en:how_to_configure_one_device_legacy_mode [2021/12/17 10:29]
peterk
@@ Line 1: / Line 1: @@
-===== How to configure One Device(Legacy) Mode =====
+===== How to configure Secure Tamper =====
 ----
-In BioStar 2.5.0 or below, the wiegand input signal can be processed after you add the 3rd-party device as wiegand device. This means that you cannot regard the 3rd-party device as one device with Suprema reader. For example, if you should use the special card which is not supported in Suprema reader with the authentication mode “Card + Fingerprint”, you may connect 3rd-party reader with Suprema reader via Wiegand. At this point, many customers would like to deal with the card authentication event as if it is generated in one device. \\
+When **Tamper On** option is ON: If the device is separated from the bracket (**Tamper On** event happens), the information on all users, logs, encryption key, and SSL certificates configured in the device will be deleted promptly. \\ \\
-From BioStar 2.6.0, we will introduce new feature **“One device Mode”**. In this feature, if the wiegand input is configured in device setting and then wiegand signal is generated without adding 3rd-party reader as wiegand reader to master device, the wiegand signal will be received in master device (Suprema reader). \\ \\
-{{:en:biostar2_one_device_mode_1.png?nolink&1200|}} \\ \\
+Supported device: \\
+<callout type="primary" icon="true">
+BioStation 2 V1.6.0 or above
+BioStation A2 V1.5.0 or above
+BioStation L2 V1.4.0 or above
+CoreStation V1.1.0 or above
+BioEntry P2 V1.1.0 or above
+BioLite N2 V1.0.0 or above
+BioEntry W2 V1.2.0 or above
+BioEntry R2 V1.0.0 or above
+XPass D2 V1.0.0 or above
+FaceStation 2 V1.1.0 or above
+FaceStation F2 V1.0.0 or above
+FaceLite V1.0.0 or above
+X-Station 2 V1.0.0 or above
+</callout>
+{{:en:biostar2_secure_tamper_6.png?nolink&500|}}
+\\ \\
-==== How to configure? ====
+<callout type="tip" icon="true">
+  * Once the **Tamper On** event is generated, the users saved in BioStar 2 can no longer be synchronized with the device. In this case, you should transfer users to the device manually.
+  * Slave device is not supported.
+</callout> \\ \\
-You can configure One Device Mode without any additional task. You should just connect 3rd-party device with Suprema reader using wiegand cable. \\ \\
+==== How to configure ====
-. Connect 3rd-party device with Suprema reader using wiegand cable. At this point, the wiegand input port should be connected in Suprema reader. \\
+There are two cases to configure. \\ \\
-. Set connection mode to either **Master** or **Default**. \\
+=== Case 1: ===
+If you set **Secure communication with device** to **Not Use** in **Setting** > **SERVER**, you should follow the below instructions to configure secure tamper. \\
-<callout type="info" icon="true">
+{{:en:biostar2_secure_tamper_1.png?nolink&600|}} \\ \\
-One Device(Legacy) Mode supports all types of device if wiegand input setting is configured.
-The **SLAVE** device does not support One Device Mode. Only Master or Default(Standalone) can be supported.
-</callout> \\
-. Change **Format Type** into **Wiegand** and select the suitable wiegand format. In addition, select **Wiegand Card Format**. \\
+. Go to Device **Setting** > **Advanced**. \\
+. Change **Secure Tamper** into **On**. \\
-{{:en:biostar2_one_device_mode_2.png?nolink&1000|}} \\ \\
+{{:en:biostar2_secure_tamper_2.png?nolink&1000|}} \\ \\
-. In the Advanced Setting, configure **Wiegand Input/Output** into **Input** and then select the suitable **In/Out Format**. \\
+. When the Tamper On event happens, you can see the below message in BioStar 2. \\
-{{:en:biostar2_one_device_mode_3.png?nolink&1000|}} \\ \\
+{{:en:biostar2_secure_tamper_3.png?nolink&500|}} \\ \\
+Then, you can see the below event logs in the Monitoring section. Especially, if you check the users and logs on the device directly, they would be deleted completely. \\
+{{:en:biostar2_secure_tamper_4.png?nolink&1200|}} \\ \\ \\
+=== Case 2: ===
+If you set **Secure communication with device** to **Use** in **Setting** > **SERVER**, you can see additional options below. Please see **Server & device encryption key manual management**. \\
+{{:en:biostar2_secure_tamper_5.png?nolink&1200|}} \\ \\
+If you change **Server & device encryption key manual management** into **Use**, you can see below warning message.
+\\
+Please note that, if you configure this setting, the function **Secure Tamper** will be applied automatically. Before you apply this setting, please be careful.
+{{:en:biostar2_secure_tamper_7.png?nolink&600|}} \\ \\
-. We will test “Card + Fingerprint” authentication with these setting. \\
--1. In Suprema reader, we configure Auth Mode to “Card + Fingerprint”. \\
-{{:en:biostar2_one_device_mode_4.png?nolink&1000|}} \\ \\
--2. Once you succeed in card authentication on 3rd-party device, wiegand input signal will sent to Suprema reader. After that, Suprema reader requests you to scan fingerprint on it. If you succeeded in scanning fingerprint on Suprema reader, below event will happen as if “Card + Fingerprint” authentication is generated in one device. \\
-{{:en:biostar2_one_device_mode_5.png?nolink&1200|}} \\ \\ \\
-=== Supported Device & Firmware version: ===
-{{:en:biostar2_one_device_mode_6.png?nolink&500|}} \\ \\