Onboarding Utility
Requests

Using Mutual TLS on the Client Side with Requests

How to use TLS, client authentication, and CA certificates in Requests

Create a private key and request a certificate for your Requests client

Before you can teach your client to speak TLS, you will need a certificate issued by a trusted certificate authority (CA). If your organization already runs its own CA and you have a private key and certificate for your Requests client, along with your CA's root certificate, you can skip to the next step.

If your organization does not yet run its own internal CA, you can read more about creating and running a CA using the open source Smallstep software here.

$ step ca certificate "myuser" client.crt client.key

Your certificate and private key will be saved in client.crt and client.key respectively.

Request a copy of your CA root certificate, which will be used to make sure each application can trust certificates presented by other applications.

$ step ca root ca.crt

Your certificate will be saved in ca.crt.

Make a request from Requests using mutual TLS

Now, we need only to configure our Requests client to make authenticated requests using our certificate and private key. The CA root certificate will be used to verify that the client can trust the certificate presented by the server.

Pass your certificate, private key, and root CA certificate to requests.get() (or its respective request method) to authenticate your request over TLS.

result = requests.get(
    'https://myserver.internal.net:443',
    cert=('client.crt', 'client.key'),
    verify='ca.crt')

# do something with result...

Improve this content

All documentation content from the Hello mTLS project is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0).

Creative Commons License

Connect to a Server from Requests

© 2019 Smallstep Labs, Inc. All rights reserved.