Skip to content
Access

Secure network: certificates, identity and PasspointAuthentication

OpenRoaming identity providers: how a user identity is trusted

You will be able to decide whether your organisation should act as an OpenRoaming identity provider, an access network provider or both. You will also see how RadSec, WBA certificates and EAP establish trust, and what to prepare before go-live: firewall paths, device profiles, revocation steps and GDPR records.

12 min read

Watch the explainer

An OpenRoaming identity provider is the organisation that issues a person's WiFi credential and vouches for it on other networks. When the device joins a venue's Passpoint network, the identity provider authenticates it over EAP inside a RadSec tunnel. Certificates from the Wireless Broadband Alliance PKI prove each side is a federation member, so the venue never sees passwords.

What is an OpenRoaming identity provider?

OpenRoaming is a WiFi roaming federation run by the Wireless Broadband Alliance (WBA). It lets a phone or laptop join any participating network automatically, with no sign-in page. Every connection involves two parties:

  • The access network provider (ANP) runs the venue's access points.
  • The identity provider (IdP) knows who the person is.

The IdP is the only party that issues credentials. A mobile operator, a university, an employer or an app publisher can each act as an IdP. Each one gives its people a credential once, then answers for it wherever they roam. The venue never creates accounts. It accepts the IdP's yes or no.

That acceptance rests on shared rules rather than private contracts. Every member holds a certificate chained to the WBA's public key infrastructure (PKI), and every member signs up to the same OpenRoaming policy. A hotel in Leeds can trust a student from another country because both organisations trust the same root. The federation's own overview sits on the WBA OpenRoaming page.

A few terms recur throughout this guide, so here they are up front:

  • Passpoint is the access point and device standard, built on IEEE 802.11u and also called Hotspot 2.0. It lets a device find and join a network without a captive portal, the web sign-in page that open networks show.
  • RADIUS is the protocol an access point uses to ask a server whether to admit a device.
  • IEEE 802.1X is port-based access control. It carries EAP, the Extensible Authentication Protocol, which runs the credential exchange.
  • RadSec is RADIUS over TLS, defined in RFC 6614.

Purple runs three networks: open, secure and xPSK. OpenRoaming belongs on the secure network, alongside EAP-TLS and cloud RADIUS. Our secure network guide to certificates, identity and Passpoint covers that wider picture.

{"tone":"note","title":"Scope of this guide","text":"This guide covers the identity provider side of OpenRoaming. Turning your own venues into roaming hotspots is covered in [becoming an OpenRoaming access network provider](guide:openroaming-access-network-provider)."}

How does an OpenRoaming identity provider prove who someone is?

Trust is built in two layers. Organisations trust each other through certificates. The device proves the person to its own IdP through EAP. The venue relays that conversation but cannot read it. Five steps make up every sign-in.

1. The identity provider issues a profile

The IdP gives the device a Passpoint profile. The profile holds three things: a credential, a home realm and a list of roaming consortium organisation identifiers (RCOIs). The credential takes one of three forms:

  • a client certificate for EAP-TLS (RFC 5216)
  • a password for EAP-TTLS (RFC 5281)
  • a SIM for EAP-AKA'

Profiles arrive through an app, a web download or mobile device management. For managed laptops and phones, see deploying a Passpoint profile with Intune.

2. The venue advertises OpenRoaming

The venue's access points advertise the OpenRoaming RCOIs. Devices query them with ANQP, the Access Network Query Protocol defined in IEEE 802.11u. When an advertised RCOI matches one in the profile, the device associates. Nobody taps a button or opens a page.

3. The venue locates the identity provider

The device sends an outer identity in Network Access Identifier (NAI) format, defined in RFC 7542. It usually reads anonymous@realm, so the realm is visible but the person is not.

The venue's RADIUS proxy looks up that realm in DNS. A NAPTR record, as specified in RFC 7585, points to the IdP's RadSec server. Nobody configures a static route for each IdP.

4. Mutual TLS checks membership

The proxy opens a RadSec connection to that server. Both sides present certificates chained to the WBA root. If either chain fails, the connection drops before any credential moves. This is how a venue knows it is talking to a federation member and not an impostor.

