No RADIUS Server to Run
Authentication is built into every VPN server. There is no RADIUS server, shared secret or firewall rule for your IT team to maintain.
VPN With RADIUS Authentication
Every PrivyNet VPN server uses RADIUS authentication over IKEv2, pre-configured as part of the deployment. There is nothing to set up. Your users sign in to the VPN with their PrivyNet account, and you decide who can reach each VPN server from your dashboard.
How RADIUS Authentication Works, and Why We Handle It for You
When a user connects to their PrivyNet VPN server, the sign-in is checked against their PrivyNet account and their access to that server, and the result is returned in seconds
User Device
User enters their PrivyNet email and password on their device
IKEv2 Tunnel
Credentials travel through an encrypted IKEv2 tunnel
PrivyNet VPN Server
The RADIUS service on the dedicated VPN server receives the sign-in
PrivyNet Platform
Checks that the account is active and holds an access grant for this VPN server
Your Dashboard
Where you add users and grant or remove access to each VPN server
RADIUS is already configured on every PrivyNet VPN server. There is no RADIUS server for you to run and no VPN-side configuration work required.
What Pre-Configured RADIUS Authentication Means in Practice
The operational impact of authentication that is built in and managed from your dashboard
One Account Per Person
Each person signs in to the VPN with their own PrivyNet account, so every connection belongs to a named user. No shared passwords.
Access Per VPN Server
A valid sign-in is not enough. Each user needs an access grant for the VPN server they connect to, so people reach only the servers you choose.
Remove Access in One Place
Deactivate a user in your dashboard and their VPN sessions are disconnected and they cannot sign in again. There is no separate step on the VPN server.
What Setup Looks Like on Your Side
Three steps in your dashboard. PrivyNet handles everything else.
Add Your Users
Add each team member in your dashboard. Each person sets their own password the first time they sign in.
Grant Access to a VPN Server
Choose which users can connect to each VPN server. Nobody can connect without an access grant.
Your Team Connects
Users connect over IKEv2 with their PrivyNet email and password. Remove the grant or deactivate the user to end their access.
PrivyNet handles the RADIUS configuration on the VPN server: it is pre-built into the infrastructure. Every grant and removal of access is recorded in your access log.
Frequently Asked Questions
Common questions about RADIUS authentication on PrivyNet
Does PrivyNet support RADIUS authentication?
Yes. Every PrivyNet dedicated VPN server uses RADIUS authentication over IKEv2. It is pre-configured as part of every deployment, so there is nothing for your team to set up.
Do I need to configure RADIUS on my PrivyNet VPN server?
No. RADIUS authentication is pre-configured in PrivyNet's infrastructure. You add your users and grant access in the dashboard, and there is no VPN-side configuration required from your team.
What do users sign in to the VPN with?
Their own PrivyNet account: the email address and password they use for PrivyNet. Each person has their own sign-in, so every connection belongs to a named user.
How do I remove someone's access?
Remove their access grant for that VPN server, or deactivate the user, in your dashboard. A deactivated user is disconnected from every VPN server and cannot sign in again.
Enterprise Authentication, Without the Enterprise Setup Overhead
RADIUS authentication is pre-configured in every PrivyNet deployment. Add your users, grant access from your dashboard and your team is connected, with no VPN-side configuration required.
RADIUS pre-configured
Managed from your dashboard
Zero VPN-side setup
