Cómo Passpoint (Hotspot 2.0) transforma la experiencia de Wi-Fi para invitados

Una guía de referencia técnica exhaustiva que detalla cómo los protocolos Passpoint (Hotspot 2.0) y 802.11u sustituyen a los Captive Portals tradicionales por un roaming Wi-Fi fluido, seguro y similar al celular. Proporciona a los responsables de IT visiones generales de la arquitectura, marcos de implementación y el caso de negocio para adoptar la autenticación basada en credenciales para resolver los desafíos de la aleatorización de MAC y mejorar la experiencia del invitado.

📖 6 min de lectura📝 1,359 palabras🔧 2 ejemplos❓ 3 preguntas📚 8 términos clave

🎧 Escuchar esta guía

Ver transcripción

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.

Resumen Ejecutivo

Para el recinto empresarial moderno, la fricción es una desventaja competitiva. Los Captive Portals tradicionales, aunque antes eran el estándar para el acceso a la red de invitados, ahora representan un cuello de botella operativo significativo y una fuente de frustración persistente para el usuario. Passpoint, también conocido como Hotspot 2.0, transforma fundamentalmente este paradigma al sustituir la autenticación manual basada en web por un roaming fluido, similar al de las redes celulares. Al aprovechar el estándar IEEE 802.11u y el cifrado WPA3-Enterprise, Passpoint permite que los dispositivos de los invitados descubran, se autentiquen y se conecten a las redes Wi-Fi empresariales de forma automática y segura.

Para los responsables de IT en los sectores de Hostelería , Retail y grandes recintos públicos, la transición a Passpoint ya no es opcional. La aleatorización de direcciones MAC predeterminada implementada en los dispositivos iOS y Android modernos ha roto efectivamente la lógica de reautenticación de los Captive Portals heredados, lo que significa que los invitados que regresan aparecen como dispositivos nuevos en cada visita. Passpoint resuelve esto autenticando el perfil de credenciales del usuario en lugar de su dirección de hardware. Esta guía detalla la arquitectura técnica de Passpoint, el impacto empresarial del despliegue y un marco de implementación neutral respecto al proveedor, diseñado para mejorar la experiencia de Guest WiFi y reducir la carga de trabajo del helpdesk.

Inmersión Técnica Profunda

El problema de la selección de red y 802.11u

En los despliegues de Wi-Fi heredados, los dispositivos dependen de un mecanismo fundamentalmente frágil para la selección de red: el escaneo de Identificadores de Conjunto de Servicios (SSID) conocidos. Este enfoque requiere que el usuario se haya conectado previamente a la red o que seleccione manualmente la red de una lista. No proporciona visibilidad previa a la asociación sobre la postura de seguridad de la red, los requisitos de autenticación o la disponibilidad de internet ascendente. Passpoint aborda esta limitación a través de la enmienda IEEE 802.11u, que introduce el Interfuncionamiento con Redes Externas.

En lugar de escanear pasivamente los SSID, un dispositivo habilitado para Passpoint consulta activamente la infraestructura de red antes de intentar la asociación. Cuando un punto de acceso emite su baliza (beacon), incluye un Elemento de Interfuncionamiento, un indicador que señala la compatibilidad con 802.11u. El dispositivo cliente detecta este indicador e inicia una solicitud de Servicio de Anuncio Genérico (GAS). Encapsulada dentro de esta solicitud se encuentra una consulta del Protocolo de Consulta de Red de Acceso (ANQP). El dispositivo pregunta a la infraestructura: "¿Qué Identificadores Organizativos (OI) de Consorcio de Roaming soportas?". Si la respuesta del punto de acceso coincide con un perfil de credenciales almacenado en el dispositivo, se procede a la autenticación automática.

Arquitectura de Seguridad y Autenticación

Passpoint exige seguridad de nivel empresarial, eliminando por completo la fase de "red abierta" inherente a los despliegues de Captive Portal. La autenticación se gestiona a través del control de acceso a la red basado en puertos IEEE 802.1X, junto con un método de Protocolo de Autenticación Extensible (EAP). Los métodos más frecuentes en los despliegues empresariales son EAP-TLS (basado en certificados de cliente y servidor), EAP-TTLS (credenciales tunelizadas) y EAP-SIM/AKA (para escenarios de descarga celular).