5. EAP proves the person

Inside the tunnel, the device and its IdP run the EAP method from step one. The IdP checks the credential against its own records. It then returns an Access-Accept or an Access-Reject.

An accept also carries a Chargeable-User-Identity (CUI), defined in RFC 4372. The CUI is a stable pseudonym. The venue can rate-limit or block that pseudonym without ever learning a name.

{"kind":"flow","direction":"lr","caption":"How an OpenRoaming identity provider authenticates a visiting device, step by step","alt":"Flow from a device with a Passpoint profile through the venue access point and RADIUS proxy to the identity provider, which returns an accept carrying a pseudonymous CUI.","nodes":[{"id":"a","label":"Device with Passpoint profile","sub":"Credential, home realm and RCOIs from its identity provider","tone":"neutral"},{"id":"b","label":"Venue access point","sub":"Advertises OpenRoaming RCOIs over ANQP (IEEE 802.11u)","tone":"neutral"},{"id":"c","label":"ANP RADIUS proxy","sub":"Reads the realm from the anonymous outer NAI (RFC 7542)","tone":"brand"},{"id":"d","label":"DNS NAPTR lookup","sub":"Finds the identity provider's RadSec server (RFC 7585)","tone":"neutral"},{"id":"e","label":"Identity provider RadSec server","sub":"Mutual TLS with WBA PKI certificates (RFC 6614)","tone":"brand"},{"id":"f","label":"Access-Accept with CUI","sub":"Venue gets a pseudonym (RFC 4372), never the real identity","tone":"success"}],"edges":[{"from":"a","to":"b","label":"1. RCOI matches, device associates","style":"solid"},{"from":"b","to":"c","label":"2. EAP over IEEE 802.1X","style":"solid"},{"from":"c","to":"d","label":"3. Look up the realm","style":"dashed"},{"from":"d","to":"e","label":"4. Proxy opens RadSec tunnel","style":"solid"},{"from":"e","to":"f","label":"5. EAP verifies, decision returned","style":"solid"}]}

The second diagram shows the same exchange as layers of trust. It runs from the federation root down to the EAP conversation.

{"kind":"layers","direction":"tb","caption":"The layers of trust behind every OpenRoaming sign-in","alt":"Stacked layers from the WBA policy and PKI root through brokers, identity providers and access network providers down to the RadSec tunnel and the EAP exchange inside it.","nodes":[{"id":"a","label":"WBA policy and PKI root","sub":"Sets federation rules and anchors every member certificate","tone":"brand"},{"id":"b","label":"Certified identity broker","sub":"Onboards members and arranges their WBA certificates","tone":"neutral"},{"id":"c","label":"Identity provider (IdP)","sub":"Issues credentials and holds the real identity","tone":"success"},{"id":"d","label":"Access network provider (ANP)","sub":"Runs the venue network and holds only the CUI","tone":"neutral"},{"id":"e","label":"RadSec mutual TLS","sub":"Each side checks the other's WBA-chained certificate","tone":"neutral"},{"id":"f","label":"EAP inside the tunnel","sub":"Device proves the person to its IdP; the venue cannot read it","tone":"brand"}],"edges":[{"from":"a","to":"b","label":"Certifies","style":"solid"},{"from":"b","to":"c","label":"Onboards","style":"solid"},{"from":"b","to":"d","label":"Onboards","style":"solid"},{"from":"c","to":"e","label":"Presents certificate","style":"solid"},{"from":"d","to":"e","label":"Presents certificate","style":"solid"},{"from":"e","to":"f","label":"Carries","style":"solid"}]}

OpenRoaming IdP, enterprise IdP or identity broker: which is which?

Four confusions account for most stalled projects. Each one mixes two roles that the federation keeps apart.

Treating Microsoft Entra ID as the OpenRoaming IdP

Microsoft Entra ID, Okta and Google Workspace are single sign-on identity providers. They sign people in to applications with SAML (Security Assertion Markup Language) or OpenID Connect. An OpenRoaming IdP speaks RADIUS and EAP instead.

