170 likes | 288 Vues
This project outlines a system for authenticating and authorizing roaming users without prior registration, allowing secure IP access to both local and remote networks. The infrastructure features both MAC address and web captive portal authentication methods, supporting various client operating systems and hardware types. The server, operating on Red Hat 9, utilizes FreeRadius for authentication and NoCat for captive portal management. Future developments aim to enhance security with 802.1x integration and improve infrastructure by adding a Radius server.
E N D
INFN Trip Project Mirko Corosu for TRIP WORKGROUP HEPiX 2004 - Brookheaven
Aim of the project • Authentication and authorization of roaming users without any previous registration. • The system should provide: • IP access : • To users LAN • To local LAN • Security • Compatibility to local infrastructure • Independence to user OS and hardware
Authentication/authorization methods • We started to analyze two kind of methods: • Mac address authentication (layer 2) • Web captive portal (layer 3)
Software components • Server side: • Red Hat 9 operating system • FreeRadius-1.0.1: open source radius authentication server • NoCat-0.82: web captive portal for wireless and wired network • Apache-1.3.27 + mod-SSL • Client side tested: • RedHat 9 and Fedora Core, Windows 2k/XP • Mozilla and Internet Explorer browser for web authentication
Wireless access points • Cisco Aironet 1100 supports: • 802.1q protocol (VLAN tagging) • Multiple SSID • Mac address authentication • 802.1x authentication (EAP/TLS) • WEP encryption
NoCat captive portal • Captive portal application written in PERL • Two elements: • Gateway: changes iptables rules on a Linux based gateway/firewall. • Authentication server: collection of PERL cgi’s which perform the web authentication of the user and tell the gateway to open or close firewall TCP ports. • There can be multiple gateway that interact with a single authentication server
Web authentication Association request Association allowed IP address request IP address allowed NOCAT gw NAT/FW (iptable) WAN Apply iptables rule to open firewall Browser is redirect to NOCAT authentication page certificate or username /password MySQL (NOCAT) authentication confirmed Browser session NIS/K5/AFS Connection to requested page AFS (WAN) NOCAT auth HTTP radius (NOCAT) X.509 certificate (Mod-SSL) radius vs Local db radius vs PAM Private network NIS/K5/AFS/MySQL DHCP AFS/CA auth RADIUS
Web authorization/authentication infrastructure • Features: • Supports different authentication mechanism (Linux PAM, X.509 Certificates, Radius, MySql, ldap) • Independence to client OS and hardware • Problems: • No encryption • Difficult to grant different privileges based on users credentials
Mac address authentication • Features: • Useful to discriminate local users (registered mac address) from others • Possibility to use different VLAN • Problems: • No encryption • Doesn’t support other authentication/authorization method
Solution • Try to integrate different authentication methods
First step: use one machine WAN Private network NIS/K5/AFS/MySQL auth DHCP NOCAT gateway NAT/FW (iptable) AFS/CA auth NOCAT auth HTTP RADIUS
Second step: MAC/Web authentication Association request MAC authentication via radius server LAN2 NOCAT MAC is present in database MAC not present in db; user is put in the NOCAT lan NOCAT + httpd iptables (NAT/FW) radiusd dhcpd radius check dhcpd database LAN1 Local users Filtered access to local network Full access to local network
Feature of web/mac authentication • Supports different authentication methods • Indipendence to user OS/HW • Different access levels • One problem: • Connection not encrypted • Solution: 802.1x protocol
802.1x protocol • Features: • Encrypted connection • Supports different authentication method • Problems: • Problem on some OS’s and hardware
Current project goals • Web + MAC address authentication infrastructure • Automatic installation of the authentication server
Future development • 802.1x integration • Creation of a Radius server infrastructure to extend authentication mechanism to all INFN sections or • Put TRIP infrastructure in Kerberos 5 INFN framework • Test of other web captive portal (TINO)
Documentation • Documentation and software can be found at http://trip.ge.infn.it/