Come Passpoint (Hotspot 2.0) trasforma l'esperienza Guest Wi-Fi

Una guida tecnica di riferimento completa che dettaglia come i protocolli Passpoint (Hotspot 2.0) e 802.11u sostituiscano i tradizionali Captive Portal con un roaming Wi-Fi fluido, sicuro e simile a quello cellulare. Fornisce ai responsabili IT panoramiche architetturali, framework di implementazione e il business case per l'adozione dell'autenticazione basata su credenziali per risolvere le sfide della randomizzazione MAC e migliorare l'esperienza degli ospiti.

📖 6 min di lettura📝 1,359 parole🔧 2 esempi❓ 3 domande📚 8 termini chiave

🎧 Ascolta questa guida

Visualizza trascrizione

How Passpoint Transforms the Guest Wi-Fi Experience
A Purple Technical Briefing — Approximately 10 Minutes

---

INTRODUCTION AND CONTEXT — approximately 1 minute

Welcome to the Purple Technical Briefing series. I'm going to spend the next ten minutes walking you through something that, frankly, should have replaced the captive portal years ago — Passpoint, also known as Hotspot 2.0.

If you're managing Wi-Fi infrastructure at a hotel group, a retail estate, a stadium, or any venue where guests connect repeatedly, you've almost certainly hit the same wall: guests complaining about having to log in every single time, your IT helpdesk fielding calls about Wi-Fi that "used to work," and a growing realisation that iOS 14 and Android 10's MAC address randomisation has quietly broken your re-authentication logic.

Passpoint is the answer to all of those problems. But it's not a magic switch — it's a properly engineered protocol that requires deliberate deployment. So let's get into it.

---

TECHNICAL DEEP-DIVE — approximately 5 minutes

Let's start with the core problem Passpoint solves, which engineers call the network selection problem.

In traditional Wi-Fi, your device scans for a known SSID — a network name — and if it recognises one, it connects. That's simple, but it's brittle. It requires prior connection, it tells you nothing about the network's security posture, and it doesn't support roaming between venues. Every time a guest walks into your hotel, their device has to be manually pointed at your network, then intercepted by a captive portal, then authenticated through a web form. That's friction. And in 2026, friction is a competitive disadvantage.

Passpoint shifts the paradigm entirely. Instead of looking for a network name, the device looks for a network that supports its credentials. Before even attempting to connect, the device asks the access point: "Do you support my identity provider?" If the answer is yes, authentication proceeds automatically. No login page. No password prompt. No manual selection. It's the cellular roaming model, applied to Wi-Fi.

The mechanism that makes this possible is called the Generic Advertisement Service — GAS — combined with the Access Network Query Protocol, or ANQP. When a Passpoint-enabled access point broadcasts its beacon, it includes what's called an Interworking Element — essentially a flag that says "I speak 802.11u," which is the IEEE amendment that underpins all of this. Your device sees that flag, sends a GAS request, and inside that request, an ANQP query asks: "What Roaming Consortium Organisational Identifiers do you support?" The access point responds. If there's a match with a profile already on the device, the full WPA2 or WPA3 Enterprise authentication handshake begins.

That authentication uses IEEE 802.1X — the same port-based access control standard used in enterprise wired networks — combined with an EAP method. The most common are EAP-TLS, which uses certificates; EAP-TTLS, which tunnels username and password securely; and EAP-SIM or EAP-AKA for mobile operator SIM-based authentication.

The result is a mutually authenticated, fully encrypted session. The device proves its identity to the network, and the network proves its identity to the device. That mutual authentication is what prevents evil twin attacks and man-in-the-middle attacks that plague open Wi-Fi environments.

Now, a term you'll hear alongside Passpoint is OpenRoaming — the Wireless Broadband Alliance's federation framework. Here's the distinction that matters: Passpoint is the vehicle. OpenRoaming is the highway system.

