---
title: About TLS Crypt v2 Connection Profiles
canonical: https://openvpn.net/cloud-docs/owner/get-started/about-cloudconnexa/about-tls-crypt-v2-connection-profiles/
product: CloudConnexa Docs
description: CloudConnexa connection profiles use TLS Crypt v2 by default, giving each profile its own unique control-channel key. Learn how TLS Crypt v2 differs from TLS Auth, which clients and routers support it, and when to download a legacy profile instead.
---

# About TLS Crypt v2 Connection Profiles

## Overview

CloudConnexa uses TLS Crypt v2 to protect the control channel in new connection profiles for devices and OpenVPN connectors. Previously, CloudConnexa used TLS Auth for all connection profiles.

The OpenVPN protocol uses two channels during a VPN connection:

- **Control channel:** Handles authentication, key negotiation, and configuration before data starts flowing.
- **Data channel:** Encrypts and transports traffic through the VPN connection.

TLS Auth and TLS Crypt v2 both protect control-channel communications, but they use different approaches to authentication, encryption, and key management.

## TLS Auth

TLS Auth authenticates control-channel packets using a shared key. It rejects packets without a valid authentication signature but doesn't encrypt the control channel.

With TLS Auth, CloudConnexa connection profiles share the same control-channel authentication key. If that key is exposed, it can affect other profiles using the same key.

## TLS Crypt v2

TLS Crypt v2 authenticates and encrypts control-channel traffic using a unique key for each connection profile, also called a **per-profile key**.

This provides several security benefits:

- **Per-profile key protection:** If a connection profile is exposed, its control-channel key doesn't expose the keys assigned to other profiles.
- **Encrypted control channel:** TLS Crypt v2 encrypts control-channel communications in addition to authenticating them.
- **Early client identification:** CloudConnexa can identify a connecting client before the TLS handshake is completed.
- **Stateless DoS protection:** OpenVPN 2.6 and newer can use TLS Crypt v2 to reject certain invalid or replayed connection attempts before completing the TLS handshake, reducing the resources spent processing unwanted traffic.

## What changes for connection profiles

> **Important**
>
> Your existing VPN connections will keep working. You don't need to make any changes.

CloudConnexa now uses TLS Crypt v2 by default when you download a new connection profile for a device or OpenVPN connector. Here's what that means for you:

- **Existing connections:** Your current connection profiles will continue to work with TLS Auth. You don't need to replace existing profiles or reconnect your devices and Connectors.
- **New or re-issued profiles:** When you download a new connection profile, it uses TLS Crypt v2 by default.
- **Older clients and routers:** If your device or router doesn't support TLS Crypt v2, you can download a legacy profile that uses TLS Auth instead.
- **Certificate validity:** Your connection profile certificates are still valid for 25 years from their issue date.
- **IPsec connectors:** Nothing changes for IPsec connectors.

> **Note**
>
> You can use TLS Auth and TLS Crypt v2 profiles in the same Wide-Area Private Cloud (WPC). This means you can update devices and connectors when you're ready, without updating everything at once.

## Client and router compatibility

> **Tip**
>
> Most current OpenVPN clients support TLS Crypt v2, so you can use the default connection profile without making any changes.

If you're using an older OpenVPN client or router, you may need a legacy profile instead. Check your client or router version to determine which profile to download.

| **Client or router** | **TLS Crypt v2 profile** | **Legacy profile (TLS Auth)** |
| --- | --- | --- |
| OpenVPN Connect 3.2 and newer | Supported | Supported |
| OpenVPN Connect older than 3.2 | Not supported | Supported |
| OpenVPN 2.6 and newer | Supported, including stateless DoS protection | Supported |
| OpenVPN 2.5 | Supported | Supported |
| OpenVPN older than 2.5 | Not supported | Supported |
| Routers running OpenVPN older than 2.5 | Not supported | Supported |

