...
A standard TLS (version 1.3 in D2000 version 25) is used. Clients verify the validity of the D2000 Server's certificate. It is necessary to regenerate and redistribute the server certificate before it expires. More information on configuration and certificate generation can be read in the documentation.
Please describe
...
which OS accounts and elevated privileges are used for the D2000 system
Scenario 1 - D2000 on Linux
On Linux, the D2000 runs under a user specified during installation. The default user is D2000. The D2000 application is started as a service using systemd. Most of the D2000 processes run with basic privileges; there are several exceptions, which are described in the documentation:
- D2000 Server process requires special capabilities to create multicast sockets:
setcap cap_net_raw=pe kernel - D2000 Kom process may require special capabilities to work with raw sockets, to bind to privileged ports, and to work with GPIO and serial ports (usage depends on used protocols):
setcap cap_dac_override,cap_sys_rawio,cap_net_bind_service+ep kom - D2000 Wssc process requires access to privileged port (port<1024):
setcap cap_net_bind_service+ep wssc
Scenario 2 - D2000 on Windows
...
- D2000 Event Handler: If the Sysprof module is deployed, to access other computers with D2000 (to monitor disk/CPU usage, free memory, etc). Also, if the process accesses remote file shares (e.g., to read/create TXT, XML, or CSV files), a dedicated user is needed, as network services are not available under a LOCAL SYSTEM user.
- D2000 Kom: If the OPC DA protocol is or OPC HDA protocols are used to connect to the remote OPC DA/HDA server, the same user with an identical password has to be configured on both computers.
- D2000 DbManager: If Kerberos authentication is used for some ODBC connections, this process may have to be run under a specific user.
In the configuration of individual processes, when Autostart is enabled, a specific Windows user can be configured (together with the password). In this case, the D2000 Server process creates a Windows service under this user and starts the service. The specified user has to have a "Log on as a service" right, so that a service can be started impersonating the specified user.