Passpoint defines how a device discovers and authenticates to a network. OpenRoaming defines the trust ecosystem that allows an identity provider — say, Google, Samsung, or a mobile operator — and an access provider — your hotel, your stadium, your retail estate — to trust each other's credentials without a bilateral agreement between every pair. OpenRoaming uses a hub-and-spoke PKI model with RadSec tunnels — that's RADIUS over TLS — to proxy authentication requests across the federation. The key Roaming Consortium OI for settlement-free OpenRoaming is 5A-03-BA. You'll also want to broadcast the legacy Cisco OI, 00-40-96, for compatibility with older devices and Samsung OneUI profiles.

From a security compliance perspective, Passpoint is a significant upgrade. WPA3-Enterprise uses 192-bit security mode and mandates forward secrecy — every session uses unique encryption keys, so compromising one session doesn't expose historical traffic. For organisations subject to PCI DSS — particularly retail environments processing card payments — or GDPR obligations around personal data, Passpoint's certificate-based authentication means you're not collecting credentials through a web form, which substantially reduces your data handling surface area.

And then there's MAC address randomisation. Modern iOS and Android devices randomise their MAC address by default. This breaks traditional captive portal re-authentication flows — the device looks new on every visit. Passpoint is immune to this. Authentication is credential-based, not MAC-based. Your returning guest connects seamlessly on every visit, regardless of what their device's MAC address happens to be that day. This also has a significant implication for your Wi-Fi analytics — if you're using Purple's analytics platform, credential-based authentication restores the accuracy of your returning visitor data.

---

IMPLEMENTATION RECOMMENDATIONS AND PITFALLS — approximately 2 minutes

Let me give you the practical deployment picture.

The infrastructure requirements are more involved than a captive portal, but they're well within reach for any organisation running enterprise-class hardware. You need Passpoint-certified access points — most enterprise APs from Cisco, Aruba, Ruckus, and Ubiquiti support this today. You need a RADIUS server with EAP support, AAA infrastructure for credential management, and ideally an OSU — Online Sign-Up — server for self-service profile provisioning.

The configuration work centres on four elements: your ANQP settings, which define what the AP advertises pre-association; your Roaming Consortium OIs; your NAI realm definitions, which tell devices which EAP methods you support; and your venue information, which is used by devices to display context about the network.

My strongest recommendation for most venues is a dual SSID strategy. Run a Passpoint SSID for returning guests and enrolled users, and maintain a captive portal SSID for first-time visitors. Use the captive portal as an onboarding funnel — present the option to install a Passpoint profile at the end of the first-visit authentication flow. This progressive onboarding model gives you the best of both worlds: easy first access, seamless return visits.

Now, the pitfalls. The most common deployment failure I see is treating Passpoint as a drop-in replacement for captive portals without building the onboarding journey. If guests don't know how to install a profile, or if the OSU flow is clunky, adoption stalls. Invest in the provisioning experience.

The second pitfall is certificate management. If you're using EAP-TLS with device certificates, you need a robust PKI lifecycle. Expired certificates will silently break authentication for affected devices — and your helpdesk will be the last to know. Automate certificate renewal and monitor expiry proactively.

Third: don't neglect legacy device support. Passpoint requires iOS 7 or later, Android 6 or later, and Windows 10 or later. That covers the vast majority of modern devices, but IoT devices and some older corporate-issued hardware will need alternative access paths.

---

RAPID-FIRE Q AND A — approximately 1 minute

Does Passpoint work with existing access points? If they're enterprise-class hardware from the last five years, almost certainly yes — check for Wi-Fi Alliance Passpoint certification in the spec sheet.

Can I still collect guest data with Passpoint? Yes, but the mechanism shifts. Data collection happens at profile provisioning time — in the OSU flow or app-based enrolment — rather than at every login. This is actually more GDPR-friendly, as consent is captured once, explicitly.

What about venues that want branded splash pages? Passpoint connections are invisible by design, so traditional splash pages don't apply. However, you can trigger in-app notifications or push messages post-connection if you have a loyalty app integration. Some operators use a hybrid model where the first visit still goes through a branded portal before Passpoint enrolment.

