Hello,

Thank you for reporting this error. We can reproduce this also ourselves.

The error happens because the server sends different EndpointDescriptions in GetEndpointsResponse and CreateSessionResponse.

In GetEndpoints, the returned EndpointDescriptions contain TransportProfileUri=http://opcfoundation.org/UA-Profile/Transport/uatcp-uasc-uabinary. In CreateSessionResponse, the corresponding TransportProfileUri is empty.

In principle, the server application is not working according to specification. The part 4 of the OPC UA specification states that “The Server shall return a set of EndpointDescriptions available for the serverUri specified in the request. … The Client shall verify this list with the list from a DiscoveryEndpoint if it used a DiscoveryEndpoint to fetch the EndpointDescriptions. It is recommended that Servers only include the server.applicationUri, endpointUrl, securityMode, securityPolicyUri, userIdentityTokens, transportProfileUri and securityLevel with all other parameters set to null. Only the recommended parameters shall be verified by the client.”

This being said, the Prosys OPC UA Client could handle this error situation more robustly. For example, the client application should show an indication of the error and give an option to acknowledge the error and continue. We’ll improve this feature of the Client application in the future.

Unfortunately, there’s no workaround available for now. The Prosys OPC UA Client cannot connect to this server until the server is changed so that it returns the same EndpointDescriptions in GetEndpoints and CreateSession.

If you would be using the Prosys OPC UA Java SDK directly, you could bypass this validation check with method

However, as said this is not possible at the moment with the graphical Prosys OPC UA Client application.

Please let us know if there’s any additional questions or comments about this matter.