Aruba Central

Download this guide ⬇

Introduction

Scope and Purpose

Thank you for purchasing the Trusted WiFi solution. This document is a hardware configuration guide describing how to setup Aruba Central for a Trusted WiFi Passpoint service.

• For more information on how to setup an end-to-end Trusted WiFi Passpoint service, please refer to the Trusted WiFi Passpoint Administration Guide.

• For complete information on how to setup Aruba Central, please refer to the vendor’s original documentation.

Documentation Conventions

Passpoint Overview

Passpoint – also known as Hotspot 2.0 – is an industry-wide next generation approach to public internet access driven by the Wi-Fi Alliance that brings the following benefits:

• Frictionless onboarding and roaming, thanks to a one-time registration followed by automatic access to interconnected hotspots

• More secure and private Wi-Fi connections, compared with general visitor networks

Passpoint is based on the IEEE 802.11u standard, which is a set of protocols enabling cellular-like roaming. Following the initial enrollment, frequent users such as visitors, guests or employees bypass repeated logins, forms and passwords, as their mobile devices automatically join the Wi-Fi subscriber service when they return to a venue or roam between inter-linked Passpoint enabled hotpots and providers, while being better protected against potential cyber threats.

If a device supports 802.11u and is enrolled to a service, it automatically communicates with the Wi-Fi infrastructure via the access points to discover the network SSID and connects securely to it by presenting its access credentials. Upon successful authentication, the device is provisioned with Passpoint standards-based management objects - known as Per-Provider Subscription Management Objects (PPS-MO).

GlobalReach - an ASSA ABLOY company - has been involved with Passpoint since its inception and even contributed to the creation and initial pilot testing of the standard. As a result, it is one of the few trusted worldwide experts on this topic, with a proven platform backed by real-world operational experiences at scale.

The best user experience is to offer Passpoint through a customer/brand mobile app integration, as it further simplifies the onboarding process, while incentivizing app downloads and customer loyalty, leading to further engagement and monetization opportunities. To this effect, Trusted WiFi offers a Software Development Kit (SDK) for easy app integration.

End-to-End Service Components

Implementing an end-to-end Trusted WiFi Passpoint service requires a combination of the following software and hardware components:

• Trusted WiFi Passpoint: the core services are offered and managed centrally via the Trusted WiFi Passpoint Module (hosted and operated by GlobalReach). Following an initial setup performed by the GlobalReach Operations team, Managed Service Providers (MSPs) can then add sites to customer realms and monitor the solution.

• Customer Realm: the service requires connectivity to a realm including domain, security certificate and private key, as well as the database holding the users’ Personally Identifiable Information (PII). It is the responsibility of the Identity Provider – typically the customer/brand – to make this part available.

• Mobile App: the best user experience is to offer Passpoint through a customer/brand mobile app integration. Trusted WiFi offers a Software Development Kit (SDK) for easy implementation. It is the responsibility of the app owner – typically the customer/brand – to perform the integration.

• Local Networks: the local networks must be compliant with Passpoint (Hotspot 2.0). – Most recent   Wi-Fi access points and controllers from major vendors support Passpoint today, however older models or products from more exotic manufacturers might not do. The configuration of the local infrastructure is typically handled by the Managed Service Providers (MSPs).

• User Devices: the subscribers’ mobile devices (belonging to visitors, guests, employees, etc.) must be compliant with Passpoint (Hotspot 2.0) – All recent iOS and Android-based smartphones or tablets support Passpoint today, however older models or products running less popular operating systems might not do. Laptops compatibility is also more erratic. It is therefore essential to maintain a traditional onboarding service in parallel with Passpoint to handle non-compatible devices.

High-Level Topology

The diagram below illustrates the high-level topology for the end-to-end Trusted WiFi Passpoint service:

Glossary

The following is a glossary of the most common terms used regarding this solution.

ARUBA CENTRAL CONFIGURATION

Supported Versions

Aruba Central supports Passpoint on AOS v10. Aruba recommends upgrading to the latest version of AOS.

Note

Please refer to the Aruba documentation for further information on which versions of OS code supports which APs.

Warning

The configuration of the RADIUS is documented using the WLAN configuration option. The alternative method, under Configuration > Authentication, is not covered in this document.

Prerequisites

