4 replies to this topic

[SearchingforAnswers]

Hello. The group I'm working for is trying to establish a way for different users to access and experiment with our OPC server. The server itself is a Rockwell Automation RSLinx Classic OEM, and we're trying to figure out how to restrict the access users can have with it. We'd like them to be able to read and write to the server, but not anything else.

I'm new to labVIEW, so I was wondering if there might be anything available here to limit access to the OPC server?

Thanks.

[asbo]

Is your traffic brokered through LabVIEW? I'm not sure I see how this relates to LabVIEW. I would expect this would be a configuration option of the RSLinx software.

[SearchingforAnswers]

We're looking into our traffic being brokered through labVIEW, to see if it could limit anything. My Supervisor believes that labVIEW has security protocols in place that might limit the amount of interaction with the OPC server.

I suppose another question along these lines is can LabVIEW access any part of the OPC server other than to write and read, and how?

[Tim_S]

Check RSLinx capability to restrict access. LabVIEW is out of the picture once it transfers information to the OPC server.

[JamesMc86]

It depends on how you are accessing it. If you are using OPC clients as part of the DSC modules you can add some security to the shared variables, see http://www.ni.com/white-paper/3322/en for some introductory details.

However this would not stop someone getting some other OPC client and still altering the server.