For routers, compatibility depends on the OpenVPN version included in the router firmware, not just the router model. For more information, refer to [Router Connectors](https://openvpn.net/cloud-docs/owner/get-started/about-cloudconnexa/network-connectors-for-routers.md).

> **Important**
>
> If your router uses OpenVPN older than 2.5 and you can't update its firmware, download a legacy connection profile.

## Download a legacy connection profile

You only need a legacy connection profile if your client or router doesn't support TLS Crypt v2. Otherwise, use the default profile.

You can download legacy profiles for devices and OpenVPN connectors from the CloudConnexa Administration Portal.

### Download a legacy profile for a device from the Administration Portal

1. Sign in to the CloudConnexa Administration Portal using your WPC's **Cloud ID** address (for example, `yourcompany.openvpn.com`).
2. Navigate to **Users → Devices**.
3. Select the **Device Actions** menu for the device.
4. Select **Download Legacy Profile (no TLS Crypt v2)**.
   - The legacy connection profile downloads to your computer. Import it into your OpenVPN client to connect to CloudConnexa.

### Download a legacy profile for a connector

If your Network or Host Connector uses an OpenVPN version that doesn't support TLS Crypt v2, download a legacy profile instead.

1. Sign in to the CloudConnexa Administration Portal using your WPC's **Cloud ID** address (for example, `yourcompany.openvpn.com`).
2. Navigate to **Networks → Connectors** or **Hosts → Connectors**, depending on the connector type.
3. Select the **Connector Actions** menu for the connector.
4. Select **Download Legacy Profile (no TLS Crypt v2)**.
   - The legacy connection profile downloads to your computer. Use it to configure the connector.

### Download a legacy profile when deploying a network connector to a router

If your router doesn't support TLS Crypt v2, you can download a legacy profile during connector deployment.

1. In the **Deploy Network Connector** step, select **Download Legacy Profile (no TLS Crypt v2)** instead of **Download Profile**.
2. Use the downloaded profile to configure your router.

## Troubleshooting

### My router doesn't connect with the default profile

Your router may be running an OpenVPN version that doesn't support TLS Crypt v2.

1. Check the OpenVPN version included in your router firmware.
2. If it's older than 2.5, download a legacy connection profile for the Network Connector.
3. Import the legacy profile into your router and try connecting again.

If your router supports a newer OpenVPN version, you can also update its firmware and try the default profile again.

### OpenVPN Connect can't import or use my connection profile

If you're using OpenVPN Connect older than version 3.2, the app doesn't support TLS Crypt v2.

1. Check your OpenVPN Connect version.
2. If it's older than 3.2, update to a supported version.
3. Import the connection profile again.

If you can't update OpenVPN Connect, ask your CloudConnexa administrator to download a legacy connection profile for your device from the Administration Portal, then import it.

## Related topics

- [About Connectors](https://openvpn.net/cloud-docs/owner/get-started/about-cloudconnexa/cloudconnexa-connectors.md)
- [Connectors Types](https://openvpn.net/cloud-docs/owner/get-started/about-cloudconnexa/types-of-cloudconnexa-connectors.md)
- [Router Connectors](https://openvpn.net/cloud-docs/owner/get-started/about-cloudconnexa/network-connectors-for-routers.md)
- [Download an OpenVPN Network Connector's connection profile as a .ovpn file](https://openvpn.net/cloud-docs/owner/networks/networks---connectors/download-an-openvpn-network-connector-s-connection-profile-as-a--ovpn-file.md)
- [Download a Host Connector's connection profile as a .ovpn file](https://openvpn.net/cloud-docs/owner/hosts/hosts---connectors/download-a-host-connector-s-connection-profile-as-a--ovpn-file.md)

---

Prev: [CloudConnexa Service Health Status](https://openvpn.net/cloud-docs/owner/get-started/about-cloudconnexa/cloudconnexa-service-health-status.md)
Next: [About Connectors](https://openvpn.net/cloud-docs/owner/get-started/about-cloudconnexa/cloudconnexa-connectors.md)
Index: https://openvpn.net/cloud-docs/llms.txt