Is OpenRoaming free to join? The settlement-free tier of OpenRoaming, using the 5A-03-BA OI, is available at no cost through the Wireless Broadband Alliance. Commercial tiers with analytics and monetisation features are available through WBA members.

---

SUMMARY AND NEXT STEPS — approximately 1 minute

To summarise: Passpoint is not a future technology — it's a mature, standards-based protocol that is already deployed at major airports, hotel chains, and stadiums globally. The question for your organisation is not whether to adopt it, but when and how.

If you're running a hotel group, a retail chain, or a large venue with recurring visitors, the ROI case is clear: reduced helpdesk burden, improved guest satisfaction, compliance risk mitigation, and accurate analytics data that isn't broken by MAC randomisation.

Your next steps are straightforward. First, audit your current AP estate for Passpoint certification. Second, evaluate your RADIUS infrastructure and determine whether you need an OSU server for self-service provisioning. Third, design your dual SSID strategy and onboarding journey. And fourth, if you're considering OpenRoaming federation, engage with the Wireless Broadband Alliance or a platform provider like Purple who can handle the federation plumbing on your behalf.

This is Purple's Technical Briefing on Passpoint and Hotspot 2.0. For the full written guide, architecture diagrams, and worked deployment examples, visit purple.ai. Thank you for listening.

Sintesi operativa

Per le moderne sedi aziendali, l'attrito è uno svantaggio competitivo. I tradizionali Captive Portal, pur essendo stati lo standard per l'accesso alla rete ospite, rappresentano oggi un significativo collo di bottiglia operativo e una fonte di persistente frustrazione per l'utente. Passpoint, noto anche come Hotspot 2.0, trasforma radicalmente questo paradigma sostituendo l'autenticazione manuale basata sul web con un roaming fluido, simile a quello cellulare. Sfruttando lo standard IEEE 802.11u e la crittografia WPA3-Enterprise, Passpoint consente ai dispositivi degli ospiti di rilevare, autenticarsi e connettersi alle reti Wi-Fi aziendali in modo automatico e sicuro.

Per i leader IT nei settori Hospitality , Retail e nei grandi spazi pubblici, il passaggio a Passpoint non è più opzionale. La randomizzazione dell'indirizzo MAC predefinita implementata nei moderni dispositivi iOS e Android ha di fatto interrotto la logica di ri-autenticazione dei Captive Portal legacy, il che significa che gli ospiti che ritornano appaiono come nuovi dispositivi a ogni visita. Passpoint risolve questo problema autenticando il profilo delle credenziali dell'utente anziché il suo indirizzo hardware. Questa guida dettaglia l'architettura tecnica di Passpoint, l'impatto aziendale dell'implementazione e un framework di implementazione neutrale rispetto ai fornitori progettato per migliorare l'esperienza Guest WiFi riducendo al contempo il carico di lavoro dell'helpdesk.

Approfondimento tecnico

Il problema della selezione della rete e lo standard 802.11u

Nelle implementazioni Wi-Fi legacy, i dispositivi si affidano a un meccanismo di selezione della rete fondamentalmente fragile: la scansione di Service Set Identifiers (SSID) noti. Questo approccio richiede che l'utente si sia precedentemente connesso alla rete o che selezioni manualmente la rete da un elenco. Non fornisce alcuna visibilità pre-associazione sulla postura di sicurezza della rete, sui requisiti di autenticazione o sulla disponibilità di internet a monte. Passpoint affronta questa limitazione attraverso l'emendamento IEEE 802.11u, che introduce l'Interworking con reti esterne.

Invece di scansionare passivamente gli SSID, un dispositivo abilitato a Passpoint interroga attivamente l'infrastruttura di rete prima di tentare l'associazione. Quando un access point trasmette il suo beacon, include un Interworking Element — un flag che indica il supporto per 802.11u. Il dispositivo client rileva questo flag e avvia una richiesta Generic Advertisement Service (GAS). All'interno di questa richiesta è incapsulata una query Access Network Query Protocol (ANQP). Il dispositivo chiede all'infrastruttura: "Quali Roaming Consortium Organisational Identifiers (OI) supporti?". Se la risposta dell'access point corrisponde a un profilo di credenziali memorizzato sul dispositivo, l'autenticazione automatica procede.

