Implementing App Transport Security on NodeJS

What is App Transport Security?

ATS is Apple’s term for a set of “best practice” minimum security requirements that must be met in order for a client to establish a connection with a server. ATS is being enforced by default on iOS 9, and OSX 10.11.

On Stackoverflow respondents will tell you that ATS = TLS 1.2, but this is only partly true. ATS actually has 3 requirements:

My experience implementing ATS

Diagnosing problems

Implementing ATS is actually pretty straight forward, but it took me a couple of days to get right. This was mostly due to my ignorance on network security. (In my defence I would note that the client gave supremely unhelpful error messages). Being able to diagnose the problem was the biggest challenge for me. Here are a few tools I found quite useful:


Implementing ATS in Node is simple. A minimal implementation might look something like this:

var https = require('https')
var fs = require('fs')

var privateKey = fs.readFileSync('/path/to/my/private/key', 'utf8')
var certificate = fs.readFileSync('/path/to/my/certificate', 'utf8')

var credentials = {
  key: privateKey,
  cert: certificate,

server = https.createServer(credentials, app)

My mistakes

Certificate chain

I am not sure if this was breaking ATS, but, reported that I was not providing the complete certificate chain, but only the client certificate.

I was using a certificate issued by Godaddy, and I found the missing certificates in their certificate repository. To include the certificate in my server, I followed this tutorial. As a short summary: You basically concatenate the two certificates together into a single file, which you use as your certificate file.

Cipher mapping

You should only allow the list of accepted ciphers as described in the ATS technotes.

A caveat is that this list provides the Cipher Suite Name, but in the Node documentation they refer to the ciphers using their OpenSSL names. I found the mapping to convert between the names here.

Outdated NodeJS

Finally, and this took me the longest to resolve, I was using a very out of date version of NodeJS. My server was running Ubuntu - Trusty Tahr, and I did a normal apt-get install, which installed node v0.10.40.

I do not know the minimum version for this configuration to work, but I would suggest installing the latest (v4.1.1 at the time of writing) using the method described in the node installation guide

Projects · Blog · Gallery · About ·