70 likes | 221 Views
A-Select: Hitchhiking in authentication space. Internet2 Member Meeting, Los Angeles, 30 October 2002. Ton Verschuren Innovation Management – SURFnet – NL Ton.Verschuren@SURFnet.nl. Rationale for A-Select. A-Select is a weblogin system like pubcookie Separation between authN and authZ
E N D
A-Select: Hitchhiking in authentication space Internet2 Member Meeting, Los Angeles, 30 October 2002 Ton Verschuren Innovation Management – SURFnet – NL Ton.Verschuren@SURFnet.nl
Rationale for A-Select • A-Select is a weblogin system like pubcookie • Separation between authN and authZ • Better security thru stronger (local) authN • New authN methods shouldn’t bother apps • We’re looking for authN means that users already have: hitchhiking! • Differentiate between various levels of assurance
A-Select overview Application User Filter A-Select Agent Local A-Select Server Remote A-Select Server Local Authentication Service Providers Remote Authentication Service Providers UDB
Supported AuthN Service Providers (ASPs) • V 1.1 (now): • IP address • U/p thru RADIUS • Internet banking (banking card) • SMS (mobile phone) • V 1.2 (Nov/Dec): • LDAP • V 2.0 (?): • PKI
Implementation • A-Select server: Java • Apache + Tomcat • Crypto: Cryptix • SHA1 hashes + RSA signatures • Filters for Apache and IIS • Memory cookies: • Ticket granting ticket (for SSO) • Application ticket • Redirection to ASP • UDB: • JDBC • LDAP (v1.2) • SSL recommended but not required
Applications Authorisation Systems Back Office ? Authentication Systems What’s next: standardising on APIs? webISO
More info • Soon on www.a-select.org • Functional & technical design + API • And now…a demo!