Architettura di autenticazione e sicurezza

Passpoint impone una sicurezza di livello enterprise, eliminando completamente la fase di "rete aperta" inerente alle implementazioni dei Captive Portal. L'autenticazione è gestita tramite il controllo dell'accesso alla rete basato su porta IEEE 802.1X, abbinato a un metodo Extensible Authentication Protocol (EAP). I metodi più diffusi nelle implementazioni aziendali sono EAP-TLS (basato su certificati client e server), EAP-TTLS (credenziali tunnelizzate) e EAP-SIM/AKA (per scenari di offload cellulare).

Questa architettura fornisce un'autenticazione reciproca. Il dispositivo dimostra crittograficamente la propria identità alla rete e, cosa fondamentale, la rete dimostra la propria identità al dispositivo. Questa verifica reciproca è la difesa principale contro gli access point evil twin e i tentativi di intercettazione man-in-the-middle. Inoltre, Passpoint impone la crittografia WPA2-Enterprise o WPA3-Enterprise. WPA3-Enterprise introduce la modalità di sicurezza a 192 bit e impone la forward secrecy, garantendo che anche se le chiavi di sessione venissero compromesse in futuro, il traffico storico rimanga crittografato.

La federazione OpenRoaming

Mentre Passpoint definisce il meccanismo tecnico per il rilevamento e l'autenticazione, OpenRoaming fornisce il framework di fiducia. Sviluppata dalla Wireless Broadband Alliance (WBA), OpenRoaming è una federazione globale che consente agli Identity Provider (come operatori di rete mobile, Google o Apple) e agli Access Provider (come hotel, stadi e catene di vendita al dettaglio) di fidarsi reciprocamente delle credenziali senza richiedere accordi bilaterali tra ogni entità.

OpenRoaming opera su un modello Public Key Infrastructure (PKI) hub-and-spoke. Le richieste di autenticazione vengono inoltrate attraverso la federazione utilizzando tunnel RadSec (RADIUS su TLS). Trasmettendo l'OI OpenRoaming settlement-free (5A-03-BA), una sede aziendale può fornire istantaneamente un accesso Wi-Fi fluido e sicuro a milioni di utenti in tutto il mondo che già possiedono un profilo di identità compatibile sui propri dispositivi.

Guida all'implementazione

L'implementazione di Passpoint richiede una base infrastrutturale più sofisticata rispetto a una rete aperta tradizionale, ma i componenti sono standard nei moderni ambienti aziendali.

Prerequisiti dell'infrastruttura

Access Point certificati Passpoint: L'infrastruttura wireless deve supportare le specifiche 802.11u e Hotspot 2.0. La stragrande maggioranza degli access point aziendali prodotti negli ultimi cinque anni da fornitori come Cisco, Aruba e Ruckus soddisfa questo requisito.
Infrastruttura RADIUS/AAA: Un server RADIUS robusto in grado di gestire l'autenticazione EAP e di instradare le richieste agli archivi di identità appropriati. Se si partecipa a OpenRoaming, il server RADIUSIl server deve supportare RadSec per il proxying sicuro.
Server Online Sign-Up (OSU): Per gli ambienti che emettono le proprie credenziali (anziché affidarsi esclusivamente a identità federate), un server OSU fornisce il meccanismo per il provisioning sicuro dei profili Passpoint sui dispositivi degli ospiti.

La Strategia Dual-SSID

Il modello di implementazione più efficace per le sedi che passano a Passpoint è la strategia dual-SSID. Questo approccio mantiene un SSID Captive Portal tradizionale per l'onboarding iniziale, fornendo al contempo un SSID Passpoint per le connessioni successive senza interruzioni.

