1021563 - Passpoint / Hotspot 2.0 support in API

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Wifi, defect)

Description

[Stefan Winter]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release)
Build ID: 2014050900

Steps to reproduce:

The command-line tool wpa_supplicant which Firefox OS uses for its WiFi
connectivity supports IEEE 802.11 Interworking / Hotspot 2.0 / Passpoint since
version 2.0.

It is not possible yet to configure Passpoint networks, neither via Firefox OS UI, nor
is there an API for pushing the settings down to wpa_supplicant.

This feature request is about an API to configure Passpoint. This would probably be a feature of the API about WiFi management (bug #917101). The feature request is not about UI support; most other Passpoint devices don't have UI either as it would necessarily look convoluted; but automated provisioning via scripts and APIs is common.

Examples of devices supporting Passpoint are Apple iOS and some releases of Android devices (on select Samsung Galaxy devices).

For reference, below is what needs to be done on the wpa_supplicant backend side of things; the API capabilities would have to wrap around that:

One thing is to enable IEEE 802.11u + HS20. They could be enabled in one
go; there is little benefit in turning on just one. So an API call like, say,

WIFI_API_enable_passpoint(TRUE/FALSE);

would do the following in wpa_supplicant.conf:

interworking=1
auto_interworking=1
hs20=1

Passpoint disregards the SSID when joining networks, it uses "Consortium Identifiers" and "MCC/MNC" and "NAI realm" identifiers to verify whether the network is usable with the user's credentials.

So, WiFi API needs to store besides/instead of the SSID the following properties:

WIFI_API_set_compatible_consortium_list(array of strings: the consortium oi's);
WIFI_API_set_compatible_mncmcc_list(array of strings: the supported MNC/MCC combos);

If "passpoint" is true, the network is forcibly a WPA2/AES Enterprise network using EAP credentials; so re-use the eap wifi API calls to create a
cred { } block in wpa_supplicant.conf. cred { } blocks look very similar to network { } blocks, but contain NO ssid, instead contain the consortia and MNC/MCC list. They can also contain a "domain" field (set identical to the EAP credential's realm part) and a "nai_realm" field (again, set identical to the EAP credential's realm part).

I realise that this whole Hotspot 2.0 / Passpoint stuff is relatively new. I'm
happy to get people up to speed if there is need.

Comment 1

[BMO Automation]

Firefox OS is not being worked on