# Mutual TLS Client Certs

**URL:** <https://community.postman.com/t/mutual-tls-client-certs/5228>\
**Category:** Help Hub\
**Tags:** client-certificate\
**Created:** [April 30, 2019, 7:54pm UTC](https://community.postman.com/t/mutual-tls-client-certs/5228 "2019-04-30T19:54:43Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![MichaelMcD](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/michaelmcd/32/1730_2.png) [@MichaelMcD](https://community.postman.com/u/MichaelMcD)\
**Post date:** [April 30, 2019, 7:54pm UTC](https://community.postman.com/t/mutual-tls-client-certs/5228/1 "2019-04-30T19:54:43Z")

</div>

Using Postman v7.0.9 certificates configured under the **Settings/Certificates** are not being submitted with request to the host. This works as expected on earlier versions of Postman. This new behaviour is confirmed using the Postman console (and Fiddler). I don’t think this is a configuration issue because if I mis-type the certs name Postman prints out an appropriate error to the console, but does _nothing_ if it finds them.

Interestingly I had to upgrade cURL to v7.6.14 before it would work with the --cert and --key parameters.

I wonder if other users are seeing this or if anyone has an idea as to why this might be happening.

Thanx in adv.  
Michael McD.

Ps this is on a new Win 10 PC.