Similar to the HTTP transport, the HTTPS transport consists of a receiver implementation which comes from the Carbon core component and a sender implementation which comes from the Tomcat http connector. In fact, this transport uses exactly the same transport sender implementation as the HTTP transport . The transport receiver implementation of the HTTP transport is available in the Carbon core component. The transport sender implementation comes from the Tomcat http connector. This transport is shipped with WSO2 Carbon and all WSO2 Carbon-based products, which use this transport as the default transport, except WSO2 ESB. By default, we use non-blocking Tomcat Java connector,
axis2.xml file contains configurations for HTTP/S transports by default, they are not used by WSO2 products. Instead, the products use the HTTP/S transport configurations in Tomcat-level; therefore, changing the HTTP/S configurations in the
axis2.xml file has no effect.
HTTPS servlet transport should be configured in the
<PRODUCT_HOME>/repository/conf/tomcat/catalina-server.xml file, same as with the HTTP servlet transport. The transport class that should be specified in the
catalina-server.xml file is as follows:
Transport connector parameters
In addition to the configuration parameters supported by the HTTP servlet transport, HTTPS servlet transport supports the following configuration parameters:
In the transport parameter tables, the literals displayed in italics under the "Possible Values" column should be considered as fixed literal constant values. Those values can be directly put in transport configurations.
Transport level security protocol to be used.
|enableLookups||Set to ||true, false|
|clientAuth||Set to ||true, false|
|scheme||Set this attribute to the name of the protocol you wish to have returned by calls to ||http, https|
|secure||Set this attribute to ||true, false|
|SSLEnabled||Use this attribute to enable SSL traffic on a connector. To turn on SSL handshake/encryption/decryption on a connector set this value to ||true, false|
Path to the keystore which should be used for encryption/decryption.
A valid file path to a keystore file
Password to access the specified keystore.
A valid password
Similar to the servlet HTTP transport, this transport is also based on Apache Tomcat's connector implementation. For a complete list of supported parameters, see Tomcat connector configuration reference.
Defining multiple tomcat connectors
You have the option of defining multiple HTTPS connectors in the
catalina-server.xml file in the same way as for HTTP connectors. See HTTP servlet transport for more information.