Pilz PITreader - Page 17

Function description
Operating Manual PITreader, PITreader Firmware V1.5.x
1004806-EN-08
| 17
External authentication (REST API)
REST (HTTPS)
Permission
Modbus/TCP
PITreader
REST API Client
(e.g. HMI)
PLC
Security ID and
permission
PIT m4SEU
Permission
Security ID
Fig.: External authentication (REST API)
The permission for the user can be identified using a permission database on the REST
API Client (e.g. HMI) and the data from the transponder key (e.g. security ID).
Authentication occurs on the RESTAPI Client. The information about the authentication
status is adopted by the PITreader and forwarded to the controller and the safe evaluation
unit (e.g. PITm4SEU). The externally calculated authentication status is displayed via the
device LED on the PITreader.
External authentication (OPC UA)
OPC UA DA
Permission
Modbus/TCP
PITreader
Display unit
with OPC UA
Client
(e.g. display unit from
Pilz with PASvisu
Client and PASvisu
project)
PLC
Security ID and
permission
PIT m4SEU
Permission
Security ID
Fig.: External authentication (OPC UA)
The permission for the user can be identified using a permission database on the OPC UA
Client (e.g. display unit) and the data from the transponder key (e.g. security ID).
Authentication occurs on the OPCUA Client. The information about the authentication
status is adopted by the PITreader and forwarded to the controller and the safe evaluation
unit (e.g. PITm4SEU). The externally calculated authentication status is displayed via the
device LED on the PITreader.