Skip to content
Access

Secure network: certificates, identity and PasspointAuthentication

Pointing access points at cloud RADIUS: shared secret, ports and server settings by vendor

You will be able to point Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist and Ubiquiti UniFi access points at Purple cloud RADIUS with the right ports, secrets and server order. You can also decide when NAT, a controller or RadSec changes a value, and which device to register as the RADIUS client at each site.

12 min read

Watch the explainer

Point access points at cloud RADIUS with two server addresses, UDP 1812 for authentication and UDP 1813 for accounting. Add a random shared secret of at least 16 octets, the length RFC 2865 prefers. RadSec carries the same exchange over TCP 2083 under TLS (RFC 6614). The matrices list each value, its source and what changes it.

How do you read this cloud RADIUS reference?

This reference lists RADIUS server settings for Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist and Ubiquiti UniFi, correct as of 10 June 2026. It belongs to the secure network, one of three networks Purple Access runs on the access points you already own.

The other two networks sit outside this page:

  • Open networks use a captive portal, a web page that gates access before a device joins.
  • xPSK networks give each device or resident its own pre-shared key.

On the secure network, every device proves its identity through 802.1X, the IEEE standard for port-based access control. Identity then sets the VLAN, the virtual LAN segment the device lands on.

How the main matrix works

Read the main matrix row by row. Each row is one setting you type into a console, such as the authentication port or the shared secret. The highlighted column gives the value for Purple cloud RADIUS.

The "Changed by" column points to numbered notes, N1 to N8, in the next section. A note only matters when your estate matches its condition. The Source column names the RFC, IEEE standard or Purple onboarding step behind the value.

How the second matrix works

The second matrix covers vendor variants. It shows where each console takes the server address, and which device sends the requests. That second answer decides how you register each site, so read it before you enter a single secret.

Three terms used throughout

  • NAS (network access server): the device that sends RADIUS requests, which is an access point, controller or gateway.
  • RADIUS client: the NAS as the server sees it, identified by its source IP address.
  • Shared secret: the key both ends use to sign packets and hide the password fields inside them.
{"kind":"flow","direction":"lr","caption":"How a cloud RADIUS request leaves a site","alt":"A device authenticates with EAP-TLS to an access point, which sends RADIUS through the site firewall to Purple cloud RADIUS, which checks identity and returns an Access-Accept with a VLAN.","nodes":[{"id":"dev","label":"Device","sub":"EAP-TLS over 802.1X","tone":"neutral"},{"id":"nas","label":"Access point or controller","sub":"The NAS that sends RADIUS requests","tone":"neutral"},{"id":"nat","label":"Site firewall and NAT","sub":"Public egress IP is the RADIUS client (N1)","tone":"neutral"},{"id":"pri","label":"Purple cloud RADIUS, primary","sub":"UDP 1812 and 1813, or TCP 2083 RadSec","tone":"brand"},{"id":"sec","label":"Purple cloud RADIUS, secondary","sub":"Answers when the primary does not (N7)","tone":"brand"},{"id":"idp","label":"Identity provider","sub":"Microsoft Entra ID, Okta or Google Workspace","tone":"neutral"},{"id":"acc","label":"Access-Accept with VLAN","sub":"RFC 3580 tunnel attributes set the VLAN","tone":"success"}],"edges":[{"from":"dev","to":"nas","label":"EAPOL"},{"from":"nas","to":"nat","label":"RADIUS"},{"from":"nat","to":"pri","label":"secret or TLS"},{"from":"nat","to":"sec","label":"failover","style":"dashed"},{"from":"pri","to":"idp","label":"identity check"},{"from":"pri","to":"acc","label":"policy"}]}

What values does an access point need for cloud RADIUS?

The table below is the configuration you carry from console to console. Every value is the same on Meraki, Aruba, Ruckus, Mist and UniFi, because each one comes from a standard rather than a vendor. Only the field names and menu locations differ, and the second matrix maps those.