Quando un ospite si connette all'SSID Captive Portal per la prima volta, completa il flusso di autenticazione standard (ad esempio, accettando termini e condizioni, fornendo un indirizzo email). Una volta completata l'autenticazione, il portale presenta l'opzione per scaricare un profilo Passpoint. Una volta installato, il dispositivo preferirà automaticamente l'SSID Passpoint sicuro per tutte le visite future. Questo modello di onboarding progressivo garantisce l'accessibilità per i dispositivi legacy, migrando al contempo la maggior parte degli utenti verso la rete Passpoint sicura e senza attriti.

Best Practice

Nella progettazione di un'architettura Passpoint, i responsabili IT devono attenersi ad alcune best practice critiche per garantire stabilità operativa e sicurezza.

In primo luogo, la gestione del ciclo di vita dei certificati è fondamentale. Se si utilizza EAP-TLS, la scadenza dei certificati client o server comporterà fallimenti di autenticazione silenziosi, difficili da diagnosticare per gli helpdesk di prima linea. Implementate protocolli di rinnovo automatico dei certificati e un monitoraggio proattivo. Come evidenziato nella nostra guida sulla Valutazione della postura del dispositivo per il controllo degli accessi alla rete , una visibilità robusta degli endpoint è essenziale quando si gestisce l'accesso basato su certificati.

In secondo luogo, garantite la compatibilità con i dispositivi legacy. Sebbene iOS 7+, Android 6+ e Windows 10+ supportino nativamente Passpoint, alcuni dispositivi IoT, hardware datati e dispositivi gestiti a livello aziendale con restrizioni rigorose potrebbero non supportarlo. La strategia dual-SSID mitiga questo rischio fornendo un metodo di accesso alternativo.

In terzo luogo, durante la configurazione degli elementi ANQP, assicuratevi che le Venue Information siano accurate e descrittive. Questi metadati vengono spesso visualizzati dal sistema operativo del dispositivo client per fornire il contesto sulla rete a cui l'utente si sta connettendo.

Risoluzione dei problemi e mitigazione dei rischi

La complessità di Passpoint introduce domini di errore specifici che differiscono dalle implementazioni Captive Portal.

Modalità di errore 1: Timeout o irraggiungibilità RADIUS Se il server RADIUS locale non riesce a raggiungere l'Identity Provider a monte (specialmente negli scenari OpenRoaming federati), l'handshake EAP andrà in timeout. Mitigazione: Implementate un'infrastruttura RADIUS ridondante e garantite un monitoraggio robusto dei tunnel RadSec. Consultate la nostra documentazione tecnica su RadSec: Protezione del traffico di autenticazione RADIUS con TLS per indicazioni sulla configurazione.

Modalità di errore 2: Errori di provisioning del profilo Gli utenti potrebbero riscontrare errori durante il tentativo di scaricare il profilo Passpoint dal server OSU, spesso a causa delle limitazioni del browser del Captive Portal sui dispositivi mobili. Mitigazione: Progettate il flusso del Captive Portal in modo che esca dal mini-browser del captive network assistant (CNA) per passare al browser di sistema nativo del dispositivo prima di avviare il download del profilo.

Modalità di errore 3: Impatto della randomizzazione MAC sulle analisi Sebbene Passpoint risolva l'interruzione dell'autenticazione causata dalla randomizzazione MAC, le piattaforme di analisi legacy che si affidano esclusivamente agli indirizzi MAC continueranno a riportare conteggi dei visitatori imprecisi. Mitigazione: Integrate i log di autenticazione RADIUS con la vostra piattaforma WiFi Analytics. Tracciando identificatori di credenziali univoci (come la Chargeable User Identity o la NAI anonimizzata) anziché gli indirizzi MAC, le sedi possono ripristinare metriche accurate su affluenza e fedeltà.

ROI e impatto aziendale

Il business case per l'implementazione di Passpoint si basa su tre pilastri misurabili: efficienza operativa, riduzione del rischio ed esperienza utente.

