# VPN Service

> For the complete documentation index, see [llms.txt](https://help.1nce.com/llms.txt).

# VPN Service

This page covers how OpenVPN changes on the 1NCE Platform 2.0 and what you need to do to migrate.

## Authentication

| | 1NCE Platform 1.0 | 1NCE Platform 2.0 |
| --- | --- | --- |
| Authentication | Username / password | **Certificate-based** |
| Configuration | Separate credentials + configuration files | One configuration file |

On the 1NCE Platform 2.0, OpenVPN uses **certificate-based authentication** instead of username and password. You receive a single configuration file that replaces your two (credentials + configuration) existing ones.

:::info Certificate renewal
On the 1NCE Platform 2.0, authentication certificates are valid for **two years**. Plan for certificate renewal every two years as part of your operations.
:::

:::note One connection per customer
By default, you can run **one OpenVPN connection per customer account**. If you need multiple connections, contact 1NCE Support to file a service ticket.
:::

## Hybrid mode — simpler migration

During migration, use **hybrid mode** to connect to both core networks through a single OpenVPN connection. This is the simplest approach:

1. Download the 1NCE Platform 2.0 configuration file from the Portal.
2. Replace your current configuration file with the new one.
3. Restart your VPN client.

From that point forward, a **single OpenVPN connection serves both your 1NCE Platform 2.0 and 1NCE Platform 1.0 core network traffic**. The backend automatically routes your migrated and not-yet-migrated SIMs — you manage only one client throughout the transition.

:::danger Do not run both VPNs simultaneously
Do **not** run both the 1NCE Platform 2.0 and 1NCE Platform 1.0 VPN connections at the same time. Running both connections simultaneously will not work. Complete the configuration swap as a single cutover step.
:::

:::info Fallback to old configuration
If you need to roll back during migration, switch back to your old configuration file, restart the VPN client, and contact 1NCE Support for help if needed.
:::

## What to do

- Download the 1NCE Platform 2.0 configuration file during your migration window.
- Swap your configuration file and restart the VPN client.
- Plan for certificate renewal **every two years**.
- If you need **multiple connections**, contact 1NCE Support.
- After migration, your VPN should work exactly as before — traffic flows through a single OpenVPN connection that serves both core networks.