Certificates
Client certificates (mTLS)
Section titled “Client certificates (mTLS)”Some APIs only answer when you present a certificate. Set it per environment in SSLConfiguration, the same setting
JetBrains IDEs use, or in the Environments tab under Client certificate (mTLS), which saves it in your private
file.
{ "dev": { "SSLConfiguration": { "clientCertificate": "./certs/me.pfx", "hasCertificatePassphrase": true } }}{ "dev": { "SSLConfiguration": { "certificatePassphrase": "…" } }}clientCertificateis a.pfxor.p12file, or a PEM certificate withclientCertificateKeyfor its key (unless the key is in the same file). Paths are relative to the env file.- With
hasCertificatePassphrase, Reqjet asks for the passphrase once per session, or readscertificatePassphrasefrom the private file. That setting is Reqjet’s own; JetBrains IDEs ignore it and ask. - The certificate is also used for OAuth token requests, WebSockets and server-sent events.
- Copy as cURL adds
--cert, without the passphrase.
On the command line, the passphrase comes from the private file, or is asked for on the terminal.
Self-signed server certificates
Section titled “Self-signed server certificates”By default, Reqjet checks the server’s certificate, as a browser does. For a development server with a self-signed certificate, turn the check off for that environment:
{ "local": { "baseUrl": "https://localhost:5001", "SSLConfiguration": { "verifyHostCertificate": false } }}Only turn it off for servers you control: without the check, anyone between you and the server could read and change the traffic.
The Timing tab on a response shows the server’s certificate: its names, issuer and valid dates, with a warning when it expires within a month.