{"caption":"Cloud RADIUS values to enter on any access point or controller","asOf":"2026-06-10","columns":[{"key":"setting","label":"Setting"},{"key":"value","label":"Value for Purple cloud RADIUS","highlight":true},{"key":"note","label":"Changed by"},{"key":"source","label":"Source"}],"rows":[["Primary server","Primary address shown in your Purple Access secure network settings","N1, N2","Purple Access onboarding"],["Secondary server","Secondary address from the same settings, entered second","N7","Purple Access onboarding"],["Authentication port","UDP 1812","N3, N5","RFC 2865, section 3"],["Accounting port","UDP 1813","N3, N5","RFC 2866, section 3"],["Shared secret","Random, 16 octets or more, unique per RADIUS client","N1, N3","RFC 2865, section 3"],["RadSec transport","TCP 2083 under TLS, shared secret fixed as `radsec`","N3","RFC 6614, sections 2.1 and 2.3"],["CoA and Disconnect","UDP 3799, listened on by the NAS","N4","RFC 5176, section 3"],["Message-Authenticator","Required on every packet carrying EAP; send on all packets","N6","RFC 3579, section 3.2; CVE-2024-3596"],["VLAN by identity","Tunnel-Type 13, Tunnel-Medium-Type 6, Tunnel-Private-Group-ID set to the VLAN ID","N8","RFC 3580, section 3.31; RFC 2868"],["EAP method","EAP-TLS with client certificates","No note","RFC 5216; RFC 9190"],["SSID security mode","WPA2-Enterprise or WPA3-Enterprise using 802.1X","No note","IEEE 802.1X-2020; IEEE 802.11-2020"]],"footnote":"Values come from the RFCs and Purple Access onboarding. Changed by refers to notes N1 to N8 in the next section.","download":{"filename":"purple-cloud-radius-values-2026-06-10.csv"}}

Server addresses

Three rows need more than a value. The server addresses belong to your Purple Access account, so this page cannot print them. Copy them from your settings. Never type them from memory or from another estate's configuration.

Shared secret

The shared secret row sets a floor, not a target. RFC 2865 asks for a secret as hard to guess as a well-chosen password, preferably 16 octets or more. Generate it with a password manager and store it in your vault. Give each RADIUS client its own.

EAP method

The EAP method row assumes EAP-TLS. It is the Extensible Authentication Protocol method in which client and server both present certificates. RFC 5216 defines it, and RFC 9190 updates it for TLS 1.3. Certificates remove passwords from the WiFi sign-in, so a phished password cannot open the network.

{"tone":"note","title":"What this matrix leaves out","text":"Timeouts, retry counts and dead-server timers have no common standard value, so they are omitted rather than guessed. Check them in your vendor documentation before go-live."}
{"tone":"warning","title":"One secret across 100 sites","text":"A secret reused across every site means one leaked configuration file exposes the whole estate. Give each RADIUS client its own secret, and rotate it when an engineer leaves."}

Which notes change a value in the matrix?

Each note below changes one or more cells. Apply a note when its condition matches your estate. Otherwise, the matrix value stands.

N1: NAT changes the address the server sees

Most sites reach the internet through network address translation (NAT). Cloud RADIUS therefore sees the site's public egress IP address, not each access point's private address. Register that public address as the RADIUS client, with its own shared secret.

Several sites may share one egress, for example through a central firewall. In that case, they share one client entry. Send a distinct NAS-Identifier (RFC 2865, section 5.32) from each site so the server can still tell them apart.

N2: Controller, gateway or proxy mode moves the client

Some platforms forward requests through a controller, gateway or proxy. Where they do, that device becomes the RADIUS client, not the access point. Three common cases are:

  • an HPE Aruba AOS 8 mobility controller
  • a Ruckus SmartZone controller set to proxy
  • a Juniper Mist Edge acting as proxy

Register the forwarding device's address and secret. The second matrix shows which device sends requests in each mode.

N3: RadSec replaces the port, transport and secret

RadSec runs RADIUS inside TLS over TCP. RFC 6614 sets the destination port to TCP 2083. It also fixes the shared secret at the literal string radsec, because TLS now protects the exchange.

Mutual certificates become the trust anchor in place of source IP and secret. That suits sites whose public IP address changes, such as retail units on consumer broadband.

N4: CoA needs a path back to the NAS

