Difference between revisions of "uaCap:Transport https binary"

From UaCapabilities
Jump to: navigation, search
 
Line 12: Line 12:
 
* [http://opcfoundation.org/UA-Profile/TransportSecurity/TLS-1-2 '''One or more Transport Security Profiles''']
 
* [http://opcfoundation.org/UA-Profile/TransportSecurity/TLS-1-2 '''One or more Transport Security Profiles''']
 
|
 
|
* [http://opcfoundation.org/UA-Profile/Transport/https-uabinary  '''HTTPS Transport with UA Binary''']
+
identical to Client
* [http://opcfoundation.org/UA-Profile/TransportSecurity/TLS-1-2 '''One or more Transport Security Profiles''']
+
 
}}
 
}}

Latest revision as of 13:40, 5 February 2015

URN:          https://opcfoundation.org/wiki/index.php/Transport/HTTPS/UA_Binary

Description
This transport mapping uses the HTTPS transport for the exchange of binary OPC UA messages. HTTPS is a protocol that provides transport security. This means all bytes are secured as they are sent without considering the message boundaries. Transport security can only work for point to point communication and does not allow untrusted intermediaries or proxy servers to handle traffic. In scenarios where an intermediary is needed, the HTTPS transport cannot ensure security and the applications will have to establish a secure tunnel like a VPN before attempting any OPC UA related communication.

Usage Considerations

  • Requires more resources with more overhead than UA_TCP
  • Firewall friendly: uses standard https ports.
  • Can use a browser as a Client.

Conformance Testing

Client Server

identical to Client