Your directory can sit behind the OpenRoaming IdP as the source of truth. It cannot answer a RadSec request itself. Something must turn directory accounts into WiFi credentials.

Assuming the broker holds identities

An identity broker onboards members into the federation. A WBA-certified broker arranges WBA certificates and checks members against the policy. It can also run RadSec infrastructure on their behalf. The broker does not own anyone's credential. The IdP still decides who gets in.

Equating Passpoint with OpenRoaming

Passpoint is a standard, and OpenRoaming is a federation that uses it. You can run Passpoint for your own staff with no roaming at all. OpenRoaming adds the shared RCOIs, the WBA PKI and dynamic discovery. Those three additions are what let outside identities work on your network.

Assuming the venue sees who connected

The venue sees a realm, an anonymous outer identity and a CUI. The real name, email address or employee number stays with the IdP. If your incident process assumes you can look up a person, add a step that contacts the IdP.

{"caption":"OpenRoaming identity provider vs the roles people confuse with it","asOf":"2026-06-10","columns":[{"key":"term","label":"Role"},{"key":"does","label":"What it does"},{"key":"holds","label":"What it holds"},{"key":"example","label":"Typical example"},{"key":"purple","label":"Where Purple fits","highlight":true}],"rows":[["OpenRoaming identity provider","Authenticates its people for every OpenRoaming venue over RadSec and EAP","The credential and the real identity","University, employer, mobile operator, app publisher","Purple cloud RADIUS answers as your IdP"],["Enterprise SSO IdP","Signs people in to applications with SAML or OpenID Connect","Directory accounts and groups","Microsoft Entra ID, Okta, Google Workspace","Source of truth behind Purple cloud RADIUS"],["Identity broker","Onboards members to the WBA federation and arranges certificates","Member certificates, not personal identities","A WBA-certified broker","Purple is a certified WBA identity broker"],["Access network provider","Runs the venue network and proxies authentication","Realm, anonymous outer identity and CUI","Hotel, airport, stadium, city network","Purple Access on your existing access points"],["Passpoint","Lets devices find and join a network with no captive portal","Nothing; it is a standard","IEEE 802.11u, Hotspot 2.0","Purple delivers the Passpoint profile"],["eduroam IdP","Authenticates for the education federation over a static RADIUS hierarchy","Institutional accounts","A university in eduroam","A separate federation, out of scope here"]],"footnote":"Roles overlap: a university is often an IdP and an ANP at the same time.","download":{"filename":"openroaming-roles.csv"}}

Where you meet an OpenRoaming identity provider in practice

A city and campus that share one identity

The clearest example is a city where one identity works on networks run by several operators. A student's IdP issues the credential once. Every participating network accepts it through the same federation, with no separate sign-in at each stop. The campus, the city centre and the transport network each stay in control of their own access points.

{"tone":"proof","title":"Newcastle","text":"Purple runs Newcastle, the world's first city-wide OpenRoaming network. 53,000+ students roam between campus, city and trams on one identity."}

A multi-site estate on the hardware you own

Most estates first meet the IdP role from the venue side. You enable Passpoint on an SSID in the console you already use:

  • Cisco Meraki Dashboard
  • HPE Aruba Networking Central
  • RUCKUS One or SmartZone
  • the Juniper Mist dashboard
  • the UniFi Network application

You add the OpenRoaming RCOIs to the SSID. Then you point its RADIUS settings at an ANP proxy that speaks RadSec. From that point, people from every OpenRoaming IdP can join. For exact steps on one vendor, follow Passpoint configuration on Cisco Meraki.

Your own staff or students as roaming identities

The second encounter comes when you become an IdP yourself. Your staff or students already live in Microsoft Entra ID, Okta or Google Workspace. A cloud RADIUS service issues them Passpoint credentials tied to those accounts.

On your own sites, the same RADIUS answer sets the VLAN through the Tunnel-Private-Group-ID attribute from RFC 3580. Identity then decides which segment a device lands on. When someone leaves and you disable their directory account, their next authentication fails at every OpenRoaming venue, not just yours.

Limits and edge cases of OpenRoaming identity providers

