Certificate Validation in Dedicated Load Balancers

logo cloud active logo hybrid disabled logo server disabled logo rtf disabled

If at least one CA certificate is provided for the SSL endpoint, the load balancer passes the client certificate data to the API using these HTTP headers:

  • X-SSL-Client-Verify

    Returns one of:

    • SUCCESS

      The client is verified only after SUCCESS.

    • NONE when the certificate is not present

    • FAILED when other validation problems occur

  • X-SSL-Client-DN

    Contains the full distinguished name of the client certificate

  • X-SSL-Issuer

    Contains the full distinguished name of the issuing certificate

  • X-SSL-Client-Serial

    Contains the serial number used by the CA to identify the client

Add Revocation Lists

The CloudHub load balancer can optionally verify client requests against certificate revocation lists (CRL). All CRL files must be concatenated into a single, unencrypted PEM-encoded file for upload. The order of items in the CRL is not important.

To add a revocation list when you create the load balancer, use the --crl option with the cloudhub load-balancer create command.

If your load balancer already exists, you can use the CloudHub API to add or update your CRLs. To do so, send a PATCH request to the /organizations/{myOrgID}/vpcs/{myVpcID}/loadbalancers/{myDlbID} endpoint and include a revocationList element:

[
  {
    "op": "replace",
    "path": "/sslEndpoints/0/revocationList",
    "value": "-----BEGIN X509 CRL-----\nMIIBTTCBtwIBATANBgkqhkiG9w0BAQUFADBXMQswCQYDVQQGEwJBVTETMBEGA1UE\nCBMKU29tZS1TdGF0ZTEhMB8GA1UEChMYSW50ZXJuZXQgV2lkZ2l0cyBQdHkgTHRk\nMRAwDgYDVQQDEwdvcmcuY29tFw0xNjAzMTUwOTI2MThaFw0xODAzMTUwOTI2MTha\nMBwwGgIJAIBvvO4dJHjhFw0xNjAzMTUwODUwMTZaoA4wDDAKBgNVHRQEAwIBBjAN\nBgkqhkiG9w0BAQUFAAOBgQCCAbGXW+Hnzmd1bXqWsFXfogOsJScoxkJOhhmjui3I\nhTUyO5plGHUBLjBnDkypM+iLfn0W4wPcNj7FZdz4Hu/WLntxwrTtR5YOcfIhEGcq\nwvJq/1+WKUPC6eqGwx0iKOOBIWsaf5CNOOUQMo6RaeTeu8Uba2EGFk1Vu/SoZYAK\nsw==\n-----END X509 CRL-----\n"
  }
]

To get the values for myVpcID and myDlbID values from the CLI, use the cloudhub vpc describe-json and cloudhub load-balancer describe-json commands.

To update any other property, send a PATCH request to your load balancer endpoint.

Prepare to Manage Certificate Cipher Suites

To manage cipher suites with the CloudHub API, you must first:

Generate Authorization Bearer Token

To generate your authorization bearer token for Anypoint Platform:

  1. Send your Anypoint Platform user name and password to the API:

    curl -X POST 'https://anypoint.mulesoft.com/accounts/login' -H 'Content-Type: application/json' -d '{"username":"myUsername","password":"myPassword"}'

    This command returns the access token:

    {
      "access_token": "myAccessToken",
      "token_type": "bearer",
      "redirectUrl": "/home/"
    }
  2. Copy the value of access_token to use in the API calls.

Manage Certificate Cipher Suites

Using the CloudHub API, you can:

List Available Cipher Suites

To list available cipher suites for an organization using the CloudHub API:

  1. Prepare to manage certificate cipher suites.

  2. Run this GET call:

    curl https://anypoint.mulesoft.com/cloudhub/api/organizations/myOrgID/loadbalancers/ciphersuites -H 'Authorization: Bearer myAccessToken' | jq
    • myOrgID is the organization ID.

    • myAccessToken is the access token you generated.

The output includes ciphers:

{
  "data": [
      {
          "id": "5b4a36e1e65c892316abd4d1",
          "name": "NewDefault-v1",
          "ciphers": "ECDHE-RSA-AES256-GCM-SHA512:DHE-RSA-AES256-GCM-SHA512:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES256-GCM-SHA384",
          "description": "Default ciphers (new version)-v1",
          "defaultSuite": true
      },
      {
          "id": "5b4a36e1e65c892316abd4d2",
          "name": "OldDefault",
          "ciphers": "ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA:ECDHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:HIGH:!aNULL:!eNULL:!EXPORT:!DES:!MD5:!PSK:!RC4",
          "description": "Default ciphers (old version)",
          "defaultSuite": false
      },
      {
          "id": "5b4bfedee4b0f45ab1de6979",
          "name": "EcdheEcdsaRsa",
          "ciphers": "ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-SHA384",
          "description": "ECDHE ECDSA RSA ciphers",
          "defaultSuite": false
      },
      {
          "id": "5ba28106e4b00522d78f40b6",
          "name": "RestrictCiphers",
          "ciphers": "AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256",
          "description": "Restricted Ciphers",
          "defaultSuite": false
      }
  ],
  "total": 4
}

