Page tree
Skip to end of metadata
Go to start of metadata


In order to configure SSL connection between server and client you need to have SSL certificate and private key. After getting them you will be able to configure FIXEdge so that the SSL connection between server and client(s) can be established.

How to get SSL certificate and private key

There are two ways to get the SSL certificate and the private key:

  1. Create the self-signed SSL certificate and the private key via OpenSSL.
    The instruction about how to create such a certificate and key can be found here: How to configure built-in SSL support for FIX session in FIXEdge
    This type of certificates is only suitable for testing period, because most clients don't trust self-signed certificates.
  2. Prepare a Certificate Signing Request (CSR) from a Certificate Authority (CA), for example, "DigiCert".
    In order to do it, you should create the private key file and then generate CSR.
    You can find the instruction here:

    During this process you have to provide the following information for CA:
    1. commonName (for example, “CN=B2BITS”)

    2. organizationalUnitName (for example, “OU=Dev”)

    3. organizationName (for example, “O=EPAM Systems”)

    4. localityName (for example, “L=Newtown”)

    5. stateOrProvinceName - should not be abbreviated (for example, “S=Pennsylvania”)

    6. countryName - two-letter ISO code for the country where your organization is located (for example, “C=US”)

    7. emailAddress - an email address to contact the organization. Usually the email address of the certificate administrator or IT department

    CA will create the SSL certificate based on provided information. After that you should install this certificate on your server.

Do not forget to back up your private key and certificate in a secure place. Share private key only with entitled personnel.

How to validate the SSL certificate

After you got the certificate you can check all information about it using the command line opened in the same folder where the certificate is placed:

openssl x509 -in cert.pem -text

where cert.pem is a certificate name.

You will see the following information:

openssl x509 -in cert.pem -text
        Version: 3 (0x2)
        Serial Number: 11159143049149737040 (0x9add3d7ac256e850)
    Signature Algorithm: sha1WithRSAEncryption
        Issuer: C=US, ST=PA, L=Newtown, O=EPAM Systems, OU=Dev
            Not Before: Oct 19 14:46:36 2015 GMT
            Not After : Oct 18 14:46:36 2016 GMT
        Subject: C=US, ST=PA, L=Newtown, O=EPAM Systems, OU=Dev
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
                Public-Key: (2048 bit)
                Exponent: 65537 (0x10001)
        X509v3 extensions:
            X509v3 Subject Key Identifier:
            X509v3 Authority Key Identifier:
            X509v3 Basic Constraints:
    Signature Algorithm: sha1WithRSAEncryption

How to validate the private key

In order to check the private key you can use the following command:

openssl rsa -in key.pem -check

where privateKey.key is a private key name.

You will see the following information:

openssl rsa -in key.pem -check
RSA key ok
writing RSA key
<actual key here>

The certificate and the private key can be merged into the one file (for example, cert.pem).

Types of SSL protocols

There are a lot of SSL protocols. FIXEdge supports SSL v2.0, SSL v3.0, TLS v1.0, TLS v1.1, TLS v1.2. By default only TLS v1.0, TLS v1.1, TLS v1.2 protocols are enabled in FIX Edge.

It's highly recommended to use TLS v1.1 or TLS v1.2 protocol, because SSL protocol versions were deprecated (see: Deprecating SSL v3.0 )

Recommended TLS 1.1 and TLS 1.2 protocols are supported only by OpenSSL version 1.0.1 and higher (see: ).

How to configure FIXEdge

The article which describes how to configure FIXEdge for SSL connection can be found here: How to configure built-in SSL support for FIX session in FIXEdge

  • No labels