# User based security for OPC-UA server **URL:** \ **Category:** Ignition\ **Created:** [September 12, 2020, 5:43pm UTC](https://forum.inductiveautomation.com/t/user-based-security-for-opc-ua-server/38621 "2020-09-12T17:43:00Z")\ **Posts on this page:** 1\ **Showing post:** 16
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [November 17, 2020, 3:31pm UTC](https://forum.inductiveautomation.com/t/user-based-security-for-opc-ua-server/38621/16 "2020-11-17T15:31:51Z")
My Modbus Server module is getting close to reality... as noted over here: > [@Connecting to SAP with 3rd party Python lib or SAP JCo jar](http://forum.inductiveautomation.com/t/connecting-to-sap-with-3rd-party-python-lib-or-sap-jco-jar/40712/7): > > I’ve mentioned it a few times around here, but it implements the server (slave) side of the Modbus protocol so that other masters can connect to Ignition. It supports simultaneous Modbus TCP, Modbus Serial RTU, and Modbus RTU over TCP connections to the configured virtual device. Within the virtual device, multiple units are supported, each with their own data format setttings (word swapping, etc) and configurable ranges of bits and registers to expose. It also supports a configurable number… --- _[View the full topic](https://forum.inductiveautomation.com/t/user-based-security-for-opc-ua-server/38621)._