Ignition OPC UA Server and Connection To OSI-PI OPC-UA Connector

[Kevin.Herron]

Looks like an issue others have had: PI OPC UA Connector To Ignition OPC UA Server - #2 by Kevin.Herron

I think the punchline is that if you can't get connected with security by pointing OSI PI at the discovery endpoint URL then you need to get OSI PI involved, and potentially get them to fix their client.

Ignition has an admittedly unusual endpoint setup re: security. This will be changing in 8.3 due to the trouble it seems to cause for some 3rd party clients.

@Kevin.Herron

There is a discovery endpoint at opc.tcp://host:62541/discovery. It accepts unsecured connections and implements the discovery services. The endpoints it returns contain URLs that point to the session endpoint at opc.tcp://host:62541 (no /discovery).

If your client / client library can't correctly use the endpoint URLs returned in the GetEndpoints response then it won't be able to connect.

I've found that on order to connect broken clients like this to Ignition you have to enable the "None" security policy in the server and then point the client directly at the session endpoint instead.