Captive Portal para Aruba
Una guía de referencia técnica autorizada para configurar puntos de acceso gestionados por Aruba Instant (IAP) y Aruba Central para redirigir a los usuarios invitados al Captive Portal externo, seguro y de alta conversión de Purple. Esta guía cubre la configuración paso a paso del SSID de invitados, la redirección al Captive Portal externo, los parámetros de autenticación y contabilidad del servidor RADIUS, las listas de excepciones de walled garden y el soporte de WISPr.
Escucha esta guía
Ver transcripción del podcast
📚 Parte de nuestra serie principal: WiFi multi-tenant →
- Executive Summary
- Technical Deep-Dive
- The Captive Portal Redirect Flow
- RADIUS Authentication and Accounting Parameters
- The Walled Garden (Exception List) Architecture
- Implementation Guide
- Aruba Instant (IAP) Configuration (ArubaOS 8.x)
- Aruba Central Configuration (AOS-8 and AOS-10)
- Best Practices
- 1. Secure Certificate Management
- 2. Network Segmentation and Compliance
- 3. Optimising WISPr and Captive Portal Detection
- Troubleshooting & Risk Mitigation
- Captive Portal Troubleshooting Matrix
- ROI & Business Impact
- Operational Efficiency and Scalability
- Data Monetisation and Marketing ROI
- Cost-Benefit Analysis: Native Aruba vs. Purple Integration

Executive Summary
For enterprise wireless engineers, network architects, and venue operations directors, deploying a robust guest wireless infrastructure is no longer just about providing basic internet access. Modern venues require a solution that balances strict network security, regulatory compliance, and a high-converting guest experience. While HPE Aruba's native captive portal capabilities are highly reliable, they lack the sophisticated marketing data capture, global multi-site scalability, and real-time location and demographic analytics required by enterprise venues in hospitality, retail, and public sectors.
By integrating Purple directly with Aruba Instant (IAP) or Aruba Central managed access points, organisations can replace basic local splash pages with a secure, highly-scalable, global guest portal. This integration leverages standard network protocols, including Remote Authentication Dial-In User Service (RADIUS) and Wireless Internet Service Provider roaming (WISPr), to deliver seamless, secure, and brand-consistent onboarding. This technical reference guide provides the exact configuration parameters, architectural diagrams, and troubleshooting workflows required to successfully deploy Purple on Aruba infrastructure.
Technical Deep-Dive
The integration of Purple with Aruba wireless infrastructure relies on a standard external captive portal redirect and RADIUS authentication flow. This architecture ensures that user authentication and traffic accounting are handled securely in the cloud, while local access points enforce access control and quality of service (QoS) policies.
The Captive Portal Redirect Flow
When an unauthenticated client associates with the guest Service Set Identifier (SSID), the Aruba access point intercepts the client's initial HTTP request (typically TCP port 80) and performs a HTTP 302 redirect to Purple's cloud-hosted splash page.
+--------------+ +-----------------+ +------------------+ +------------------+
| Guest Device | | Aruba AP / AP | | Purple Captive | | Purple RADIUS |
| (Client) | | (Central/IAP) | | Portal (Cloud) | | Server (Cloud) |
+--------------+ +-----------------+ +------------------+ +------------------+
| | | |
|-- 1. Associates to SSID ---->| | |
| | | |
|-- 2. HTTP Request (TCP 80) ->| | |
| |-- 3. HTTP 302 Redirect ------>| |
|<-- 4. Presents Splash Page ----------------------------------| |
| | | |
|-- 5. Submits Login Form ------------------------------------>| |
| | |-- 6. RADIUS Access-Request --->|
| |<-- 7. RADIUS Access-Accept ------------------------------------|
| | (with Session Timeout) | |
|<-- 8. Internet Granted ------| | |
| | | |
| |-- 9. RADIUS Accounting Start --------------------------------->|
| |-- 10. RADIUS Accounting Interim (every 5 min) ---------------->|