Devices without a profile still need a portal

Recent iOS, Android and Windows releases support Passpoint. Older devices do not, and some visitors have no participating IdP at all. Those visitors still need an open network with a captive portal. Our guide to Passpoint vs captive portal sets out when each sign-in fits.

The network path must be open

{"tone":"warning","title":"Open the path before you go live","text":"RadSec runs on TCP port 2083 ([RFC 6614](https://www.rfc-editor.org/rfc/rfc6614)) and discovery needs DNS NAPTR lookups. If your firewall blocks either, every roaming sign-in fails even though the SSID looks healthy."}

Revocation sits with the identity provider

The venue cannot revoke a visitor's credential. It can block a CUI or a whole realm locally. Only the IdP can withdraw the identity everywhere. Write that split into your incident runbook before the first escalation.

Identity quality varies between providers

Not every IdP verifies people to the same standard. A mobile operator authenticates against a SIM. An app might rely on a self-declared email address. The OpenRoaming policy lets an IdP signal the kind of identity it issued. It also lets a venue choose which kinds it accepts through the RCOIs it advertises. Decide this per site before go-live.

Settlement-free is the default, not the only tier

OpenRoaming supports settlement-free roaming, where no money changes hands between members. It also supports settled arrangements, where payment flows between members. Most venues start settlement-free. Settled tiers bring commercial terms you agree before you advertise them.

Data roles need writing down

The IdP holds personal data. The venue holds a pseudonym and connection logs. Your GDPR record of processing should state each role clearly. RadSec certificate chains and CUI logs give you evidence for that record. They do not replace the record itself.

How OpenRoaming identity providers relate to Purple

{"items":[{"value":"5 million+","label":"OpenRoaming hotspots worldwide","note":"Purple figure"},{"value":"53,000+","label":"students roaming in Newcastle","note":"Purple data"},{"value":"80,000+","label":"live Purple venues","note":"Purple data"},{"value":"99.999%","label":"platform uptime","note":"Purple data"}]}

Purple is a certified WBA identity broker. We onboard your organisation into the federation and arrange the WBA certificates. You do not build or run a PKI of your own. OpenRoaming is free through the Connect licence.

On the identity side, Purple's cloud RADIUS connects to Microsoft Entra ID, Okta and Google Workspace. Your directory stays the source of truth. Purple turns those accounts into Passpoint credentials and returns the VLAN on your own sites. When a leaver's account is disabled, Purple revokes their access at the next authentication.

On the venue side, Purple Access is hardware-agnostic. It runs as a cloud overlay on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet access points. You change console settings, not hardware. Guest data capture and marketing sit separately in Engage, covered in our guest WiFi guide.

Purple has run guest and secure networks since 2012, across 80,000+ venues in 90 countries. It holds ISO 27001, Cyber Essentials and B Corp certification. Newcastle shows the model at city scale. See Passpoint and OpenRoaming on Purple Access for what the product configures.

In a real deployment, the IdP concept bites in two places first: the firewall path for RadSec and the profile on each device. The venue side is next, in becoming an OpenRoaming access network provider.

Frequently asked questions

What does it cost to become an OpenRoaming identity provider with Purple?

OpenRoaming is free through Purple's Connect licence. Purple acts as your certified WBA identity broker, so you do not buy or run a separate PKI for federation certificates. Your directory stays where it is, in Microsoft Entra ID, Okta or Google Workspace. Settled roaming tiers, where payment flows between members, carry their own commercial terms. Agree those terms before you advertise them.

Does an OpenRoaming identity provider work with Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist and Ubiquiti UniFi?

Yes. The IdP never touches access point hardware; it only answers RadSec requests. The venue side needs Passpoint on the SSID. Each of these platforms exposes this as Passpoint or Hotspot 2.0 settings in its console. Check that your firmware release supports it. Purple is hardware-agnostic, so one IdP serves a mixed estate without new hardware.

Do we need to be an identity provider, an access network provider or both?

Most multi-site estates start as an ANP and add the IdP role when their own people need to roam. If you want visitors from other organisations on your network, you are an ANP. If you want your staff or students to connect elsewhere, you are an IdP. Universities, councils and large employers usually become both.