CoA is the RFC 5176 mechanism that lets the server change or end a live session. It uses UDP 3799. The server starts this exchange, so the RADIUS server must be able to reach the NAS.

Behind NAT, that path takes one of three forms:

  • a forwarding rule on the site firewall
  • a proxy that relays the request
  • a RadSec connection that carries the request back

Confirm the listening port in your vendor documentation before you open the firewall. RADIUS CoA on WiFi covers each platform.

N5: Legacy ports 1645 and 1646

Early RADIUS deployments used UDP 1645 for authentication and 1646 for accounting. RFC 2865 records that 1645 conflicts with the "datametrics" service, and assigns 1812 instead.

An older template or controller may still carry 1645 or 1646. Replace both with 1812 and 1813 before you cut over.

N6: Message-Authenticator after Blast-RADIUS

RFC 3579 already requires the Message-Authenticator attribute on every packet that carries EAP. In July 2024, CVE-2024-3596, known as Blast-RADIUS, showed that an attacker in the path can forge unsigned RADIUS responses over UDP.

The mitigation is to send and require Message-Authenticator on all packets. Install your vendor's patched firmware, and enable any setting that enforces the attribute.

N7: The secondary server is not optional

Enter both Purple addresses on every SSID, primary first. Access points fail over to the second server when the first stops answering. The timers that decide failover are vendor-specific.

Purple cloud RADIUS carries a 99.9% RADIUS uptime SLA, on a platform that runs at 99.999% uptime. RADIUS server down explains what devices experience if both addresses become unreachable.

N8: VLAN attributes need the override switched on

Identity sets the VLAN through the three RFC 3580 tunnel attributes in the main matrix. Some consoles ignore those attributes until you allow RADIUS to override the SSID's VLAN. RADIUS attributes for VLAN assignment lists that setting on each platform.

Where does each vendor console take these settings?

The values do not change between vendors. What changes is the console, the setting name and the device the server sees as the RADIUS client. That last column decides how N1 and N2 apply to your estate.

{"caption":"Where each platform takes cloud RADIUS settings and which device sends requests","asOf":"2026-06-10","columns":[{"key":"platform","label":"Platform"},{"key":"where","label":"Where you enter the server"},{"key":"client","label":"Device sending requests (RADIUS client)"},{"key":"source","label":"Source"}],"rows":[["Cisco Meraki","Meraki dashboard access control page, on an SSID set to Enterprise with your own RADIUS servers","Each MR access point","Cisco Meraki documentation: RADIUS authentication with WPA2-Enterprise"],["HPE Aruba Instant","Instant WLAN security settings, with an external RADIUS authentication server","Each access point; the virtual controller when Dynamic RADIUS Proxy is on","HPE Aruba Networking documentation: Instant authentication servers"],["HPE Aruba AOS 8","RADIUS server and server group in the AAA profile on the mobility controller","The mobility controller","HPE Aruba Networking documentation: AOS 8 authentication servers"],["Ruckus SmartZone","Authentication and accounting services, selected on the WLAN","The controller when proxy is chosen; each access point when it is not","Ruckus SmartZone administrator documentation"],["Juniper Mist","Mist WLAN with 802.1X security, RADIUS authentication and accounting servers","Each access point, or Mist Edge when it proxies","Juniper Mist wireless documentation"],["Ubiquiti UniFi","UniFi Network RADIUS profile, selected on a WPA2 or WPA3 Enterprise WiFi network","Each UniFi access point","Ubiquiti help centre: RADIUS profiles"]],"footnote":"Where the access point sends requests, N1 applies: cloud RADIUS sees the site's public egress address."}

Proxy and RadSec options

Proxy and RadSec options vary by platform:

  • Cisco Meraki documents RadSec on MR access points.
  • HPE Aruba documents RadSec and Dynamic RADIUS Proxy on Instant.
  • Juniper Mist supports RadSec from the access point or through Mist Edge.
  • Ruckus SmartZone can proxy every request through the controller.

Where a platform offers RadSec, N3 replaces the port and secret rows of the main matrix.

Test one site before the estate

