Recluda as the second factor for your organization's VPN.
How to make Recluda the second factor for your organization's VPN, set people up, and use the VPN tab in the app.
Your VPN already has a sign-in. Recluda plugs in as a RADIUS server, so after the username (and password, if you connect a directory) the person approves on their phone:
Each VPN username belongs to one person, and only that person's devices can approve its sign-ins.
Two places show the same three values:
In the admin console (on the server's network, port 5004): VPN → VPN Settings: Server, Port and Shared secret (click Show).
In the Recluda app, on an administrator's iPhone, iPad or Mac:
The secret is only shown to administrator accounts, with a fresh biometric signature, and it's hidden again when you close the screen. If it doesn't appear, see Troubleshooting.
In your VPN's settings, add a RADIUS (or AAA) server with:
| Setting | Value |
|---|---|
| Server address | the Server from step 1 |
| Authentication port | 1812, UDP |
| Shared secret | the Shared secret from step 1 |
| Authentication method | PAP |
| Timeout | 60 seconds or more (Recluda waits up to 60 s for the approval; a shorter VPN timeout rejects people who are still reaching for their phone) |
| Challenge / "RADIUS challenge" / "Access-Challenge" | on, if your VPN has the option |
| Accounting | optional; Recluda acknowledges it and ignores it |
Then make that RADIUS server the authentication for the VPN profile or connection your people use. The names differ by product; look for "AAA server group" (Cisco), "RADIUS server" and "PAP" (FortiGate), or "RADIUS server profile" with "Authentication protocol: PAP" (GlobalProtect).
Passwords. If your Recluda server is connected to your directory (LDAP), the password is checked against it first, then Recluda asks for approval: the usual "password, then phone". Without a directory, Recluda's approval is the only check and the password field is ignored.
A new person (they get a setup QR):
The code is shown once and is valid for 24 hours. If the username already belongs to someone, the QR adds another device to that person instead.
Someone who already uses Recluda: in VPN → People, type their VPN username next to their account and click Save.
In the People table, ● in teal next to a device means it can receive pushes; a grey ● means it hasn't sent a push token yet (open Recluda on it and allow notifications).
Everyone sees:
Administrators also use For administrators → Show the VPN settings (step 1).
| What you see | What it means |
|---|---|
| The app says "Not set up yet" | No VPN username is linked to this account. Set the person up (step 3). |
| "These settings are for administrators." | The device's account isn't an admin of the admin console. |
| "This device isn't registered with the sign-in server yet." | Approve one sign-in on it first, or link it with a setup QR. |
| "The VPN isn't set up on the sign-in server yet." | The RADIUS bridge has no settings on the server. |
| "Cancelled." | Face ID or Touch ID was cancelled; try again. |
| The VPN rejects at once | The username isn't linked to anyone, the directory password was wrong, or the VPN can't reach UDP 1812 or has a different shared secret. |
| No push arrives | Enter the code the VPN shows in Recluda instead. For notifications: the device needs a teal ● (open Recluda and allow notifications), and the server needs push set up. |
| The VPN times out while they approve | Raise the VPN's RADIUS timeout to 60 seconds or more. |
| "That username belongs to someone else." (admin console) | Each username is one person's; remove it from the other account first. |
| The number is never shown | The VPN doesn't support RADIUS challenge messages, or the option is off. |