Re: [Captive-portals] Arguments against (any) Capport "API"

[David Bird <dbird@google.com>]

Eduroam, at the end of the day, is not unlike Boingo or iPass. They went out and negotiated roaming contracts with hotspot providers, in this education organizations. Of course, part of that negotiation was the T&C acceptance/compliance. While this is a great example of an aggregate network and a great use-case for 802.1x, it doesn't offer much guidance for public access in general. 

On Wed, Apr 5, 2017 at 1:14 AM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:

> On 5 Apr 2017, at 05:19, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>
> What about an enterprise SSID that allows anyone to connect to it, but the only thing you get is a captive portal. After you've accepted terms of service and entered username/password, this is now somehow provisioned into your device as 802.1x credentials and you then disconnect and reconnect with these new credentials, which gives you access as long as these credentials are valid?

That’s eduroam, used by at least tens of millions of people at higher education and research organisations in over 70 countries, supporting roaming between all participants by default.  Except it skips the captive portal bit; indeed captive portal is expressly forbidden; you purely use 802.1x.  The T&C bit is implicit through your account being provided, and accepting the T&C/AUP of the university/NREN when you sign to get that.

Tim