Documentation

SSL Client Certificate

SSL Client Certificate¶

Authentication
SSL Client Certificate

Environments as reusable presets
Use invalid SSL certificates

What is a SSL Client Certificate?¶

SSL Client Certificates are used to digitally identify a particular individual or user with an authentication server. Please refer to RFC 6101 - Client Certificate for more information.

Paw natively supports X.509 certificate authentication for use with a secure TLS/SSL connection via the Certificate Dynamic Value.

Setup SSL Client Certificate¶

Find your Certificate & Private Key

Find your Certificate & Private Key¶

Your API provider should give you access to a X.509 certificate and a private key to be used for authentication.

Setup Dynamic Value

Setup Dynamic Value¶

In the Options tab, click the SSL Client Certificate field to popup the Certificate Dynamic Value. You can setup your certificate using:

PEM: if you have been given a certificate and private key files, chances are that you have either a PKCS #12 archive file (.p12 or .pfx) or a pair of PEM files (.pem). You can import them using the Import from File button. If the certificate and private key were given to you in text format (limited by -----BEGIN ...----- and -----END ...----- headers), you can directly paste them on the editor. Certificate and Private Key will be encrypted and stored on the document file.

Keychain: if you have a certificate and private key ready to be used on Keychain, you can select it from Paw. Certificate and Private Key won’t be stored on the document file.

../../_images/ssl-certificate-keychain.png

Done

Done¶

Your SSL Client Certificate field should be green now, indicating that your request is properly configured for SSL Client Authentication!

Use Environment Variables¶

orphan:

As you may often switch between development and production environments, or between several users, you may need to have several OAuth credentials you may apply to your Requests. You can keep those credentials in Environments, and then use them in the OAuth Header Dynamic Value.

Read more about Environments and how to use Environments as Reusable Presets.

You can add a Certificate Dynamic Value as an environment variable value, and then reference this environment variable on any Request that requires SSL Client Certificates for authentication:

On the Environments panel, define a new enviorment variable MyCert, adding a Certificate Dynamic Value as value (context menu Authorization > Certificate)

Setup the Certificate Dynamic Value accordingly

On every request you need authentication, go to the request Options tab, click the certificate icon on the SSL Client Certificate field and select the Regular Field menu item.

Remove the existing Certificate Dynamic Value and type {MyCert} - the autocomplete will suggest the environment variable you have previoulsy defined; type Enter to select it.