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

# sk66760 - Captive Portal certificate used by ipsec vpn

| Property | Value |
|----------|-------|
| Solution ID | sk66760 |
| Date Created | 2012-02-23 |
| Last Modified | 2017-07-09 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |

## Symptoms

- After creating a certificate to use for the Captive Portal, the same certificate is used for IPSEC VPN.

## Cause

In SmartDashboard, there is one default certificate in the:

Gateway properties \> IPSEC VPN \> Repository of Certificates Available to the Gateway \>

This default certificate is suppose to be used for IPSEC clients.

If the user configures a certificate for Identity Awareness:

Gateway properties \> Identity Awareness \> Captive Portal Settings \> Access Settings \> Certificate \>  
this portal is associated with this certificate: xxxxxx.com

ALL portals on the same IP address use the same certificate including IPSEC VPN.

## 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