Esta arquitectura proporciona autenticación mutua. El dispositivo demuestra criptográficamente su identidad a la red y, lo que es crucial, la red demuestra su identidad al dispositivo. Esta verificación mutua es la defensa principal contra los puntos de acceso "evil twin" y los intentos de interceptación de intermediarios (man-in-the-middle). Además, Passpoint exige el cifrado WPA2-Enterprise o WPA3-Enterprise. WPA3-Enterprise introduce el modo de seguridad de 192 bits y exige el secreto hacia adelante (forward secrecy), garantizando que incluso si las claves de sesión se ven comprometidas en el futuro, el tráfico histórico permanezca cifrado.

La Federación OpenRoaming

Mientras que Passpoint define el mecanismo técnico para el descubrimiento y la autenticación, OpenRoaming proporciona el marco de confianza. Desarrollado por la Wireless Broadband Alliance (WBA), OpenRoaming es una federación global que permite a los Proveedores de Identidad (como operadores de redes móviles, Google o Apple) y a los Proveedores de Acceso (como hoteles, estadios y cadenas de retail) confiar en las credenciales de los demás sin necesidad de acuerdos bilaterales entre cada entidad.

OpenRoaming opera bajo un modelo de Infraestructura de Clave Pública (PKI) de tipo hub-and-spoke. Las solicitudes de autenticación se envían por proxy a través de la federación utilizando túneles RadSec (RADIUS sobre TLS). Al emitir el OI de OpenRoaming sin liquidación (5A-03-BA), un recinto empresarial puede proporcionar instantáneamente un acceso Wi-Fi fluido y seguro a millones de usuarios en todo el mundo que ya poseen un perfil de identidad compatible en sus dispositivos.

Guía de Implementación

Desplegar Passpoint requiere una base de infraestructura más sofisticada que una red abierta tradicional, pero los componentes son estándar en los entornos empresariales modernos.

Requisitos Previos de Infraestructura

Puntos de Acceso Certificados para Passpoint: La infraestructura inalámbrica debe ser compatible con las especificaciones 802.11u y Hotspot 2.0. La gran mayoría de los puntos de acceso empresariales fabricados en los últimos cinco años por proveedores como Cisco, Aruba y Ruckus cumplen con este requisito.
Infraestructura RADIUS/AAA: Un servidor RADIUS robusto capaz de gestionar la autenticación EAP y de enrutar las solicitudes a los almacenes de identidad adecuados. Si se participa en OpenRoaming, el servidor RADIUS debe ser compatible con RadSec para un proxy seguro.
Servidor de Registro en Línea (OSU): Para entornos que emiten sus propias credenciales (en lugar de depender únicamente de identidades federadas), un servidor OSU proporciona el mecanismo para suministrar de forma segura perfiles Passpoint a los dispositivos de los invitados.

La Estrategia de SSID Dual

El modelo de despliegue más eficaz para los recintos que transicionan a Passpoint es la estrategia de SSID dual. Este enfoque mantiene un SSID de Captive Portal tradicional para la incorporación inicial, mientras proporciona un SSID de Passpoint para conexiones posteriores fluidas.

Cuando un invitado se conecta al SSID del Captive Portal por primera vez, completa el flujo de autenticación estándar (por ejemplo, aceptando términos y condiciones, proporcionando un correo electrónico). Tras una autenticación exitosa, el portal presenta una opción para descargar un perfil Passpoint. Una vez instalado, el dispositivo preferirá automáticamente el SSID seguro de Passpoint en todas las visitas futuras. Este modelo de incorporación progresiva garantiza la accesibilidad para los dispositivos heredados mientras migra a la mayoría de los usuarios a la red Passpoint segura y sin fricciones.

Mejores Prácticas

Al diseñar una arquitectura Passpoint, los responsables de IT deben adherirse a varias mejores prácticas críticas para garantizar la estabilidad operativa y la seguridad.

En primer lugar, la gestión del ciclo de vida de los certificados es primordial. Si se utiliza EAP-TLS, la expiración de los certificados de cliente o servidor provocará fallos de autenticación silenciosos que son difíciles de diagnosticar para los helpdesks de primera línea. Implemente protocolos de renovación automática de certificados y una monitorización proactiva. Como se destaca en nuestra guía sobre Evaluación de la postura del dispositivo para el control de acceso a la red , una visibilidad robusta de los endpoints es esencial cuando se gestiona el acceso basado en certificados.