Before you cut over the estate, test one site end to end. Use the console's RADIUS test where it offers one. Then join one device with a certificate. Confirm the Access-Accept and the VLAN in the RADIUS logs before you move the next site.

{"tone":"proof","title":"Running at branch scale","text":"JPMorgan runs Staff WiFi on Purple across 5,000 branches, on the largest cloud RADIUS in the world."}

Which standards and sources sit behind each value?

Every cell traces to one of these primary sources. Link to them in your change records, so the next engineer can verify a value without asking you.

  • RFC 2865: RADIUS authentication, UDP 1812, the shared secret guidance, the legacy 1645 note and NAS-Identifier.
  • RFC 2866: RADIUS accounting on UDP 1813.
  • RFC 2868: RADIUS tunnel attributes.
  • RFC 3579: RADIUS support for EAP, including Message-Authenticator.
  • RFC 3580: 802.1X RADIUS usage, including the VLAN attribute values.
  • RFC 5176: dynamic authorisation, CoA and Disconnect on UDP 3799.
  • RFC 6614: RADIUS over TLS on TCP 2083, with the fixed radsec secret.
  • RFC 5216 and RFC 9190: EAP-TLS, and EAP-TLS with TLS 1.3.
  • CVE-2024-3596: the Blast-RADIUS vulnerability record.
  • IEEE 802.1X-2020 and IEEE 802.11-2020: port-based access control and the WiFi security modes.

For vendor settings, start from the documentation home of each platform:

For the wider picture, read Secure network: certificates, identity and Passpoint. Passpoint is the standard that lets devices join a network automatically using stored credentials. The Purple cloud RADIUS product page covers the service itself. The enterprise WiFi security guide places RADIUS alongside your other controls. You can also see how the secure network fits with open and xPSK networks on one platform.

How is this reference maintained?

Every cell in both matrices traces to a primary source, and the source column names it. When an RFC is updated or obsoleted, the affected row changes and the asOf date moves.

When a vendor renames a setting, the second matrix follows the vendor's documentation, not memory. The same applies when a vendor changes which device sends requests. A row that loses its source is removed rather than left to stand. Timers and limits stay out until a vendor documents them.

On your side, keep the downloaded CSV with your change records. Re-check it after every firmware upgrade and every RADIUS migration. Together with console screenshots, it serves as evidence for configuration review in an ISO 27001 or PCI DSS audit.

Frequently asked questions

Does Purple cloud RADIUS work with the access points I already own?

Yes. Purple is hardware-agnostic and runs as a cloud overlay on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet. You change the RADIUS server settings in the console you already use, with the values in the main matrix. No new access points, controllers or appliances are needed. The same settings serve every site in a multi-site estate.

How long does a migration from on-premises RADIUS take?

RADIUS migration is usually a weekend exercise. You add Purple's two addresses and per-site secrets, then move SSIDs one site at a time. Keep the old server as a fallback until devices authenticate cleanly. Certificate deployment through your device management tool takes longer, so start it before the cutover weekend. The matrices give every engineer one set of values for every site.

How should I model the cost of cloud RADIUS?

Model it per site and per identity, then compare it with the full cost of your current servers. Include hardware, licences, patching and the staff time a cloud service removes. A per-site view makes estates of different sizes comparable. Cloud RADIUS pricing sets out how to model cost per site, so you can put a defensible number in front of finance.

What happens if cloud RADIUS becomes unreachable?

Access points fail over to the secondary address, which is why the matrix lists two servers. Purple backs cloud RADIUS with a 99.9% RADIUS uptime SLA, on a platform that runs at 99.999% uptime. Connected devices keep their session until it needs to reauthenticate, while new connections wait for a server. RADIUS server down covers recovery and the vendor timers behind failover.

Should I use RadSec or RADIUS over UDP?

Use RadSec where your platform supports it, because RADIUS to a cloud server crosses the internet. RFC 6614 wraps each exchange in TLS on TCP 2083, so certificates protect the traffic rather than a shared secret alone. Where a platform only offers UDP, use 1812 and 1813 with a unique secret per client. Require Message-Authenticator on every packet.

Can one shared secret cover every site?

