Portais Cativos HTTPS em 2026: Porque é que o HSTS e o Reforço dos Navegadores Estão a Quebrar os Padrões Antigos

Este guia detalha como o HSTS e as políticas HTTPS-first dos navegadores estão a quebrar os portais cativos legados de interceção HTTP em 2026. Fornece orientação técnica acionável para arquitetos de rede implementarem alternativas modernas, incluindo a CAPPORT API e o Passpoint (Hotspot 2.0), garantindo acesso WiFi de convidado seguro e fiável.

📖 6 min de leitura📝 1,495 palavras🔧 2 exemplos❓ 3 perguntas📚 8 termos-chave

🎧 Ouça este Guia

Ver Transcrição

PODCAST SCRIPT: HTTPS Captive Portals in 2026 — Why HSTS and Browser Hardening Are Breaking the Old Patterns
Runtime target: ~10 minutes | Voice: UK English, senior consultant tone

---

[INTRO — ~60 seconds]

Welcome back. I'm going to cut straight to it today, because if you're running guest WiFi at scale — hotels, retail estates, stadiums, conference centres — you've probably already hit this problem, or you're about to.

The classic captive portal pattern — the one where your network intercepts an HTTP request and redirects the user to a splash page — is breaking. Not gradually. It's breaking hard, and the browser vendors are the ones doing it.

In the next ten minutes, I want to walk you through exactly what's changed, why it's changed, and what your realistic options are in 2026. This isn't theoretical. This is the conversation I'm having with network architects and IT directors every week right now.

Let's get into it.

---

[TECHNICAL DEEP-DIVE — ~5 minutes]

So let's start with the mechanism. The legacy captive portal pattern works like this: a device connects to your open or PSK-protected WiFi network. It tries to load a web page. Your network controller intercepts that HTTP request — port 80 traffic — and issues a 302 redirect to your portal page. The user sees your splash screen, accepts terms, maybe logs in, and then you open the walled garden. Simple. It's worked for twenty-plus years.

The problem is that pattern depends entirely on the device making an unencrypted HTTP request that you can intercept. And browsers are systematically eliminating those requests.

Here's the timeline of what's happened. HSTS — HTTP Strict Transport Security — has been around since RFC 6797 in 2012. The mechanism is straightforward: a site sends a Strict-Transport-Security header, and the browser remembers it. For the duration of the max-age period, the browser will refuse to load that site over plain HTTP. It upgrades the connection to HTTPS automatically. If HTTPS isn't available, the connection fails — hard. No bypass, no redirect, just a certificate error.

Now, HSTS on its own is manageable. The browser only enforces it after the first visit. But then came the HSTS preload list. Chrome maintains a hardcoded list of domains that are HTTPS-only, baked directly into the browser binary. Firefox, Safari, and Edge all consume the same list. As of 2026, that list covers well over 100,000 domains, including essentially every major consumer destination — Google, Facebook, Twitter, banking sites, government portals, the lot.

What that means in practice is this: when your guest device connects to your network and tries to load gmail.com, or bbc.co.uk, or any preloaded domain, the browser doesn't even attempt an HTTP request. It goes straight to HTTPS. Your network controller never sees a plain HTTP request to intercept. The redirect never happens. The user just gets a certificate error, because your portal's self-signed certificate is not trusted for gmail.com. They see NET::ERR_CERT_AUTHORITY_INVALID and they're stuck.

And it's getting worse. In October 2025, Google announced that Chrome 154 — shipping October 2026 — will enable "Always Use Secure Connections" by default for all users on public sites. Chrome 147, which shipped in April 2026, already enabled this for the one-billion-plus users who have Enhanced Safe Browsing turned on. Firefox has been moving in the same direction. Safari has had HTTPS-first behaviour on iOS for some time.

The net effect: by the end of 2026, the majority of your guests' browsers will attempt HTTPS for every navigation, regardless of whether the domain is on the preload list. The HTTP intercept pattern is not just unreliable — it's dead.

Now, there's a secondary problem that compounds this. Even when the OS-level Captive Network Assistant — the CNA — fires up its mini-browser to handle the portal, that mini-browser has its own HSTS enforcement. On iOS, the CNA uses a sandboxed WebKit instance. On Android, it uses a Chrome Custom Tab. Both enforce HSTS. Both will fail to load your portal if you're trying to serve it via a hostname that has an HSTS policy.

