TLS Authentication with Express Gateway Pt. 2

We’re back with more about how you can use Transport Layer Security (TLS) Client Authentication from the latest 1.8.0 release. We’ll cover how to revoke a client certificate and special use cases if you want to use TLS Authentication for a specific path.

How to revoke a client certificate

In case the client certification is tampered with or you just do not trust the owner anymore, it is possible to revoke a client certificate. Just like with other policies like JWT, key-auth, it is possible to revoke a credential.

There are multiple ways to revoke a client certificate depending on the configuration of your CA. When choosing your client certificate revocation strategy, you should also think about is whether or not you have transitioned from CRL to OCSP.

Require a client certificate just for a specific path?

No problem! Let’s look into how you can require a client certificate only for a particular path, rather than for the entire API.

Normally, TLS authentication must happen at the edge of your server and — it’s something that happens at TCP level rather than at HTTP level. Therefore, you might want to use two separate domains to handle where you need the TLS Authentication and where not. Something such as and might do the job.

However, if this is only a single case scenario, then you can move the TLS check on the HTTP level by making few modifications to your Express Gateway configuration:

"https": {
    "port": 4444,
    "tls": {
      "default": {
        "key": "/var/lib/certs/tls.key",
        "cert": "/var/lib/certs/tls.crt",
        "ca": ["/var/lib/chain/chain.pem"]
    "options": {
      "requestCert": true,
-      "rejectUnauthorized": true
+      "rejectUnauthorized": false

We have modified our HTTPS server configuration so that the server will ask for a client certificate, but it will let the connection happen even if no certificate has been provided. Let’s move the client certificate.

Check on the pipeline level using an adhoc condition

      - clientAuthEndpoint
      - terminate:
        - condition:
            name: not
              name: tlsClientAuthenticated
            statusCode: 403
      - proxy:
        - action:
            serviceEndpoint: backend

In the case when tlsClientAuthenticated is not true—that is, the client didn’t provide a certificate or the provided one is invalid—the request will be terminated with 403.

If it passes, the pipeline continues and the proxy action will be performed.

Moving On

TLS Authentication is an alternative method to authenticate a client that’s trying to connect to our system.

Aren’t API keys enough?

Client certificates offer a layer of security that API keys cannot provide. If an API key gets compromised mid-connection, it can be reused to fire its own valid, trusted requests to the backend infrastructure. Have questions? If you’re building the next awesome IoT or mobile banking app with TLS Authentication, we’d love to learn more. Join us on the Developer Community Gitter Channel and share what you’re building.

More Resources