Selective Exposure of OPC Tags to Third Party Clients
j
jay.lafave
It is possible to define users and roles to restrict access to the OPC UA Server. However, it is not possible to restrict which tags a user has access to once they have been allowed to connect to the OPC Server. It is "all or nothing". Add functionality that gives developers the ability to only expose a specific subset of tags to specific users when that user connects to the OPC Server.
Log In
P
Paul Mangels
This is something that has come up recently again. At a minimum, it would be nice to be able to select which tag providers are exposed over Ignition's OPC UA Server. This way we could put tags that we want to expose to a client in a single tag provider.
Currently, the easiest workaround here involves going outside of the Ignition system and setting up an OPC UA middleware with something like a Kepware OPC server if we want to serve OPC tags to a third-party system, but not give that system write access to every tag on our gateway. It would be nice to be able to do this within Ignition.