It is assumed the following prerequisites are met before configuring Aruba Central for a Trusted WiFi Passpoint service:

• A supported Aruba Central running version 10.0 or greater, activated and licensed.

• A Trusted WiFi account with operator permissions.

• A core Trusted WiFi Passpoint service configured and tested.

• A property in Trusted WiFi with deployed Passpoint modules.

• A deployed and configured Wi-Fi network.

Note

This document focuses on a specific part of the Aruba Central configuration only.

• Please refer to the Passpoint Administration Guide for instructions on how to configure the end-to-end Passpoint service.

• Please refer to the original Aruba documentation for complete instructions on Aruba Central configuration.

Warning

• The Aruba configuration is focusing on Passpoint v1.0.

• All properties must share the same NAI realm, RADIUS IP / port settings and SSID name for the Passpoint service (CustomerPasspoint).

• Each property requires a separate RADIUS secret and NAS identifier, both generated when a configuration is activated within the Trusted WiFi management platform.

Core Passpoint Settings

• Log into Trusted WiFi, then click on the Properties icon in the left menu to view the properties list.

• Select or search for the property you wish to work on. This will open its deployments page:
  

• Click on the Passpoint tile and then click on the Configuration option in the left menu to display the Passpoint settings summary as per the example below:
  

• Take note of the details for your respective installation as they will be required at a later step.

Aruba Central Configuration

SSID

• Log into Aruba Central with your credentials to display the below page:
  

• Click on Devices in the left-hand navigation menu to display the below page:
  

• Click on one of the Access Points to display a detailed summary, which also changes the left navigation menu. Click on the Device tab on the left and select the WLANs tab:
  

• Click on + Add SSID on the bottom of the screen to display the below page:
  

• Enter the Name of the new Passpoint SSID, (for example: CustomerPasspoint) and click Next.

Client IP and VLAN Assignment

• In the WLANs tab>VLANs tab below:
  

• Set the Client IP Assignment to External DHCP server assigned and the Client VLAN Assignment to Native VLAN, then click Next.

Security and RADIUS

• In the Security tab below:
  

• Move the Security Level slider to Enterprise and set the Key Management to WPA Enterprise from the drop-down list.

• Click on the + to the right of the Primary Server drop-down list to display the page below:
  

• Complete the fields as per the description below:

  Field	Description
  Server Type	RADIUS.
  Name	Enter a name.
  IP Addresses/FQDN	Enter the <Primary RADIUS IP> from Trusted WiFi.
  NAS Identifier	Enter the <NAS Identifier> from Trusted WiFi.
  Auth Port	Enter the < RADIUS Authentication Port> from Trusted WiFi.
  Accounting Port	Enter the < RADIUS Accounting Port> from Trusted WiFi.
  Shared Secret	Enter the < RADIUS Shared Secret> from Trusted WiFi.
  Confirm Shared Secret	Re-enter the < RADIUS Shared Secret> from Trusted WiFi.

• Click OK to save, repeat this operation for the Secondary Server and click OK to save.

• Back to the Security tab, ensure the RADIUS server you just configured is selected as the default and click on the Advanced Settings option at the bottom of the screen:
  

• Scroll down to the Passpoint Server Profile option:
  

• Click on the Manage Passpoint Services option, then click on + Add Profile at the bottom of the screen to display page below:
  

• Enter the Name of the Passpoint profile, then click on Access Network to display the options below:
  

• Complete the fields as per the description below:

  Field	Description
  Name	Name of the Passpoint profile.
  Domain Name	Enter the domain name.
  Network Type	Select free-public from the drop down list.
  IPv4	Select free-public from the drop down list. Select public from the drop down list.

• The other fields can be left as they are.

• Click Identity Provider and then +Add to display the page below:
  

• Complete the fields as per the description below:

  Field	Description
  Realm Name	Select the realm name.
  Realm Encoding	Select UTF-8 from the Realm Encoding drop-down list.
  EAP Method	Select eap-ttls from the drop-down list.

• The other fields can be left as they are.

• Click on OK to return to the Add Profile screen and then click Save and X to the Manage Passpoint Service screen pop-up.

• Ensure you select the newly created Passpoint Service Profile, as shown below:
  

• Click Next to the Access tab and click Next again to the Summary tab:
  

• Click Finish. This WLAN configuration can now be applied to any predefined group of APs.