Dal punto di vista operativo, l'eliminazione dell'attrito del Captive Portal correla direttamente con una riduzione dei ticket di assistenza IT relativi alla connettività Wi-Fi. In ampi ambienti Sanitari o di Trasporto , ciò rappresenta un risparmio significativo sui costi.

Per quanto riguarda la mitigazione del rischio, il passaggio dalle reti aperte alla crittografia WPA3-Enterprise riduce sostanzialmente il profilo di responsabilità della sede. Per gli ambienti retail soggetti a PCI DSS, la riduzione della superficie di gestione dei dati (eliminando la raccolta di credenziali basata sul web) semplifica gli audit di conformità.

Infine, il miglioramento dell'esperienza utente è profondo. Nel settore dell'ospitalità, gli studi dimostrano costantemente che un Wi-Fi affidabile e senza interruzioni è uno dei principali fattori di soddisfazione degli ospiti e di prenotazioni ripetute. Implementando Passpoint, le sedi offrono un'esperienza di connettività che rispecchia l'affidabilità delle reti cellulari, trasformando il Wi-Fi da un servizio frustrante a un comfort premium e trasparente.

Termini chiave e definizioni

IEEE 802.11u

The wireless networking standard amendment that enables Interworking with External Networks, allowing devices to query APs before associating.

When configuring wireless controllers, engineers must enable 802.11u to allow devices to discover Passpoint capabilities.

ANQP (Access Network Query Protocol)

A query and response protocol used by devices to discover network services, roaming agreements, and venue information before connecting.

IT teams configure ANQP profiles on the wireless controller to broadcast their supported Roaming Consortium OIs and NAI Realms.

Roaming Consortium OI

An Organisational Identifier broadcast by the access point that indicates which identity providers or federations the network supports.

If an enterprise joins OpenRoaming, they must ensure their APs broadcast the specific OpenRoaming OI (5A-03-BA).

OSU (Online Sign-Up)

A standardized process and server infrastructure for securely provisioning Passpoint credentials and certificates to a user's device.

When building a self-service onboarding flow for a loyalty programme, developers will integrate with an OSU server to push the profile to the device.

RadSec

A protocol that encapsulates RADIUS authentication traffic within a TLS tunnel to ensure secure transmission over untrusted networks.

Required when proxying authentication requests from a local venue to a cloud-based OpenRoaming hub.

NAI Realm

Network Access Identifier Realm; indicates the domain of the user and the specific EAP authentication methods supported by the network.

Configured alongside ANQP to tell client devices whether the network requires EAP-TLS, EAP-TTLS, or EAP-SIM.

EAP-TLS

Extensible Authentication Protocol - Transport Layer Security; a highly secure authentication method requiring both client and server certificates.

Often used in enterprise employee Wi-Fi deployments where IT can push certificates to managed devices via MDM.

MAC Address Randomisation

A privacy feature in modern mobile operating systems that generates a fake, temporary hardware address for each Wi-Fi network connection.

The primary catalyst driving venues away from captive portals, as it breaks the ability to recognize returning visitors based on their hardware.

Casi di studio

A 400-room enterprise hotel chain is experiencing a high volume of helpdesk tickets from returning guests who complain they must manually reconnect to the Wi-Fi in the lobby, restaurant, and their rooms, despite having connected previously. The hotel currently uses a traditional open SSID with a captive portal. How should the network architect resolve this?

The architect should implement a Dual-SSID strategy. First, deploy a secure Passpoint SSID broadcasting the hotel's specific Roaming Consortium OI. Second, modify the existing captive portal on the open SSID to serve as an onboarding funnel. When a guest logs in via the portal, they are prompted to download a Passpoint configuration profile to their device. Once installed, the device will automatically and securely authenticate via 802.1X/EAP to the Passpoint SSID as they move between the lobby, restaurant, and room, eliminating manual re-authentication.

Note di implementazione: This approach directly addresses the friction caused by MAC address randomisation breaking captive portal session persistence. By using the captive portal to provision the profile, the hotel ensures a smooth transition for users while maintaining an access path for legacy devices that do not support Passpoint.