The correct technical response here is to serve your portal from a dedicated hostname that has never had an HSTS header and is not on the preload list — something like portal.yourvenue.com — with a valid, CA-signed TLS certificate. That's table stakes now. But even that doesn't fully solve the detection problem, because the device still needs to discover that it's behind a captive portal in the first place.

That's where RFC 8910 and RFC 8908 come in. RFC 8910 defines a DHCP option — option 114 — and an IPv6 Router Advertisement option that tells the client device the URL of the captive portal API endpoint. RFC 8908 defines that API: a simple JSON endpoint that the OS queries to determine whether internet access is restricted, and if so, where the portal is. Modern operating systems — iOS 14 and later, Android 11 and later, Windows 11 — all support this. When you implement CAPPORT correctly, the device knows it's behind a portal before it ever tries to load a web page. The OS fires up the CNA with the correct portal URL directly. No HTTP intercept required.

That's the first modern alternative: DNS and DHCP signalling via CAPPORT, with a properly-signed portal served from a dedicated hostname.

The second alternative is Passpoint, based on IEEE 802.11u and the Wi-Fi Alliance's Hotspot 2.0 specification. Passpoint takes a fundamentally different approach. Instead of intercepting traffic, the access point advertises its identity and authentication requirements via ANQP — Access Network Query Protocol — before the device even associates. The device checks whether it has valid credentials for this network. If it does, it authenticates via 802.1X and WPA2 or WPA3 Enterprise, and gets full network access immediately. No portal, no redirect, no browser involvement at all.

Passpoint is the right answer for a specific set of deployments: multi-site operators, enterprise environments, healthcare, transport hubs, anywhere you have repeat users who benefit from zero-touch connectivity. Purple's SecurePass product line is built around this model, and for the right deployment profile it eliminates the captive portal problem entirely.

The third option, which sits between the two, is OWE — Opportunistic Wireless Encryption. OWE is defined in RFC 8110 and provides per-client encryption on open networks without requiring credentials. It doesn't replace the portal, but it removes the open-network security exposure that makes regulators nervous, particularly under GDPR and PCI DSS.

---

[IMPLEMENTATION RECOMMENDATIONS & PITFALLS — ~2 minutes]

Right, so what should you actually do? Let me give you the practical framework.

If you're running a captive portal today and it's working, your immediate priority is to implement CAPPORT. That means configuring DHCP option 114 on your controller to point to your portal API endpoint, implementing the RFC 8908 JSON API on your portal server, and ensuring your portal is served from a dedicated hostname with a valid CA-signed certificate. This will restore reliable portal detection on modern devices and eliminate the certificate error problem.

Do not — I repeat, do not — attempt to serve your portal from a hostname that appears on the HSTS preload list. And do not use a self-signed certificate. Both of these are instant failure modes.

The second thing to address is your walled garden configuration. Your DHCP server, your DNS resolver, and your portal hostname all need to be accessible before authentication. That includes the OS detection probe URLs: captive.apple.com for Apple devices, connectivitycheck.gstatic.com for Android, and msftconnecttest.com for Windows. If any of these are blocked pre-auth, the CNA won't fire and your users will be stuck.

For new deployments, particularly in hospitality and multi-site retail, I'd strongly recommend evaluating a hybrid architecture: a Passpoint SSID for repeat visitors and a CAPPORT-compliant portal SSID for first-time guests, with the portal offering Passpoint profile installation as part of the onboarding flow. This gives you the marketing touchpoint for new visitors while delivering zero-friction connectivity for returning ones.

The pitfall I see most often is operators who've invested in portal customisation and data collection treating Passpoint as a threat to their marketing stack. It isn't. Purple's platform, for example, supports progressive onboarding where the initial portal interaction captures consent and profile data, and then provisions a Passpoint credential for future visits. You get the first-party data on the first visit and the seamless experience on every subsequent one.

---

[RAPID-FIRE Q&A — ~1 minute]

Quick-fire questions I get asked constantly:

