Difference between revisions of "uaCap:Transport https soap"

From UaCapabilities
Jump to: navigation, search
Line 1: Line 1:
 
{{CapabilityUri|/Transport/HTTPS/Soap_Xml}}
 
{{CapabilityUri|/Transport/HTTPS/Soap_Xml}}
 
'''Description'''
 
'''Description'''
<br>A web service based protocol that uses HTTPS Transport with Soap/Xml Encoding.
+
<br>This transport mapping implements the OPC UA Services using a SOAP request-response message pattern over an HTTPS connection. 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'''
 
'''Usage Considerations'''
* Requires more resources with more overhead than UA_TCP
+
* Requires significantly more resources with more overhead than UA_TCP
 
* Firewall friendly: uses standard https ports.
 
* Firewall friendly: uses standard https ports.
 
* XML Web Service compatible
 
* XML Web Service compatible
* Can use a browser as a Client
+
* Can use a browser as a Client.
  
 
{{uaConformance|
 
{{uaConformance|

Revision as of 13:44, 5 February 2015

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

Description
This transport mapping implements the OPC UA Services using a SOAP request-response message pattern over an HTTPS connection. 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 significantly more resources with more overhead than UA_TCP
  • Firewall friendly: uses standard https ports.
  • XML Web Service compatible
  • Can use a browser as a Client.

Conformance Testing

Client Server

identical to Client