A national retail chain wants to offer secure, seamless Wi-Fi across its 500 locations to drive loyalty app engagement. However, managing custom certificates or individual credentials for millions of potential customers is deemed operationally unfeasible. What is the recommended deployment architecture?

The retailer should deploy Passpoint and federate with OpenRoaming. By configuring their access points to broadcast the settlement-free OpenRoaming OI (5A-03-BA) and establishing RadSec tunnels from their RADIUS infrastructure to an OpenRoaming hub, the retailer allows any customer with a compatible identity provider profile (such as a modern Samsung device or a mobile carrier profile) to connect automatically. The retailer can then integrate this with their loyalty app to trigger push notifications upon successful network association.

Note di implementazione: Federation via OpenRoaming is the optimal solution for scale. It offloads the burden of identity management and credential provisioning to established Identity Providers, allowing the retailer to focus on the access layer and the resulting engagement analytics.

Analisi degli scenari

Q1. A hospital IT director wants to deploy Passpoint to ensure doctors' mobile devices connect securely to the clinical network, while patients connect to a separate guest network. The doctors use unmanaged personal devices (BYOD). Which EAP method and provisioning strategy should the architect recommend?

💡 Suggerimento:Consider the balance between security and the operational overhead of managing certificates on unmanaged personal devices.

Mostra l'approccio consigliato

The architect should recommend EAP-TTLS with an Online Sign-Up (OSU) server provisioning flow. EAP-TLS requires client certificates, which are operationally difficult to deploy and manage on unmanaged BYOD devices. EAP-TTLS allows the doctors to authenticate securely using their existing Active Directory/LDAP credentials (username and password) tunneled inside a secure TLS session. The OSU server can provide a self-service portal where doctors log in once to download the profile, enabling automatic connection thereafter.

Q2. During a Passpoint deployment pilot, Android devices are successfully authenticating and connecting, but iOS devices are failing during the EAP handshake. The RADIUS logs show 'Unknown CA' errors. What is the most likely cause and solution?

💡 Suggerimento:Apple's iOS has strict requirements regarding the trust chain for RADIUS server certificates.

Mostra l'approccio consigliato

The most likely cause is that the RADIUS server is using a self-signed certificate or a certificate issued by a private internal Certificate Authority (CA) that the iOS devices do not inherently trust. Android devices sometimes allow users to bypass or ignore certificate validation (though this is poor security practice), whereas iOS strictly enforces it for Passpoint profiles. The solution is to replace the RADIUS server certificate with one issued by a publicly trusted commercial CA (e.g., DigiCert, Let's Encrypt), or ensure the private CA root certificate is explicitly bundled within the Passpoint configuration profile pushed to the iOS devices.

Q3. A stadium venue has implemented OpenRoaming. A user with a valid Google OpenRoaming profile walks into the venue, but their device does not attempt to connect automatically. What specific configuration on the stadium's wireless LAN controller should the network engineer verify first?

💡 Suggerimento:How does the device know that the access point supports the OpenRoaming federation before it attempts to connect?

Mostra l'approccio consigliato

The engineer should verify the ANQP configuration, specifically checking that the Access Points are broadcasting the correct Roaming Consortium Organisational Identifier (OI) for OpenRoaming, which is 5A-03-BA. If this OI is not included in the AP's beacon or GAS response, the device will not recognize the network as an OpenRoaming participant and will not attempt to authenticate.

Punti chiave

✓Passpoint (Hotspot 2.0) replaces manual captive portal logins with automatic, cellular-like Wi-Fi roaming.
✓It uses IEEE 802.11u for pre-association network discovery and WPA3-Enterprise for encrypted, mutually authenticated connections.
✓Passpoint solves the MAC address randomisation issue by authenticating the user's credential profile rather than their hardware address.
✓OpenRoaming is the global federation framework that allows Passpoint devices to connect across different venues seamlessly.
✓A dual-SSID strategy (Captive Portal for onboarding, Passpoint for returning users) is the recommended deployment model for enterprise venues.