"Can I just use a self-signed cert for my portal?" No. Modern browsers and CNA implementations will reject it. You need a CA-signed certificate.

"Does CAPPORT work on all devices?" iOS 14+, Android 11+, Windows 11 — yes. Older devices fall back to legacy detection behaviour. Plan for both.

"Is Passpoint GDPR-compliant?" Yes, when implemented correctly. The credential provisioning step is where you capture consent. Purple handles this as part of the SecurePass onboarding flow.

"What about PCI DSS scope?" If your guest network carries any cardholder data, you need network segmentation regardless of portal type. Passpoint's WPA3-Enterprise encryption significantly reduces your attack surface and simplifies scope arguments with QSAs.

---

[SUMMARY & NEXT STEPS — ~1 minute]

To wrap up: the HTTP intercept pattern is broken by HSTS preloading and Chrome's move to HTTPS-first by default. The fix for existing deployments is CAPPORT — RFC 8910 plus RFC 8908 — with a properly-signed portal on a dedicated hostname. For new deployments or major refreshes, evaluate Passpoint, particularly if you have repeat-visitor traffic or compliance requirements that benefit from WPA3-Enterprise encryption.

The browser vendors have made their position clear. The question isn't whether to adapt — it's how fast.

If you want to dig into the specifics for your deployment, the Purple team can walk you through a CAPPORT readiness assessment and a Passpoint feasibility analysis. Links in the show notes.

Thanks for listening. See you next time.

---
END OF SCRIPT

Principais Conclusões

✓Legacy HTTP intercept captive portals are fundamentally broken by HSTS preloading and browser HTTPS-first policies.
✓Chrome 154 (October 2026) enforces HTTPS-first by default, eliminating unencrypted port 80 traffic for portal detection.
✓Network architects must immediately implement the CAPPORT API (RFC 8908/8910) to restore reliable OS-level portal detection.
✓Portals must be hosted on dedicated hostnames with valid CA-signed certificates; self-signed certs and preloaded domains will fail.
✓Passpoint (Hotspot 2.0) is the definitive replacement for portals in enterprise and multi-site environments, offering WPA3 security and zero-touch roaming.
✓A hybrid approach—using CAPPORT for initial data capture and provisioning a Passpoint profile for return visits—balances marketing needs with seamless UX.
✓Proper walled garden configuration, including allowlisting OS probe URLs, is critical for the Captive Network Assistant (CNA) to function.

Resumo Executivo

O padrão legado de portal cativo — intercetar tráfego HTTP e emitir um redirecionamento 302 — está obsoleto. Impulsionado pelo HTTP Strict Transport Security (HSTS) e pelo reforço agressivo dos navegadores, o mecanismo tradicional de 'interceção e redirecionamento' está a falhar em larga escala em Hospitality , Retail e ambientes empresariais. A partir de 2026, com o Chrome a impor o comportamento HTTPS-first por predefinição e a lista de pré-carregamento HSTS a exceder 100.000 domínios, os controladores de rede já não podem depender de pedidos HTTP não encriptados para acionar a deteção do portal.

Para gestores de TI e arquitetos de rede, isto representa uma mudança arquitetónica crítica. Manter um acesso Guest WiFi contínuo exige agora a modernização do seu fluxo de integração. Este guia detalha os mecanismos técnicos que estão a quebrar os portais legados e descreve o caminho de implementação agnóstico a fornecedores: implementar a CAPPORT API (RFC 8908/8910) para estabilidade imediata, e migrar para Passpoint (Hotspot 2.0) e OpenRoaming para conectividade segura e sem toque.

Análise Técnica Aprofundada: Porque é que o HSTS Quebra o Padrão de Interceção

O portal cativo tradicional baseia-se numa premissa fundamental: o dispositivo cliente fará um pedido HTTP não encriptado na porta 80 que o servidor de acesso à rede (NAS) ou controlador pode intercetar e redirecionar para a página de apresentação do portal.

Esta premissa já não é válida.

O Problema do Pré-carregamento HSTS

O HTTP Strict Transport Security (HSTS), definido no RFC 6797, permite que um servidor web declare que os navegadores web devem interagir com ele apenas usando ligações HTTPS seguras. Quando um utilizador tenta aceder a um domínio protegido por HSTS via HTTP, o navegador atualiza internamente o pedido para HTTPS antes que qualquer tráfego de rede seja enviado.