It can, but it should not. A single secret means one leaked configuration file exposes every site. Rotating it also forces a change on every console at once. RFC 2865 asks for a secret as hard to guess as a well-chosen password, preferably 16 octets or more. Give each RADIUS client its own secret and keep all of them in your vault.

Does this reference count as audit evidence?

It gives evidence for configuration review, and each value carries its source. An ISO 27001 or PCI DSS auditor can trace a setting to the RFC or vendor documentation behind it. Pair the downloaded CSV with your change records and console screenshots for a complete trail. Purple itself holds ISO 27001 and Cyber Essentials certification, and is a certified B Corp.

How often is this reference updated?

It is updated whenever a source behind a cell changes. A revised RFC, a renamed vendor setting or a new firmware behaviour moves the asOf date on the affected table. Values with no primary source are left out rather than guessed. Compare the asOf date with your last firmware upgrade. Re-test one site whenever the upgrade is the more recent of the two.

Frequently asked questions

Does Purple cloud RADIUS work with the access points I already own?

Yes. Purple is hardware-agnostic and runs as a cloud overlay on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet. You change the RADIUS server settings in the console you already use, with the values in the main matrix. No new access points, controllers or appliances are needed. The same settings serve every site in a multi-site estate.

How long does a migration from on-premises RADIUS take?

RADIUS migration is usually a weekend exercise. You add Purple's two addresses and per-site secrets, then move SSIDs one site at a time. Keep the old server as a fallback until devices authenticate cleanly. Certificate deployment through your device management tool takes longer, so start it before the cutover weekend. The matrices give every engineer one set of values for every site.

How should I model the cost of cloud RADIUS?

Model it per site and per identity, then compare it with the full cost of your current servers. Include hardware, licences, patching and the staff time a cloud service removes. A per-site view makes estates of different sizes comparable. [Cloud RADIUS pricing](guide:cloud-radius-pricing) sets out how to model cost per site, so you can put a defensible number in front of finance.

What happens if cloud RADIUS becomes unreachable?

Access points fail over to the secondary address, which is why the matrix lists two servers. Purple backs cloud RADIUS with a 99.9% RADIUS uptime SLA, on a platform that runs at 99.999% uptime. Connected devices keep their session until it needs to reauthenticate, while new connections wait for a server. [RADIUS server down](guide:radius-server-down-wifi) covers recovery and the vendor timers behind failover.

Should I use RadSec or RADIUS over UDP?

Use RadSec where your platform supports it, because RADIUS to a cloud server crosses the internet. RFC 6614 wraps each exchange in TLS on TCP 2083, so certificates protect the traffic rather than a shared secret alone. Where a platform only offers UDP, use 1812 and 1813 with a unique secret per client. Require Message-Authenticator on every packet.

Can one shared secret cover every site?

It can, but it should not. A single secret means one leaked configuration file exposes every site. Rotating it also forces a change on every console at once. RFC 2865 asks for a secret as hard to guess as a well-chosen password, preferably 16 octets or more. Give each RADIUS client its own secret and keep all of them in your vault.

Does this reference count as audit evidence?

It gives evidence for configuration review, and each value carries its source. An ISO 27001 or PCI DSS auditor can trace a setting to the RFC or vendor documentation behind it. Pair the downloaded CSV with your change records and console screenshots for a complete trail. Purple itself holds ISO 27001 and Cyber Essentials certification, and is a certified B Corp.

How often is this reference updated?

It is updated whenever a source behind a cell changes. A revised RFC, a renamed vendor setting or a new firmware behaviour moves the asOf date on the affected table. Values with no primary source are left out rather than guessed. Compare the asOf date with your last firmware upgrade. Re-test one site whenever the upgrade is the more recent of the two.

Turn this guide into a plan for your estate

Tell us about your sites and the hardware you run. A Purple engineer maps Purple Access on top of it with you, and you keep the plan.

  1. Book a demoTell us what runs on your WiFi today, and a Purple network engineer maps it with you.
  2. Map your SSIDs onto threeOpen, secure and xPSK, on the access points you already own. You leave with the plan.
  3. Prove it on one site firstJudge the result on tickets and audit evidence, then roll out.

Book a demo

Tell us about your network

Led by a Purple network engineer. No slides.