Configuring Transport Level Security

Given below are the various transport-level security configurations that are required for WSO2 API Manager. See the following topics for instructions.

Disabling weak ciphers

A cipher is an algorithm for performing encryption or decryption. When you set the sslprotocol of your server to TLS, the TLS and the default ciphers get enabled without considering the strength of the ciphers. This is a security risk as weak ciphers, also known as EXPORT ciphers, can make your system vulnerable to attacks such as the Logjam attack on Diffie-Hellman key exchange. The Logjam attack is also called the Man-in-the-Middle attack. It downgrades your connection's encryption to a less-secured level (e.g., 512 bit) that can be decrypted with sufficient processing power.

To prevent these types of security attacks, it is encouraged to disable the weak ciphers. You can enable only the ciphers that you want the server to support in a comma-separated list in the ciphers attribute. Also, if you do not add this cipher attribute or keep it blank, the browser will support all the SSL ciphers by JSSE. This will enable the weak ciphers.

Disabling weak ciphers for the Tomcat transport

  1. Open the <PRODUCT_HOME>/repository/conf/deployment.toml file.
  2. Take a backup of the deployment.toml file and stop the Carbon server.
  3. Add the following configuration to the deployment.toml file by adding the list of ciphers that you want your server to support as follows:


    For a list of cipher suites that are secure and functional in Tomcat for the TLSv1.2 and TLSv1.3 protocols, see the list of ciphers provided in the secure configuration generator, which the Mozilla Foundation provides.

  4. Start the server.

  5. To verify that the configurations are all set correctly, download and run the testsslserver.jar.


    Note the following when you run testsslserver.jar :

    • The "Supported cipher suites" section in the output does not contain any EXPORT ciphers.

    • When you use the supported cipher suites listed here, the BEAST attack status will be shown as vulnerable. Note that this is a client-side vulnerability caused by the TLSv1 protocol. You can make the BEAST status protected by removing TLSv1, which will make clients with TLSv1 unusable. Therefore, it is recommended tofixed this from the client side.

    $ java -jar testsslserver.jar localhost 9443


From Firefox 39.0 onwards, the browser does not allow to access Web sites that support DHE with keys less than 1023 bits (not just DHE_EXPORT). 768/1024 bits are considered to be too small and vulnerable to attacks if the hacker has enough computing resources.


  • To use AES-256, the Java JCE Unlimited Strength Jurisdiction Policy files need to be installed. Download them from, if your Java installation does not have it installed.
  • From Java 7, you must set the jdk.certpath.disabledAlgorithms property in the <JAVA_HOME>/jre/lib/security/ file to jdk.certpath.disabledAlgorithms=MD2, DSA, RSA keySize < 2048 . It rejects all algorithms that have key sizes less than 2048 for MD2, DSA and RSA.

Configuring PassThrough transport-level ciphers and TLS versions

  1. To enable preferred ciphers, add the configuration given below to the <PRODUCT_HOME>/repository/conf/deployment.toml file.

    PreferredCiphers = "<CIPHER_LIST>"
  2. To enable HTTP protocols (TLS versions), add the configurations given below to the <PRODUCT_HOME>/repository/conf/deployment.toml file.

    HttpsProtocols = "<TLS_VERSION_LIST>"
    HttpsProtocols = "TLSv1.2,TLSv1.3"

Changing the server name in HTTP response headers

By default, all WSO2 products pass "WSO2 Carbon Server" as the server value in HTTP headers when sending HTTP responses. This means that information about the WSO2 product stack will be exposed through HTTP responses. It is recommended to change this by configuring the server name in the deployment.toml file.

  1. Open the <PRODUCT_HOME>/repository/conf/deployment.toml file.
  2. Add a new server name using the server property (under the relevant Tomcat connector configuration):

    server="WSO2 Carbon Server"
    server="WSO2 Carbon Server"

Disabling HTTP Transports


It is recommended to disable the HTTP transport in an API Manager production setup. Using the Bearer token over HTTP is a violation of the OAuth specification and can lead to security vulnerabilities.

API Manager has two HTTP transports.

  • Passthru (API Traffic) Transport
  • Servlet (UI Traffic and Admin service access) Transport

See the instructions given below to disable these transports.

Disabling PassThrough Transport

Add the following configuration in the deployment.toml file (stored in the <API-M_HOME>/repository/conf folder).

enable = false


Comment out or remove the http_endpoint entry in the deployment.toml file (stored in the <API-M_HOME>/repository/conf folder). This is done to avoid an error that occurs when adding the above configuration.

    name = "Default"
    type = "hybrid"
    display_in_api_console = true
    description = "This is a hybrid gateway that handles both production and sandbox token traffic."
    show_as_token_endpoint_url = true
    service_url = "https://localhost:${mgt.transport.https.port}/services/"
    username= "${admin.username}"
    password= "${admin.password}"
    ws_endpoint = "ws://"
    wss_endpoint = "wss://"
    http_endpoint = "${http.nio.port}"
    https_endpoint = "${https.nio.port}"

Disabling Servlet Transport

Add the following configuration in the deployment.toml file (stored in the <API-M_HOME>/repository/conf folder).

enable = false

Disabling the WebSocket Transport

Add the following configuration in the deployment.toml file (stored in the <API-M_HOME>/repository/conf folder).

enable = false

Disabling the WebHook Transport

Add the following configuration in the deployment.toml file (stored in the <API-M_HOME>/repository/conf folder).

enable = false

What's Next?

See the Security Guidelines for Production Deployment for the full list of security-related recommendations for WSO2 API Manager.