RADIUS Authentication and Accounting Parameters
Once the guest submits their credentials or completes a social login on the Purple splash page, the Purple portal backend communicates with the local Aruba access point or controller to initiate RADIUS authentication. The Aruba AP acts as the Network Access Server (NAS) and sends a RADIUS Access-Request to Purple's cloud RADIUS servers on UDP port 1812.
To ensure accurate session tracking, policy enforcement, and reporting, the following RADIUS attributes must be exchanged:
| Attribute Name | Attribute ID | Description | Practical Context |
|---|---|---|---|
| NAS-IP-Address | 4 | The management IP address of the Aruba virtual controller or AP. | Identifies the physical hardware originating the authentication request. |
| Calling-Station-Id | 31 | The MAC address of the client device (typically formatted as XX-XX-XX-XX-XX-XX). |
Used by Purple to track unique devices and enforce MAC caching for returning guests. |
| Called-Station-Id | 30 | The MAC address of the AP radio (BSSID) combined with the SSID name (formatted as MAC:SSID). |
Crucial for Purple to identify the exact physical venue and specific SSID the user is connecting to. |
| Acct-Session-Id | 44 | A unique identifier generated by the AP for each client session. | Links authentication events with subsequent accounting start, interim, and stop records. |
| Acct-Status-Type | 40 | Indicates the type of accounting record: Start (1), Stop (2), or Interim-Update (3). |
Enables real-time tracking of active sessions and accurate dwell-time calculations. |
| Acct-Interim-Interval | 85 | Specifies the frequency (in seconds) of interim accounting updates sent by the AP. | Must be set to 300 seconds (5 minutes) to ensure Purple's analytics dashboard displays accurate real-time data. |
The Walled Garden (Exception List) Architecture
Before a user is authenticated, the Aruba AP restricts all traffic except for destinations explicitly defined in the Walled Garden (or exception list). Because Purple's portal is cloud-hosted and relies on external identity providers (such as Google, Facebook, and Apple) for social authentication, the AP must allow unauthenticated clients to resolve DNS and communicate with these external domains.
If any required domain is omitted from the walled garden, the guest will experience a blank page, broken CSS, missing images, or a complete timeout during the login flow.