Como o pedido é encriptado, o controlador de rede não pode inspecionar o cabeçalho do host ou emitir um redirecionamento HTTP 302. Em vez disso, o controlador interceta o tráfego HTTPS e apresenta o seu próprio certificado de portal. Uma vez que este certificado não corresponde ao domínio solicitado (por exemplo, google.com), o navegador lança um erro fatal NET::ERR_CERT_AUTHORITY_INVALID. O utilizador é bloqueado e o portal nunca carrega.

A lista de Pré-carregamento HSTS exacerba este problema. Os navegadores codificam uma lista de domínios que devem ser sempre acedidos via HTTPS, mesmo na primeira visita. Em 2026, esta lista inclui praticamente todos os principais destinos de consumo. Quando um convidado se conecta à sua rede e digita um URL comum, o navegador força o HTTPS, acionando o erro de certificado e quebrando o fluxo do portal cativo.

Reforço dos Navegadores: Modo HTTPS-First

Além do HSTS, os fornecedores de navegadores têm reforçado sistematicamente os seus comportamentos predefinidos. No final de 2025, a Google anunciou que o Chrome 154 (lançado em outubro de 2026) ativaria "Sempre Usar Conexões Seguras" por predefinição para todos os utilizadores em sites públicos. O Safari e o Firefox implementaram modos HTTPS-first semelhantes.

Isto significa que, mesmo para domínios que não estão na lista de pré-carregamento HSTS, o navegador tentará primeiro uma ligação HTTPS. O padrão de interceção HTTP está efetivamente obsoleto.

Alternativas Modernas: CAPPORT e Passpoint

Para restaurar a funcionalidade e melhorar a experiência do utilizador, os arquitetos de rede devem fazer a transição para mecanismos modernos de deteção de portal cativo e frameworks de autenticação.

1. A CAPPORT API (RFC 8908 e RFC 8910)

A Internet Engineering Task Force (IETF) abordou o problema da deteção de portal cativo com a arquitetura CAPPORT. Em vez de depender do tráfego web intercetado, o CAPPORT fornece um mecanismo de sinalização explícito.

RFC 8910 (Identificação de Portal Cativo): A rede usa DHCP (Opção 114) ou Anúncios de Router IPv6 para fornecer ao dispositivo cliente o URI da API do portal cativo.
RFC 8908 (Captive Portal API): O cliente consulta o URI fornecido (um endpoint JSON) para determinar se está cativo e para obter o URL da página do portal voltada para o utilizador.

Quando implementado, o SO cliente (iOS, Android, Windows) deteta nativamente o portal antes que o utilizador abra um navegador. O SO lança o seu Assistente de Rede Cativa (CNA) e carrega o URL do portal diretamente através de uma ligação HTTPS segura. Isto elimina a necessidade de interceção HTTP e evita erros de certificado.

2. Passpoint (Hotspot 2.0) e OpenRoaming

Para ambientes com visitantes recorrentes ou requisitos de alta segurança, o Passpoint (baseado no IEEE 802.11u) é o substituto definitivo para o portal cativo.

O Passpoint opera na camada MAC. Antes de se associar ao Ponto de Acesso (AP), o dispositivo cliente usa o Access Network Query Protocol (ANQP) para descobrir as capacidades da rede e os consórcios de roaming. Se o dispositivo possuir uma credencial correspondente (por exemplo, um perfil instalado durante uma visita anterior ou via um fornecedor de identidade), ele autentica-se automaticamente usando 802.1X e WPA2/WPA3-Enterprise.

Esta abordagem fornece conectividade tipo celular, sem toque. Encripta o tráfego sem fios, mitigando os riscos de redes abertas e ataques de evil twin. O OpenRoaming, construído sobre o Passpoint, estende isto ao federar fornecedores de identidade, permitindo que os utilizadores façam roaming de forma contínua em diferentes locais. Notavelmente, a Purple atua como um fornecedor de identidade gratuito para serviços como o OpenRoaming sob a licença Connect, facilitando uma ampla adoção sem taxas de licenciamento por utilizador.

Guia de Implementação

