> Source: [sk182436](https://support.checkpoint.com/results/sk/sk182436)

# sk182436 - Capsule Connect for iOS - User Certificate Authentication Failure

| Property | Value |
|----------|-------|
| Solution ID | sk182436 |
| Date Created | 2024-06-25 |
| Last Modified | 2024-06-26 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R81.20, R81.10 (EOS), R81 (EOS) |
| OS | iOS, Gaia |
| Platform | 5000 |

## Symptoms

- * iOS Capsule Connect authentication with user certificate fails after a day of connecting to the Security Gateway. Authentication works again after a Security Gateway reboot, but fails again after some days.

* The issue occurs only on iOS Capsule Connect clients. It does not occur on Desktop Remote Access VPN clients.

* The *vpnd.elg* file contains these lines:   
  `
  [vpnd ..... ..........]@...........[2 May 17:06:57][CERT] IsSignedByIntermediateCA: signatures don't match`  
  `
  [vpnd ..... ..........]@...........[2 May 17:06:57][CPTLS] `  
  `cptls_OneSideSSL::notifyValidationResult: 'Certificate Chain is not signed by a Trusted CA..
  `

  <br />

* Two subordinate CAs in SmartConsole have the same CN but different public keys. One CA is about to expire, and the other has been renewed.

## Cause

The CN serves as the identifier of the CA certificate regardless of the keys used, so one subordinate CA mismatches the user certificate.

<br />

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content