You are attempting to use a client certificate for mTLS authentication in a Windows browser (e.g., Google Chrome, Microsoft Edge), but the certificate does not appear in the selection prompt when accessing an application URL (e.g., `https://your-application-url.example.com`). The same client certificate may function correctly in other tools like Postman when provided as separate `.crt` and `.key` files.
CAUSE
Windows browsers (such as Chrome and Edge) retrieve client certificates for mTLS authentication exclusively from the Windows Certificate Store (via CryptoAPI/CNG). They do not directly access certificate files from disk. For a client certificate to be available for selection in these browsers, it must be correctly imported into the `Current User > Personal > Certificates` store. A common reason for the certificate not appearing is that only the public certificate (`.crt` or `.cer` file) was imported, without its corresponding private key. Browsers will only list certificates that have an accessible private key associated with them.
SOLUTION
To ensure your client certificate is correctly recognized and available for mTLS authentication in Windows browsers, follow these steps:
1. **Obtain the Client Certificate with Private Key:**
Ensure you have your client certificate bundled with its corresponding private key. This is typically provided in a PKCS#12 format file, with extensions like `.pfx` or `.p12`.
2. **Convert Certificate Files to PKCS#12 (if necessary):**
If you only have separate public certificate (`.crt` or `.cer`) and private key (`.key`) files, you must combine them into a PKCS#12 (`.pfx` or `.p12`) file using a tool like OpenSSL.
Run the following command, replacing placeholders with your actual file names:
```bash
openssl pkcs12 -export -out client.pfx -inkey client.key -in client.crt -name "Your Client Certificate Name"
```
*Optional: To include the CA certificate chain (intermediate and/or root CAs) in the PKCS#12 bundle, use the `-certfile` flag:*
```bash
openssl pkcs12 -export -out client.pfx -inkey client.key -in client.crt -certfile ca_chain.crt -name "Your Client Certificate Name"
```
*Note: The `ca_chain.crt` file should contain the certificate(s) of the Certificate Authority (CA) that issued your client certificate. This file is typically provided by your certificate issuer.*
3. **Import the PKCS#12 File into the Windows Certificate Store:**
a. Locate the generated `.pfx` or `.p12` file on your system.
b. Double-click the file to launch the Certificate Import Wizard.
c. Follow the wizard prompts:
* Select "Current User" as the Store Location.
* Provide the password for the private key if prompted (this is the password you set during the `openssl pkcs12 -export` command or the password provided with your `.pfx` file).
* On the "Certificate Store" page, select "Place all certificates in the following store" and then browse to select the **Personal** store.
* Complete the wizard.
4. **Verify Certificate Installation:**
a. Open the Certificate Manager for the current user by pressing `Win + R`, typing `certmgr.msc`, and pressing Enter.
b. Navigate to `Certificates - Current User > Personal > Certificates`.
c. Confirm that your client certificate is listed. It should have a small key icon next to it, indicating that the private key is correctly associated and accessible.
5. **Restart Your Browser:**
Close all instances of your web browser (Chrome, Edge) and then reopen it. This ensures the browser reloads the updated Windows Certificate Store.
6. **Access the Application:**
Navigate to your application URL (e.g., `https://your-application-url.example.com`). Your browser should now prompt you to select the imported client certificate for authentication.
APPLIES TO
* Operating Systems: Microsoft Windows (e.g., Windows 10, Windows 11, Windows Server)
* Web Browsers: Google Chrome, Microsoft Edge
* MuleSoft applications requiring mTLS client authentication (e.g., applications deployed on CloudHub, Runtime Fabric, or customer-hosted runtimes accessed via a load balancer configured for mTLS).
005460503

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.