Implementation Guide
Deploying Purple on Aruba wireless infrastructure can be achieved via Aruba Instant (IAP) running ArubaOS 8.x (on-premises virtual-controller mode) or Aruba Central (cloud-managed AOS-8 or AOS-10).
Aruba Instant (IAP) Configuration (ArubaOS 8.x)
Step 1: Configure RADIUS Servers
- Log in to the Aruba Instant AP virtual controller web interface.
- Navigate to Security > Authentication Server and click New.
- Configure the Primary RADIUS Server with the following parameters:
- Name:
Purple_Primary - IP Address:
34.94.146.135 - Auth Port:
1812 - Acct Port:
1813 - Shared Key: [Provided in your Purple Venue Dashboard]
- Name:
- Click OK to save.
- Click New again to configure the Secondary RADIUS Server:
- Name:
Purple_Secondary - IP Address:
34.94.183.201 - Auth Port:
1812 - Acct Port:
1813 - Shared Key: [Provided in your Purple Venue Dashboard]
- Name:
- Click OK to save.
Step 2: Create the Captive Portal Profile
- Navigate to Security > Captive Portal and click New.
- Configure the profile with the following settings:
- Name:
Purple_Portal - Type:
External - IP or Hostname:
portal.venuewifi.com - URL:
/ - Port:
443 - Use HTTPS:
Enabled - Redirect URL:
https://portal.venuewifi.com - WISPr:
Enabled(Crucial for auto-triggering the portal on iOS and Android devices)
- Name:
- Click OK to save.
Step 3: Configure the Walled Garden Whitelist
- In the Security > Captive Portal menu, select your newly created
Purple_Portalprofile. - Under the Walled Garden section, click the link to open the whitelist configuration.
- Add the following core Purple domains:
*.purple.ai*.cloudfront.net*.venuewifi.com
- If social login is enabled, add the respective domains (e.g.,
*.google.com,*.facebook.com,*.apple.com). - Click Save.
Step 4: Create and Configure the Guest SSID
- Navigate to Network > New to start the WLAN wizard.
- On the WLAN Settings tab:
- Name (SSID):
Guest-WiFi - Primary Usage:
Guest - Click Next.
- Name (SSID):
- On the VLAN tab, configure IP and VLAN assignment according to your network architecture (typically Client IP assignment: Network Assigned on a dedicated guest VLAN). Click Next.
- On the Security tab:
- Splash Page Type:
External - Captive Portal Profile: Select
Purple_Portal - Auth Server 1: Select
Purple_Primary - Auth Server 2: Select
Purple_Secondary - Reauth Interval:
1440(24 hours, or as per venue policy) - Accounting:
Enabled - Accounting Interval:
5minutes
- Splash Page Type:
- Click Next to proceed to the Access tab. Ensure the default guest rule allows DHCP and DNS pre-authentication, then click Finish.
Aruba Central Configuration (AOS-8 and AOS-10)
Aruba Central AOS-8
- Navigate to Devices under the Manage section of your group in Aruba Central.
- Click Config (gear icon) on the top right, then go to the WLANs tab and click + Add SSID.
- In Step 1: General, enter the SSID name (e.g.,
Guest-WiFi) and click Next. - In Step 2: VLANs, configure your guest VLAN mapping and click Next.
- In Step 3: Security:
- Set Security Level to
Visitors. - Set Type to
External Captive Portal. - Ensure Key Management is set to
Open(do not use Enhanced Open/OWE for standard guest portals as it can cause client compatibility issues). - Click the + icon next to Captive Portal Profile to add a new profile:
- Name:
Purple_Central_Portal - IP or Hostname:
portal.venuewifi.com - URL:
/ - Port:
443 - Redirect URL:
https://portal.venuewifi.com - Use HTTPS:
True - Captive Portal Failure:
Deny Internet(Recommended for security compliance)
- Name:
- Click Save.
- Click the + icon next to Primary Server and Secondary Server to add the Purple RADIUS servers using the IPs
34.94.146.135and34.94.183.201respectively, with ports1812(Auth) and1813(Acct). - Expand Advanced Settings, scroll to Accounting, select
Use authentication servers, and set Accounting Interval to5minutes.
- Set Security Level to
- Scroll down to the Walled Garden section, click + Add, and input the required Purple and social login domains.
- Click Save Settings.
Aruba Central AOS-10
In AOS-10, the walled garden configuration moves from the WLAN Security tab to Access Rules.
- Follow the same SSID and RADIUS configuration steps as AOS-8 above.
- In the SSID wizard, navigate to the Access tab.
- Click + Add Role and create a pre-authentication role named
Purple_Pre_Auth. - In the rules editor for this role, configure explicit Allow rules for DNS, DHCP, and the required walled garden domains (e.g.,
*.purple.ai,*.venuewifi.com). - Scroll down to Assign Pre-Authentication Role, enable the option, and select
Purple_Pre_Authfrom the dropdown. - The post-authorisation role (typically matching the SSID name) should remain configured with
Allow any to all destinationsor your specific corporate access policies. - Click Save Settings.
Best Practices
To ensure maximum performance, security, and compliance, network architects must adhere to the following industry standards and vendor-neutral best practices when deploying captive portals on Aruba and Purple.
1. Secure Certificate Management
Aruba access points must present a valid, trusted SSL/TLS certificate during the captive portal redirect flow.
- Avoid Self-Signed Certificates: If the AP presents a self-signed certificate, modern browsers will display a highly visible "Your connection is not private" warning, severely damaging guest trust and reducing conversion rates.
- Deploy a Trusted CA Certificate: Upload a wildcard certificate from a globally recognised Certificate Authority (CA) to your Aruba Central global settings or Instant virtual controllers. Ensure that the intermediate and root certificates are combined into a single file to complete the trust chain.
2. Network Segmentation and Compliance
Guest traffic must be kept entirely separate from corporate and administrative traffic to mitigate security risks and ensure compliance with industry standards.
- VLAN Isolation: Map the guest SSID to a dedicated, non-routable VLAN. Use Access Control Lists (ACLs) on the upstream core switch or firewall to prevent any routing between the guest VLAN and internal corporate subnets.
- PCI DSS Compliance: If your venue processes card payments (e.g., retail point-of-sale), network segmentation is a mandatory requirement under PCI DSS Requirement 1.2 [3]. Guest WiFi must be physically or logically isolated from the Cardholder Data Environment (CDE).
- GDPR and Data Privacy: Ensure that the Purple portal is configured to display explicit, un-ticked consent checkboxes for marketing opt-ins, meeting the strict requirements of the General Data Protection Regulation (GDPR) [4].
3. Optimising WISPr and Captive Portal Detection
Modern mobile operating systems use active probing to detect captive portals immediately upon association.
- Enable WISPr: Always ensure that WISPr support is enabled in your Aruba captive portal profile. This protocol passes XML-formatted metadata to the client operating system, allowing iOS (Captive Network Assistant) and Android (Captive Portal Login) to gracefully launch the login screen in a dedicated browser window.
- Prevent "Enhanced Open" (OWE) Issues: While Opportunistic Wireless Encryption (OWE) provides encryption on open networks, many legacy client devices do not support it. For public guest networks, stick to standard Open key management to maximise device compatibility.
Troubleshooting & Risk Mitigation
Even with meticulous planning, captive portal deployments can encounter common failure modes. The following troubleshooting matrix provides immediate, actionable steps for wireless engineers.
Captive Portal Troubleshooting Matrix
| Symptom | Probable Cause | Diagnostic Steps | Actionable Solution |
|---|---|---|---|
| Guest associates but the splash page does not load (Timeout/Blank Page). | Missing or incomplete Walled Garden configuration. | Attempt to ping portal.venuewifi.com from a wired device on the same VLAN. Check if the device is trying to load external resources (e.g., social login scripts) that are blocked. |
Explicitly add *.purple.ai, *.venuewifi.com, and *.cloudfront.net to the Aruba walled garden. Verify that DNS resolution is allowed in the pre-auth role. |
| Guest is redirected but browser displays an SSL/TLS Certificate Warning. | The Aruba AP is presenting an untrusted or self-signed certificate for the local redirect page. | Inspect the browser certificate details to see which certificate is being presented. | Upload a valid, trusted SSL certificate signed by a public CA to the Aruba virtual controller or Central global settings. |
| Guest completes the login form but is not granted internet access (Redirect Loop). | RADIUS communication failure between the Aruba AP and Purple servers. | Check the Aruba virtual controller logs for RADIUS timeouts or access-rejects. Run show auth-survivability or check firewall logs. |
Verify that outbound UDP ports 1812 (Auth) and 1813 (Acct) are open on your perimeter firewall. Ensure the RADIUS shared secret matches exactly on both Purple and Aruba. |
| The captive portal does not auto-popup on iOS or Android devices. | WISPr is disabled, or the AP is blocking the operating system's captive portal detection URLs. | Verify if the device can access the internet without logging in, or if it remains connected with "No Internet" and no popup. | Enable WISPr in the Aruba captive portal profile. Ensure that captive portal detection URLs (e.g., captive.apple.com, connectivitycheck.gstatic.com) are not blocked by custom pre-auth ACLs. |
| Real-time dwell-time analytics are inaccurate or missing in Purple. | RADIUS Accounting is disabled or the accounting interval is set too high. | Check the AP configuration to see if accounting is enabled and inspect the interval. | Enable RADIUS Accounting on the Aruba SSID. Set the Accounting Interval to exactly 5 minutes (300 seconds) to ensure regular session updates. |
ROI & Business Impact
Transitioning from a basic, local captive portal to an enterprise-grade WiFi intelligence platform like Purple delivers measurable business outcomes across operations, marketing, and network management.
Operational Efficiency and Scalability
Managing individual local captive portals across hundreds of retail stores, hotels, or public venues is an administrative bottleneck. Purple provides a centralised, cloud-managed console that allows IT teams to deploy, update, and audit captive portal configurations globally with a single click. This reduces configuration drift, ensures consistent branding, and slashes administrative overhead by up to 60%.
Data Monetisation and Marketing ROI
For industries like Retail and Hospitality, guest WiFi is a powerful channel for customer acquisition and engagement. Purple replaces anonymous connections with rich demographic profiles.
- Direct Integration: Purple integrates with CRM and marketing automation platforms to trigger real-time, context-aware campaigns. For example, a retail venue can trigger a personalised discount SMS the moment a loyalty customer connects to the guest WiFi.
- Measurable Footfall Analytics: By analysing RADIUS accounting data and BSSID associations, Purple provides highly accurate dwell-time, return-rate, and path-analysis reporting. This data enables venue operations directors to optimise staffing levels, evaluate window display effectiveness, and measure the direct ROI of marketing campaigns.
Cost-Benefit Analysis: Native Aruba vs. Purple Integration
| Feature / Metric | Native Aruba Local Portal | Aruba + Purple Integration | Business Impact |
|---|---|---|---|
| Centralised Multi-Site Management | Limited. Requires individual configuration per virtual controller or complex Central group mapping. | Fully Centralised. Manage thousands of venues and SSIDs from a single cloud dashboard. | Reduces IT overhead and eliminates configuration drift across distributed estates. |
| Data Capture & Compliance | Basic form capture. No built-in GDPR/CCPA consent validation workflows. | Enterprise-grade. Automated, legally-compliant consent tracking with real-time API sync to CRMs. | Mitigates legal risk and ensures compliance with global privacy regulations [4]. |
| Social Authentication | Requires custom external web development and manual API maintenance. | Out-of-the-box support for Google, Facebook, Apple, Microsoft, LinkedIn, and SMS. | Increases conversion rates by up to 40% through friction-free login options. |
| Analytics & Reporting | Basic session logs (IP, MAC, connect time). No demographic or behaviour tracking. | Rich analytics: age, gender, dwell-time, return rates, heatmaps, and cross-venue roaming. | Drives marketing ROI and provides actionable business intelligence for operations. |
Definiciones clave
Captive Portal
Una página web que se muestra a los usuarios recién conectados de una red Wi-Fi antes de que se les conceda un acceso más amplio a los recursos de la red.
Se utiliza para capturar datos de invitados, hacer cumplir los términos de servicio y presentar contenido de marketing de marca.
RADIUS (Remote Authentication Dial-In User Service)
Un protocolo de red que proporciona una gestión centralizada de Autenticación, Autorización y Contabilización (AAA) para los usuarios que se conectan y utilizan un servicio de red.
Purple actúa como el servidor RADIUS externo, autenticando a los invitados y rastreando la duración de su sesión.
WISPr (Wireless Internet Service Provider roaming)
Un borrador de protocolo que permite a los proveedores independientes de servicios de internet inalámbrico permitir que los usuarios realicen roaming en las redes de los demás utilizando un portal de inicio de sesión común.
Habilitar WISPr en los AP de Aruba permite que los smartphones modernos detecten automáticamente el Captive Portal y muestren la splash page en una ventana nativa del sistema.
Walled Garden
Un conjunto restringido de sitios web o dominios a los que un usuario no autenticado tiene permitido acceder antes de completar el proceso de inicio de sesión del Captive Portal.
Crucial para permitir que los invitados carguen los recursos de la splash page (CSS, JS, imágenes) y accedan a proveedores de inicio de sesión social (Google, Facebook) antes de ser autenticados.
BSSID (Basic Service Set Identifier)
La dirección MAC de la interfaz de radio del punto de acceso inalámbrico para un SSID específico.
Enviado en el atributo RADIUS Called-Station-Id, lo que permite a Purple mapear la ubicación física del usuario a un AP específico.
NAS-IP-Address
La dirección IP del Servidor de Acceso a la Red (el AP o controlador de Aruba) que origina la solicitud RADIUS.
Utilizado en paquetes RADIUS para identificar qué hardware físico está solicitando la autenticación.
RadSec
Un protocolo que asegura las transacciones RADIUS utilizando Transport Layer Security (TLS) sobre TCP.
Utilizado para cifrar el tráfico de autenticación y contabilización de RADIUS al atravesar redes públicas no confiables entre el AP local y la nube de Purple.
Enhanced Open (OWE)
Una extensión de Wi-Fi Certified Easy Connect que proporciona cifrado de transmisiones inalámbricas en redes abiertas sin requerir una contraseña.
Puede causar problemas de compatibilidad con dispositivos de invitados más antiguos; se recomienda la seguridad Open estándar para los Captive Portals públicos.
Ejemplos resueltos
An enterprise wireless engineer is deploying guest WiFi across a national retail chain with 150 stores. Each store has 3-5 Aruba Instant APs managed via Aruba Central. The marketing team requires a branded captive portal with Facebook and Google social login options, and the compliance team mandates that guest traffic must be completely isolated from the store's Point-of-Sale (PoS) network. How should this be architected and configured?
- Segmentación de red: Asigne el SSID de invitados a la VLAN 100 en los AP de Aruba. Configure los puertos de los switches locales como puertos troncales, permitiendo la VLAN 100. En el firewall de la puerta de enlace de la tienda, configure la VLAN 100 con un alcance DHCP y una política NAT solo de salida. Aplique una ACL en el firewall para descartar todo el tráfico desde la VLAN 100 hacia la VLAN de PoS (VLAN 10).
- Configuración de RADIUS y del portal en Aruba Central: Cree un nuevo SSID llamado 'Store-Guest' en la VLAN 100. Establezca la seguridad en 'Visitors' y la Splash Page en 'External Captive Portal'. Agregue el servidor RADIUS principal de Purple (34.94.146.135) y el servidor secundario (34.94.183.201) con los puertos 1812/1813. Habilite el registro de RADIUS (RADIUS Accounting) con un intervalo de 5 minutos.
- Walled Garden: Configure el walled garden en Aruba Central para incluir: *.purple.ai, *.venuewifi.com, *.cloudfront.net (para el núcleo de Purple) y los dominios de inicio de sesión social: *.google.com, *.googleapis.com, *.gstatic.com (para Google) y *.facebook.com, *.fbcdn.net, connect.facebook.net (para Facebook).
- Pruebas: Conecte un dispositivo de prueba a 'Store-Guest', verifique que el DHCP asigne una IP en la VLAN 100, confirme que el navegador redirija al Captive Portal de Purple a través de HTTPS, complete el inicio de sesión de Facebook y verifique que se otorgue acceso a internet mientras que los recursos internos de PoS permanezcan completamente inaccesibles.
A stadium venue with 50,000 seats is running Aruba Central on AOS-10 with high-density AP-555 access points. During peak event hours, thousands of users attempt to connect to the guest WiFi simultaneously. The IT director is concerned about the performance impact of captive portal redirects on the virtual controller and wants to ensure the authentication process is as fast and resilient as possible. What advanced configurations should be applied?
- Rol de preautenticación (AOS-10): En AOS-10, configure un rol de preautenticación dedicado llamado 'Stadium-Pre-Auth'. Aplique una ACL que permita DHCP (UDP 67-68), DNS (UDP 53) y tráfico de salida a los dominios del walled garden de Purple. Asigne este rol como el 'Pre-Authentication Role' en la configuración del SSID. Esto descarga el filtrado de paquetes del controlador central a los AP individuales, distribuyendo la carga.
- Balanceo de carga de RADIUS: En Aruba Central, habilite el balanceo de carga de RADIUS entre los servidores RADIUS principal y secundario de Purple. Esto distribuye la carga de autenticación de manera uniforme durante las ventanas de mayor ingreso de usuarios.
- Descarga del servidor (Server Offload): Habilite 'Server Offload' en la configuración del perfil del Captive Portal. Esto evita que las aplicaciones cliente que no son navegadores (como aplicaciones móviles en segundo plano, actualizaciones del sistema o dispositivos IoT) sean redirigidas repetidamente al Captive Portal externo, preservando los ciclos de CPU del AP y el ancho de banda de la WAN.
- Política de falla del Captive Portal: Establezca la 'Captive Portal Failure' en 'Deny Internet'. Aunque 'Allow Internet' parece amigable para el cliente, durante un evento de red extremo podría provocar un acceso abierto descontrolado, eludiendo los controles de seguridad y agotando los grupos de DHCP.
Preguntas de práctica
Q1. A network engineer configures a new guest SSID on an Aruba Instant AP cluster. When testing, they connect to the SSID, but instead of the branded Purple splash page, they see a browser timeout error. What is the most likely cause of this issue, and what troubleshooting steps should be taken?
Sugerencia: Think about what is required for the client device to reach the cloud-hosted splash page before authentication.
Ver respuesta modelo
The most likely cause is a missing or incomplete Walled Garden configuration, or a DNS resolution issue. Before authentication, the AP blocks all traffic except for whitelisted domains. If the Purple domains (*.purple.ai, *.venuewifi.com, *.cloudfront.net) are not in the walled garden, the client cannot load the splash page. Troubleshooting steps: 1. Verify the client device has received a valid IP address and DNS server via DHCP. 2. Attempt to resolve 'portal.venuewifi.com' from a wired device on the same VLAN to confirm DNS is working. 3. Check the Aruba AP configuration to ensure the Walled Garden whitelist is active and contains all required Purple domains. 4. Verify that the pre-authentication role allows DNS traffic (UDP port 53) to the DNS server.
Q2. During a rollout of Purple guest WiFi at a large convention center, the IT team reports that guest devices connect successfully, but they are prompted to log in again every 15 minutes. The desired behavior is for guests to remain logged in for 24 hours. Which Aruba and Purple configuration parameters should be inspected to resolve this?
Sugerencia: Look at parameters controlling session lifetime and re-authentication intervals.
Ver respuesta modelo
This issue is caused by a mismatch in session timeout or re-authentication interval settings. To resolve this: 1. Inspect the 'Reauth Interval' on the Aruba SSID security tab; it should be set to 1440 minutes (24 hours) rather than 15 minutes. 2. Check the 'Session Timeout' attribute returned by the Purple RADIUS server in the Access-Accept message. If Purple is configured with a short session lifetime, it will force re-authentication. 3. Ensure that MAC Authentication is enabled on the Aruba SSID. This allows the AP to automatically authenticate returning guests via their MAC address against Purple's database without prompting them with the splash page again during the 24-hour window.
Q3. A public-sector organization is deploying guest WiFi across multiple libraries using Aruba Central on AOS-10. The security policy mandates that all guest traffic must be encrypted over the air, but the library directors want a seamless, friction-free login experience. How can the wireless architect achieve both requirements using Aruba and Purple?
Sugerencia: Consider the differences between Open, OWE (Enhanced Open), and WPA2/WPA3-Enterprise, and how they interact with captive portals.
Ver respuesta modelo
To achieve both over-the-air encryption and a seamless captive portal experience, the architect should deploy 'Enhanced Open' (Opportunistic Wireless Encryption - OWE) with a transition mode if legacy device compatibility is required. Enhanced Open encrypts the wireless connection between the client and the AP without requiring a pre-shared key, protecting guests from passive eavesdropping. 1. Configure the guest SSID in Aruba Central with Security Level set to 'Visitors' and Key Management set to 'Enhanced Open'. 2. Enable 'OWE Transition Mode' and associate it with a standard Open guest SSID to support older devices that do not support WPA3 OWE. 3. Configure the External Captive Portal profile pointing to Purple as usual. This combination ensures that modern devices get encrypted wireless transport automatically, while still redirecting to the Purple splash page for data capture and compliance.
Continúe leyendo esta serie
Integración de Cisco WLC y Catalyst con Purple WiFi: Guía de acceso de invitados paso a paso
Esta guía autorizada detalla paso a paso la integración de los WLC Cisco Catalyst 9800 con Purple WiFi. Cubre la External Web Authentication para Captive Portals de invitados, 802.1X EAP-TLS para el acceso seguro del personal e iPSK de Cisco para la segmentación dinámica de VLAN multi-inquilino.
Integración de CommScope Ruckus con Purple WiFi: Guía de instalación y configuración
Esta guía de referencia técnica proporciona un manual de configuración definitivo para integrar arquitecturas de CommScope Ruckus con Purple WiFi. Detalla implementaciones paso a paso para Captive Portals de Guest WiFi, WiFi seguro para el personal a través de 802.1X y aislamiento de red multi-inquilino mediante Dynamic PSK de Ruckus.
Integración de Access Points Allied Telesis con Purple WiFi
Esta guía proporciona un manual de configuración completo para integrar los access points de la serie TQ de Allied Telesis con Purple WiFi. Cubre la redirección de Captive Portal externo, la autenticación RADIUS 802.1X y el direccionamiento dinámico de VLAN mediante claves privadas precompartidas (PPSK) para despliegues multi-inquilino seguros.