The following recommended cipher suites provide a good balance between compatibility and security for your SSL endpoint:

ECDHE-RSA-AES256-GCM-SHA512
DHE-RSA-AES256-GCM-SHA512
ECDHE-RSA-AES256-GCM-SHA384
DHE-RSA-AES256-GCM-SHA384

Most cipher suites offer forward secrecy. RC4-SHA (supports Internet Explorer 8) does not. For this reason, MuleSoft and Microsoft do not recommend using it.

The CloudHub dedicated load balancer supports TLS 1.2. TLS 1.1 is disabled and is not supported by default.

Although you can configure TLS 1.0, PCI compliance doesn’t accept this protocol because of its significant vulnerabilities.

Display the Default Cipher Suite for a DLB

To display the default cipher suite for a DLB using the CloudHub API:

  1. Prepare to manage certificate cipher suites.

  2. Run this GET call:

    curl https://anypoint.mulesoft.com/cloudhub/api/organizations/myOrgID/vpcs/myVpcID/loadbalancers/myDlbID -H 'Authorization: Bearer myAccessToken' | jq

    In the command:

    • myOrgID is the organization ID.

    • myVpcID is the ID for the VPC.

    • myDlbID is the ID for the DLB.

    • myAccessToken is the access token you generated.

The output includes defaultCipherSuite:

"defaultCipherSuite": "ECDHE-RSA-AES256-GCM-SHA512:DHE-RSA-AES256-GCM-SHA512:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES256-GCM-SHA384"

Rotate the Cipher by Replacing the Default Cipher Suite

To rotate the cipher by replacing the default cipher suite for a DLB using the CloudHub API:

  1. Prepare to manage certificate cipher suites.

  2. Run this GET call:

    curl -X PATCH
    https://anypoint.mulesoft.com/cloudhub/api/organizations/myOrgID/vpcs/myVpcID/loadbalancers/
    myDlbID  -H 'Authorization: Bearer myAccessToken'
    -H 'Content-Type: application/json'
    -d '[{"op":"replace", "path":"/defaultCipherSuiteName", "value":"NewDefault-v1"}]' | jq

    In the command:

    • myOrgID is the organization ID.

    • myVpcID is the ID for the VPC.

    • myDlbID is the ID for the DLB.

    • myAccessToken is the access token you generated.

    • NewDefault is the value of name for a cipher suite from the list of available cipher suites that you generated in List Available Cipher Suites.

The output now includes defaultCipherSuite:

"defaultCipherSuite": "ECDHE-RSA-AES256-GCM-SHA512:DHE-RSA-AES256-GCM-SHA512:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES256-GCM-SHA384"

Change the Default Cipher Suite to Support TLS 1.0

To support TLS 1.0, change the default cipher suite to OldDefault:

  1. Prepare to manage certificate cipher suites.

  2. Display the current default cipher suite.

  3. Change the default cipher suite:

    curl -X PATCH https://anypoint.mulesoft.com/cloudhub/api/organizations/myOrgID/vpcs/myVpcID/loadbalancers/myDlbID  -H 'Authorization: Bearer myAccessToken' -H 'Content-Type: application/json' -d '[{"op":"replace", "path":"/defaultCipherSuiteName", "value":"OldDefault"}]' | jq

    In the command:

    • myOrgID is the organization ID.

    • myVpcID is the ID for the VPC.

    • myDlbID is the ID for the DLB.

    • myAccessToken is the access token you generated.

    • OldDefault is the name of the cipher suite that supports TLS 1.0.

  4. Check the default cipher suite and verify that the output includes the following line:

    "defaultCipherSuite": "ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA:ECDHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:HIGH:!aNULL:!eNULL:!EXPORT:!DES:!MD5:!PSK:!RC4"

Verify the TLS 1.0 Connection

After enabling TLS 1.0, test the connection:

  • openssl

    Run this command against the DLB SSL endpoint:

    openssl s_client -connect DNS of the SSL endpoint:443 -tls1

    • If the output includes the certificate information and the message Secure Renegotiation IS supported, TLS 1.0 is supported.

    • If the command returns write:errno=54, TLS 1.0 is not supported.

  • curl

    Run this command against the DLB SSL endpoint:

    curl -vI --insecure --tlsv1.0 https://DNS of the SSL endpoint

    • If you see the returned results from the backend server or the HTTP error code, TLS 1.0 is supported.

    • If the command returns curl: (35) Server aborted the SSL handshake, TLS 1.0 is not supported.

Was this article helpful?

💙 Thanks for your feedback!

Edit on GitHub