En segundo lugar, garantice la compatibilidad con dispositivos heredados. Aunque iOS 7+, Android 6+ y Windows 10+ soportan Passpoint de forma nativa, ciertos dispositivos IoT, hardware antiguo y dispositivos estrictamente gestionados por empresas pueden carecer de soporte. La estrategia de SSID dual mitiga este riesgo al proporcionar un método de acceso de reserva.

En tercer lugar, al configurar los elementos ANQP, asegúrese de que la Información del Recinto sea precisa y descriptiva. Estos metadatos suelen ser mostrados por el sistema operativo del dispositivo cliente para proporcionar contexto sobre la red a la que se une el usuario.

Resolución de Problemas y Mitigación de Riesgos

La complejidad de Passpoint introduce dominios de fallo específicos que difieren de los despliegues de Captive Portal.

Modo de fallo 1: Tiempo de espera o inaccesibilidad de RADIUS Si el servidor RADIUS local no puede alcanzar al Proveedor de Identidad ascendente (especialmente en escenarios federados de OpenRoaming), el protocolo de enlace EAP agotará el tiempo de espera. Mitigación: Implemente una infraestructura RADIUS redundante y garantice una monitorización robusta de los túneles RadSec. Revise nuestra documentación técnica sobre RadSec: Sécurisation du trafic d'authentification RADIUS avec TLS para obtener orientación sobre la configuración.

Modo de fallo 2: Fallos en el suministro del perfil Los usuarios pueden encontrar errores al intentar descargar el perfil Passpoint desde el servidor OSU, a menudo debido a las limitaciones del navegador del Captive Portal en dispositivos móviles. Mitigación: Diseñe el flujo del Captive Portal para salir del mini-navegador del asistente de red cautiva (CNA) hacia el navegador nativo del sistema del dispositivo antes de iniciar la descarga del perfil.

Modo de fallo 3: Impacto de la aleatorización de MAC en la analítica Aunque Passpoint resuelve la ruptura de la autenticación causada por la aleatorización de MAC, las plataformas de analítica heredadas que dependen únicamente de las direcciones MAC seguirán reportando recuentos de visitantes inexactos. Mitigación: Integre los registros de autenticación RADIUS con su plataforma de WiFi Analytics . Al rastrear identificadores de credenciales únicos (como la Chargeable User Identity o el NAI anonimizado) en lugar de direcciones MAC, los recintos pueden restaurar métricas precisas de afluencia y fidelidad.

ROI e Impacto Empresarial

El caso de negocio para el despliegue de Passpoint se basa en tres pilares medibles: eficiencia operativa, reducción de riesgos y experiencia del usuario.

Desde un punto de vista operativo, la eliminación de la fricción del Captive Portal se correlaciona directamente con una reducción de los tickets del helpdesk de IT relacionados con la conectividad Wi-Fi. En grandes entornos de Sanidad o Transporte , esto representa un ahorro de costes significativo.

En cuanto a la mitigación de riesgos, el cambio de redes abiertas al cifrado WPA3-Enterprise reduce sustancialmente la huella de responsabilidad del recinto. Para los entornos de retail sujetos a PCI DSS, la reducción del área de superficie de manejo de datos (al eliminar la recopilación de credenciales basada en web) simplifica las auditorías de cumplimiento.

Finalmente, la mejora de la experiencia del usuario es profunda. En hostelería, los estudios muestran consistentemente que un Wi-Fi fluido y fiable es un factor principal para la satisfacción del huésped y la repetición de reservas. Al implementar Passpoint, los recintos ofrecen una experiencia de conectividad que refleja la fiabilidad de las redes celulares, transformando el Wi-Fi de una utilidad frustrante en un servicio premium transparente.

Términos clave y definiciones

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.

Casos de éxito

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.

Notas de implementación: 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.

Notas de implementación: 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.

Análisis de escenarios

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?

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

Mostrar enfoque recomendado

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?

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

Mostrar enfoque recomendado

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?

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

Mostrar enfoque recomendado

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.

Conclusiones clave

✓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.