<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>PKCS12 on CX's Blog</title><link>https://blog.imcaoxuan.cn/en/tags/pkcs12/</link><description>Recent content in PKCS12 on CX's Blog</description><generator>Hugo</generator><language>en-US</language><copyright>imcaoxuan.cn</copyright><lastBuildDate>Mon, 26 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.imcaoxuan.cn/en/tags/pkcs12/index.xml" rel="self" type="application/rss+xml"/><item><title>Accessing mTLS Websites with Client Certificates on macOS and iOS</title><link>https://blog.imcaoxuan.cn/en/posts/2026-10-26-mtls-client-cert-macos-ios/</link><pubDate>Mon, 26 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.imcaoxuan.cn/en/posts/2026-10-26-mtls-client-cert-macos-ios/</guid><description>&lt;h1 id="accessing-mtls-websites-with-client-certificates-on-macos-and-ios"&gt;Accessing mTLS Websites with Client Certificates on macOS and iOS&lt;/h1&gt;
&lt;p&gt;This article explains how to configure client certificates on macOS and iOS devices to access HTTPS websites that enable mutual TLS (mTLS). The examples use a private CA, &lt;code&gt;step-ca&lt;/code&gt;, Nginx, PKCS#12, and a PIV smart card. All domain names, certificate names, filenames, and IP addresses in this article are examples; replace them with your actual values.&lt;/p&gt;
&lt;h2 id="1-mtls-authentication-process"&gt;1. mTLS Authentication Process&lt;/h2&gt;
&lt;p&gt;With ordinary HTTPS, the client primarily validates the server certificate; mTLS additionally requires the server to validate the client certificate.&lt;/p&gt;</description></item></channel></rss>