Configuration of metaSEC QR/NFC Reader Controller

    General
    The QR/NFC Controller is a system for communication between the respective hardware component and the James middleware. The controller can hold up to four USB reader units.
    When called, the numeric ID of the reader is passed to the middleware.
    Default values
    The controller has the IP 192.168.44.72/24 by default. This should be adjusted according to the local situation.
    The user name is root and the password is metasec.
    Configuration
    The following steps are necessary:

    Folgende Schritte sind zu notwendig:

    1. Login via SSH to the controller with the above data.
    2. The following files must be adapted to the local environment for the network to function correctly
      1. /etc/network/interfaces.d/eth0 for the IP address and possibly necessary default gateway
      2. /etc/resolv.conf für den DNS server (optional. If no DNS server is used, the file can be left empty)
      3. /etc/hostname for the host name of the box. Even if no DNS is used, the host name should be a unique identifier.

    After the adjustments have been made in the network, the system can be rebooted.

    Reader

    The next step can only be carried out if the reader units are connected to the controller.
    With the command you can see all connected readers

    ls -1 /dev/input/event*
    Output:
    /dev/input/event0
/dev/input/event1
    These values will be needed later for the configuration of the middleware. In the above example, two readers have been detected by the controller.

    Middelware
    The file /etc/metasec/qrcode_scanner.ini contains the configuration of the communication interface to the James Middelware
    [default]
james_host=james-srv.kunde.local
hw_device=/dev/input/event0 /dev/input/event1
boxid=AABBCCDD
url_base_target=/portals/wf_middelware_portal.php
url_opt_param=wf_id=17&value_rel_id=1
    The parameters are to be configured as follows:

    1. james_host = DNS name or IP address of the James server
    2. hw_device = readers which are connected to the controller. Important: If a reader is listed incorrectly or is not recognised after a system reboot, the entire process cannot start!
    3. boxid = Optional ID of the controller. Recommendation is to use the MAC address here
    4. url_base_target = Target for the call. This can be left as in the example above
    5. url_opt_param = usually a workflow is processed. The ID of the workflow must be passed as a parameter. In general, any kind of parameter sequence can be appended here.

    After successful processing of the file, you can restart the controller.
    Operation
    Each positive scan on the reader is transmitted to the configured address. You can see the calls in the syslog as well as in the NGINX log of the James web server.
    Published