Implementar uma arquitetura de acesso de convidado resiliente requer uma abordagem faseada, passando da remediação imediata para a transformação estratégica.

Fase 1: Estabilizar Portais Existentes com CAPPORT

Se for necessário manter um Captive Portal tradicional para captura de dados ou WiFi Analytics , deve implementar o CAPPORT para contornar a quebra de HSTS.

Configurar a Opção DHCP 114: Atualize o seu servidor DHCP ou controlador de rede para difundir a Opção 114, apontando para o API endpoint do seu portal (por exemplo, https://portal.yourvenue.com/capport).
Implementar o API RFC 8908: Garanta que o seu servidor de portal responde ao pedido de API com JSON válido, indicando o estado cativo e o URL visível para o utilizador.
Utilizar um Nome de Anfitrião Dedicado e Válido: O portal deve ser servido via HTTPS utilizando um certificado válido, assinado por uma CA. Nunca utilize um certificado autoassinado ou um nome de anfitrião que esteja na lista de pré-carregamento HSTS.
Permitir Probes do SO: Garanta que os probes de deteção de Captive Portal ao nível do SO (por exemplo, captive.apple.com, connectivitycheck.gstatic.com) são permitidos através do walled garden pré-autenticação.

Fase 2: Implementar Passpoint para Acesso Seguro e Contínuo

A transição para Passpoint melhora significativamente a segurança e a experiência do utilizador, particularmente em implementações de Healthcare e Transport .

Verificar o Suporte da Infraestrutura: Garanta que os seus APs e controladores suportam Hotspot 2.0/Passpoint e autenticação 802.1X.
Configurar Perfis ANQP: Defina o nome do local, OIs do consórcio de roaming e NAI realms no seu controlador de rede.
Estabelecer um Backend RADIUS/AAA: Implemente um servidor RADIUS capaz de lidar com autenticação EAP (por exemplo, EAP-TLS, EAP-TTLS).
Implementar o Provisionamento de Perfis: Utilize um servidor Online Sign-Up (OSU) ou integre com uma plataforma como Purple SecurePass para provisionar perfis Passpoint para dispositivos de utilizador.

Fase 3: O Modelo de Onboarding Progressivo Híbrido

Para locais que requerem tanto acesso contínuo como captura inicial de dados (por exemplo, ambientes de retalho que procuram impulsionar a lealdade), uma abordagem híbrida é ótima.

Primeira Visita: O utilizador conecta-se a um SSID aberto e é direcionado para um Captive Portal com CAPPORT ativado. O portal captura os dados necessários (por exemplo, e-mail, aceitação de termos) e provisiona um perfil Passpoint para o dispositivo.
Visitas Subsequentes: O dispositivo do utilizador deteta automaticamente a rede Passpoint via ANQP e autentica-se de forma contínua utilizando 802.1X. O Captive Portal é completamente ignorado.

Melhores Práticas

Evitar o Jargão de Marketing 'Sem Atrito': Concentre-se na realidade técnica. O Passpoint requer atrito de provisionamento inicial para alcançar a continuidade a longo prazo.
Segmentar o Tráfego de Convidados: Independentemente do método de autenticação, o tráfego de convidados deve ser logicamente separado das redes corporativas utilizando VLANs e firewalls, alinhando-se com Internet of Things Architecture: A Complete Guide .
Monitorizar a Expiração de Certificados: Um certificado TLS expirado no seu portal ou servidor RADIUS causará falhas catastróficas de autenticação. Implemente renovação e monitorização automatizadas.
Cumprir com os Regulamentos de Privacidade de Dados: Garanta que as suas políticas de captura e retenção de dados estão alinhadas com as leis locais. Para orientação regional específica, consulte recursos como o Brazil LGPD and Guest WiFi: A Compliance Guide .

Resolução de Problemas e Mitigação de Riscos

Sintoma: Dispositivos iOS mostram um ecrã CNA em branco.
- Causa: A página do portal contém recursos (imagens, scripts) alojados em domínios externos que são bloqueados pelo walled garden.
- Correção: Aloje todos os ativos essenciais do portal localmente ou adicione os domínios externos necessários à allowlist de pré-autenticação.
Sintoma: Dispositivos Android exibem um aviso de certificado em vez do portal.
- Causa: O controlador está a intercetar o tráfego HTTPS para um domínio HSTS pré-carregado, ou o certificado TLS do portal é inválido/autoassinado.
- Correção: Implemente o CAPPORT e garanta que o portal utiliza um certificado assinado por uma CA num nome de anfitrião dedicado.
Sintoma: A instalação do perfil Passpoint falha no Windows 11.
- Causa: A cadeia de certificados do servidor de provisionamento está incompleta ou não é fidedigna para o SO.
- Correção: Verifique se a cadeia de certificados completa (incluindo CAs intermédias) é servida durante o handshake TLS.

ROI e Impacto no Negócio

A transição de portais de interceção HTTP legados para arquiteturas CAPPORT e Passpoint modernas oferece valor de negócio mensurável:

Redução de Tickets de Suporte: A eliminação de erros de certificado relacionados com HSTS reduz diretamente o volume de pedidos ao IT helpdesk relativamente a problemas de conectividade de convidados.
Aumento das Taxas de Conexão: A deteção fiável de portal ao nível do SO garante que mais convidados concluem com sucesso o fluxo de onboarding, expandindo o seu público alcançável para iniciativas de marketing.
Postura de Segurança Melhorada: A mudança para Passpoint e WPA3-Enterprise mitiga os riscos associados a redes abertas, protegendo contra escutas e ataques de evil twin, o que é crítico para a conformidade em setores como finanças e healthcare.
Experiência do Utilizador Melhorada: O roaming zero-touch via Passpoint impulsiona maior satisfação do utilizador e envolvimento repetido, apoiando iniciativas digitais mais amplas como Indoor Positioning System: UWB, BLE, & WiFi Guide e Your Guide to Enterprise In Car Wi Fi Solutions .

Termos-Chave e Definições

HSTS (HTTP Strict Transport Security)

A web security policy mechanism that forces web browsers to interact with domains only via secure HTTPS connections, preventing protocol downgrade attacks and HTTP interception.

When IT teams see an increase in certificate errors on guest networks, HSTS enforcement on popular domains is typically the root cause, breaking legacy redirect mechanisms.

HSTS Preload List

A hardcoded list built into modern web browsers containing domains that must always be accessed via HTTPS, even on the very first visit.

If a user attempts to navigate to a preloaded domain (like google.com) while behind a legacy captive portal, the browser will refuse the HTTP connection, preventing the portal redirect.

CAPPORT (Captive Portal Architecture)

An IETF standard (RFC 8908 and 8910) that uses DHCP or IPv6 Router Advertisements to explicitly signal the presence and URL of a captive portal to a client device.

Implementing CAPPORT is the primary remediation strategy for network architects to fix broken portal detection on modern iOS, Android, and Windows devices.

Passpoint (Hotspot 2.0)

A Wi-Fi Alliance specification based on IEEE 802.11u that enables devices to automatically discover and securely authenticate to Wi-Fi networks without user intervention.

Used in enterprise and multi-site deployments to replace captive portals entirely, providing cellular-like roaming and WPA3-Enterprise security.

ANQP (Access Network Query Protocol)

A layer 2 protocol used by client devices to query Access Points for network information (like roaming partners and supported authentication types) before associating.

ANQP is the discovery mechanism that allows a Passpoint-enabled device to determine if it has the correct credentials to join a specific network silently.

CNA (Captive Network Assistant)

The OS-level pseudo-browser that automatically opens when a device detects it is behind a captive portal, allowing the user to authenticate before gaining full internet access.

IT teams must ensure their walled garden allows access to the OS-specific probe URLs (e.g., captive.apple.com) so the CNA triggers correctly.

OpenRoaming

A global Wi-Fi roaming federation that allows users to connect automatically and securely across different venues using a single set of credentials provided by an identity provider.

Venues adopt OpenRoaming to provide seamless access for guests, leveraging identity providers like Purple to manage authentication without complex bilateral agreements.

Walled Garden

A restricted network environment where unauthenticated users can only access a specific set of pre-approved IP addresses or domains necessary for the login process.

Misconfigured walled gardens that block OS detection probes or external portal assets are a leading cause of blank screens and failed guest onboarding.

Estudos de Caso

A 400-room enterprise hotel is experiencing a 30% drop in successful guest WiFi connections. Users report seeing 'Your connection is not private' (NET::ERR_CERT_AUTHORITY_INVALID) errors on their smartphones when trying to access the network. The hotel currently uses a legacy open SSID that intercepts port 80 traffic to redirect to a branded splash page.

The IT team must immediately implement the CAPPORT API (RFC 8908/8910). First, configure the network controller's DHCP server to broadcast Option 114, providing the URI of the captive portal API. Second, deploy the RFC 8908 JSON endpoint on the portal server. Third, ensure the portal is hosted on a dedicated subdomain (e.g., wifi.hoteldomain.com) with a valid, CA-signed TLS certificate. Finally, verify that OS detection URLs (like captive.apple.com) are allowed pre-authentication.

Notas de Implementação: This approach directly addresses the HSTS breakage by utilizing out-of-band signalling (DHCP) to inform the OS of the portal's location, rather than relying on intercepting encrypted web traffic. It restores the native Captive Network Assistant (CNA) experience without triggering browser certificate warnings.

A large retail chain with 500 locations wants to implement seamless WiFi roaming for their loyalty app users, eliminating the need for customers to interact with a captive portal on every visit, while still maintaining high security standards (WPA3).

The architect should deploy a Passpoint (Hotspot 2.0) architecture. The initial onboarding can occur via the retailer's loyalty app, which provisions a Passpoint profile (credential) to the user's device. The APs across all 500 locations must be configured to broadcast the appropriate ANQP roaming consortium OIs. A centralized RADIUS infrastructure will handle the 802.1X EAP authentication when the device automatically associates with the network.

Notas de Implementação: Passpoint is the correct solution for multi-site roaming and high security. By moving authentication to the MAC layer (802.1X) and utilizing WPA3-Enterprise, the network avoids the vulnerabilities of open SSIDs and the UX friction of repeated captive portal logins.

Análise de Cenários

Q1. Your organisation is deploying a new guest WiFi network across 50 regional offices. Security policy mandates that all wireless traffic must be encrypted over the air, but the marketing team insists on capturing user email addresses upon first connection. Which architecture should you propose?

💡 Dica:Consider how to balance the requirement for initial data capture with the mandate for over-the-air encryption.

Mostrar Abordagem Recomendada

Propose a hybrid progressive onboarding architecture. First-time users connect to an open SSID and are directed to a CAPPORT-enabled captive portal to provide their email address. Upon submission, the portal provisions a Passpoint profile to the device. The device then automatically transitions to a secure, WPA3-Enterprise encrypted Passpoint SSID for all subsequent traffic and future visits. This satisfies marketing's data capture requirement while enforcing security policy for the vast majority of network usage.

Q2. A client complains that their newly designed, highly customized captive portal page is displaying a blank white screen on all modern iOS devices, although it works perfectly on older Android phones. The portal relies heavily on external web fonts and a third-party analytics script.

💡 Dica:Think about how the iOS Captive Network Assistant (CNA) interacts with external resources before the device is fully authenticated.

Mostrar Abordagem Recomendada

The issue is a misconfigured walled garden. The iOS CNA is attempting to render the portal page, but the external domains hosting the web fonts and analytics scripts are blocked by the network controller pre-authentication. Because these resources cannot load, the CNA stalls and displays a blank screen. The solution is to either host all required assets locally on the portal server or add the specific external domains (FQDNs) to the controller's pre-authentication allowlist.

Q3. During a network audit, you discover that the legacy captive portal is intercepting traffic and serving a self-signed certificate. You are tasked with upgrading the system to use the CAPPORT API. What specific certificate requirements must be met for the new portal server?

💡 Dica:Consider how modern browsers and OS CNAs handle certificate validation during the captive portal detection phase.

Mostrar Abordagem Recomendada

The new portal server must be accessed via a dedicated Fully Qualified Domain Name (FQDN) that is NOT on the HSTS preload list. Furthermore, it must use a valid TLS certificate issued by a publicly trusted Certificate Authority (CA). Self-signed certificates will be rejected by the OS CNA and modern browsers, preventing the portal from loading and halting the onboarding process.