Can we use Microsoft Entra ID, Okta or Google Workspace as the identity source?

Yes, as the source of truth behind the IdP, not as the IdP itself. These directories speak SAML or OpenID Connect, while OpenRoaming needs RADIUS and EAP. Purple's cloud RADIUS sits between them. It issues Passpoint credentials tied to directory accounts. It rejects an account at the next authentication once you disable it in the directory.

How does OpenRoaming affect our GDPR records and audits?

It narrows what the venue holds. The venue sees a realm, an anonymous outer identity and a CUI pseudonym, while the IdP keeps the personal data. Record both roles in your record of processing. RadSec certificate chains and CUI logs give you evidence for access control and data minimisation reviews. Purple's ISO 27001 and Cyber Essentials certifications support your supplier assessment.

Can we replace our captive portal with OpenRoaming?

Not entirely, and you should not try. OpenRoaming serves devices that already hold a Passpoint profile from a participating IdP. Visitors without a profile, and older devices, still need an open network with a captive portal. Most estates run both side by side. OpenRoaming then handles returning visitors over time, while the portal catches everyone else.

How is an OpenRoaming identity provider different from an eduroam identity provider?

Both vouch for their own people on someone else's network over RADIUS and EAP. eduroam serves research and education. It routes requests through a static hierarchy of national RADIUS servers. OpenRoaming is open to any sector and finds each IdP dynamically through DNS NAPTR records and RadSec. An institution can belong to both federations at the same time.

Frequently asked questions

What does it cost to become an OpenRoaming identity provider with Purple?

OpenRoaming is free through Purple's Connect licence. Purple acts as your certified WBA identity broker, so you do not buy or run a separate PKI for federation certificates. Your directory stays where it is, in Microsoft Entra ID, Okta or Google Workspace. Settled roaming tiers, where payment flows between members, carry their own commercial terms. Agree those terms before you advertise them.

Does an OpenRoaming identity provider work with Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist and Ubiquiti UniFi?

Yes. The IdP never touches access point hardware; it only answers RadSec requests. The venue side needs Passpoint on the SSID. Each of these platforms exposes this as Passpoint or Hotspot 2.0 settings in its console. Check that your firmware release supports it. Purple is hardware-agnostic, so one IdP serves a mixed estate without new hardware.

Do we need to be an identity provider, an access network provider or both?

Most multi-site estates start as an ANP and add the IdP role when their own people need to roam. If you want visitors from other organisations on your network, you are an ANP. If you want your staff or students to connect elsewhere, you are an IdP. Universities, councils and large employers usually become both.

Can we use Microsoft Entra ID, Okta or Google Workspace as the identity source?

Yes, as the source of truth behind the IdP, not as the IdP itself. These directories speak SAML or OpenID Connect, while OpenRoaming needs RADIUS and EAP. Purple's cloud RADIUS sits between them. It issues Passpoint credentials tied to directory accounts. It rejects an account at the next authentication once you disable it in the directory.

How does OpenRoaming affect our GDPR records and audits?

It narrows what the venue holds. The venue sees a realm, an anonymous outer identity and a CUI pseudonym, while the IdP keeps the personal data. Record both roles in your record of processing. RadSec certificate chains and CUI logs give you evidence for access control and data minimisation reviews. Purple's ISO 27001 and Cyber Essentials certifications support your supplier assessment.

Can we replace our captive portal with OpenRoaming?

Not entirely, and you should not try. OpenRoaming serves devices that already hold a Passpoint profile from a participating IdP. Visitors without a profile, and older devices, still need an open network with a captive portal. Most estates run both side by side. OpenRoaming then handles returning visitors over time, while the portal catches everyone else.

How is an OpenRoaming identity provider different from an eduroam identity provider?

Both vouch for their own people on someone else's network over RADIUS and EAP. eduroam serves research and education. It routes requests through a static hierarchy of national RADIUS servers. OpenRoaming is open to any sector and finds each IdP dynamically through DNS NAPTR records and RadSec. An institution can belong to both federations at the same time.

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.