This article explains the step-by-step procedure to connect old FW2 and ECS10/BCS10 to BioManager ENTERPRISE (BME) R20.
TBS strongly recommends the upgrade to FW3 and EC20/BCS20 wherever possible. The below steps are meant to be used only in case upgrade is not possible due to technical limitations wrt integration or unavailability of FW3 for certain old platforms.
Remote Enrollment and device configuration from BioManager (/external ACS) is not working between FW2 and BME, due to breaking changes in server DCC channel. This is a known limitation in this constellation.
Terminal FW2
Step 1 - Server Communication Settings:
The BME R20 is hosted in IIS under a dedicated website and custom port (by default 8808) during installation. Also the Client Authentication is enforced in BME, and the key is listed in BioManager application as 'Legacy Key (Firmware v2)' under SYSTEM/Settings page.
Configure the Server Communication settings as shown below either using DeviceConfig or admin interface on terminal.
If the BME is configured with either Public or TBS-signed SSL certificate, then the Endpoint URL should already be reachable. In that case, the remaining steps should be ignored and proceed directly with validation in BioManager Clients page.
Step 2 - Custom Certificate License:
If the SSL certificate used in BME is either auto-generated by installer or a custom certificate, then the terminal requires 'Custom Certificate (non-public)' License. Use the License Manager tool to generate the required licenses. Apply the license using DeviceConfig under Maintenance/Licensing page. Once done, the page should list 'Custom Certificate (non-public)' under Active Licenses.
If you have a config package to upload the custom root CA, then the license is not required.
Step 3 - Security Settings:
The DeviceConfig provides the option to load the root CA certificate file (containing public key) after Step 2.
- BME 'auto-generated' certificate: file is named as 'TBS-GEN-ROOT-CA.crt' under '{BME installation folder}\Tools\CertInstaller\certs' folder.
- Custom certificate: file should be provided by the certificate owner or handler.
Install the file using the option 'Add Root CA directly (*.crt)' under section 'Trusted Certificate Authorities (CA)' in Maintenance/Security page. In case of config package, the option 'Add Root CA via configuration package (.tbs)' should be used. Once certificate is installed, configure the certificate for 'TBS Server' as shown below.
The Endpoint URL should now be reachable and client should be listed in BioManager for validation.
EC10/BCS10 Configuration
Step 1 - Server Connection Settings:
Open the BCS10 config either by accessing URL http://localhost:8281 or through EC10 and update the BCS10 'Server Connection' settings as shown below.
Step 2 - Security Settings:
If the SSL certificate used in BME is either auto-generated by installer or custom certificate, then install the certificate on local Windows OS certificate store using MMC. Then, configure BCS to use 'Windows certificate store' for 'Server communication certificates' under section 'Trusted Certificate Authorities (CA)' in Security page.
Restart the BCS for the new security settings to take effect.