120 likes | 128 Views
This deliverable discusses the design of an interoperability testbed for an AAA server access control device. The testbed incorporates features like RADIUS-based web authentication, VPN solutions, and a RADIUS proxy server hierarchy for scalability. Various network layouts and authentication methods are explored, including 802.1X, captive portal, and PKI-based authentication.
E N D
Deliverable H: the interoperability testbed design Klaas Wierenga SURFnet <Klaas.Wierenga@SURFnet.nl>
AAA Server Access Control Device Internet 4. 3. 5. 1. Docking Network 2. WWW-browser Web-based with RADIUS • RADIUS based Web interface authentication at the University of Tampere The Finnish are scaling their solution by using a hierarchy of RADIUS proxy servers for their national infrastructure
Dockingnetwork Dockingnetwork VPN-Gateways VPN-Gateways Campus Network Campus Network G-WiN G-WiN Intranet X Intranet X DHCP, DNS, free Web DHCP, DNS, free Web • Wbone – VPN roaming solution to 4 universities / colleges in state of Bremen. VPN • SWITCHmobile – VPN solution deployed at 7 universities across Switzerland. • A "virtual campus" initiative in Lisbon, and been testing and developing a VPN & PKI infrastructure. PPPoE – University of Bristol
Cross-domain 802.1X with VLAN assignment Supplicant Authenticator (AP or switch) RADIUS server Institution A RADIUS server Institution B User DB User DB Guest piet@institution_b.nl Internet Guest VLAN Employee VLAN Central RADIUS Proxy server Student VLAN Authentication at home institution, 802.1X , TTLS (SecureW2), (proxy) RADIUS. One time passwords are also transmitted via SMS to guest users. A RADIUS Hierarchy is proposed to scale this to a European wide solution.
Current status • Characteristics identified as • 802.1X - “The future”, easy to scale, secure but cutting edge, thus expensive. • VPN - Widely available, expensive, secure & hard to scale. • Web based – cheap, widely available, easy to scale, but not secure. • Preliminary selection for inter-NREN roaming – in draft, conclusions are • No national solution meets all the requirements. • The group has chosen not to consider the following • Local VPN access. • PKI • An architecture that supports the various national solutions is needed, a three stream approach is recommended…
Controlled Address Space for VPN Gateways • Design and work plan documentation underway. • Interoperability tests of VPN to RADIUS proxy hierarchy agreed. • Further work to follow.
Radius proxy hierarchie UNI-C FUNET DFN SURFnet UKERNA CESnet FCCN CARnet RADIUS Proxy servers connecting to a European level RADIUS proxy server RedIRIS GRnet
Integration? • 802.1X • Secure SSID • RADIUS • Web-based captive portal • Open SSID • RADIUS • PKI-based • Open SSID • No RADIUS
Conclusions • It is possible to create an interoperable solution • It’s not that hard – especially when you use delievrable H to guide you • Future will show if and how these solutions will continue to be in existence • Del. H provides also a easy upgrade path