170 likes | 365 Views
PAPI based federation as a test-bed for a common security infrastructure in EFDA sites. R. Castro , J. Vega , A. Portas, D. R. López, S. Balme , J.M. Theis , P. Lebourg , H. Fernandes , A. Neto , A. Duarte , F. Oliveira , F. Reis , K. Purahoo , K Thomsen , W. Schiller , J. Kadlecsik. Index.
E N D
PAPI based federation as a test-bed for a common security infrastructure in EFDA sites R. Castro, J. Vega, A. Portas, D. R. López, S. Balme, J.M. Theis, P. Lebourg, H. Fernandes , A. Neto , A. Duarte, F. Oliveira , F. Reis , K. Purahoo , K Thomsen , W. Schiller , J. Kadlecsik
Index • Motivation • Federation as solution • PAPI • PAPI for Federation • EFDA Federation • Future lines
Motivation • Security framework for service access control • Necessity in organizations of sharing resources for collaborative work • Transparency • Simple management
Federation • Set of organizations sharing resources based on: • Trust • Policies agreements • An Authentication and Authorization system • Requirements • Single Sign On • Secure Access • Users Mobility • Simple Management and Scalability • Transparency • Common tools compatibility
PAPI system • Distributed AA system • Authentication Server (AS) • Point of Access (PoA) • Group Point of Access (GPoA) • PAPI Front-End Server • Authentication modules • X.509 certificates • LDAP • SQL • Local file
Authentication data Temporal Signed-URLs Signed-URL Encry-cookie S1 Encry-cookie S2 Encry-cookie Signed-URL Encry-cookie How does it work? Authentication Server PoA HTTP Server S1 HTTP Client PoA HTTP Server S2
Group Point of Access • One credential -> Many resources HTTP Client GPoA 1 1 2 Point of Access Point of Access GPoA 2 Point of Access Point of Access
Front-End Service • Easy services integration • One XML configuration point HTTP Server GPoA PoA PoA HTTP Service PoA HTTP Server
PAPI for Federation • Fulfills federation requirements • Trust among components based on PKI • Client types: • Common web browsers • JAVA applications (JWS supported) • Standard java library (version > 1.5) • RT-HTTPClient • [http://www.innovation.ch/java/HTTPClient/] • jakarta commons-httpclient • [http://jakarta.apache.org/commons/httpclient/] • Service types: • Web page servers • Application servers (example Tomcat) • Wiki integration (XWIKI)
Federation Architecture • Easy management
Federation Mechanism User Repository Federation WAYF Federation GPoA Federated Organization ? ? Federated Serice Authentication Server Federated Organization Web browser Federated Serice User’s home Organization
EFDA Federation • Starting decision: meeting 28/11/2006 in JET
Coordination • EFDA wiki site • RP -> Authentication and Authorisation Systems • Mail list • efda-federation@ciemat.es • EFDA Jabber
Current State • CEA • Federated, Attributes, Java Apps • EFDA wiki federated !!! • CIEMAT • Federated, Attributes, Java Apps • EFDA • Federating • HAS/KFKI • Federating, Integrating PAPI and Shibboleth • IST • Federated, Attributes, Java Apps • JET • Federated, Attributes, Java Apps
Future lines • Evaluation of results of PAPI - Shibboleth integration • New authentication mechanisms • New services available in the federation • Agreements on polices • Evaluate new coordinated technologies taking advantage of trust and policy agreement
Thank you for your attention R. Castro, J. Vega, A. Portas, D. R. López, S. Balme, J.M. Theis, P. Lebourg, H. Fernandes , A. Neto , A. Duarte, F. Oliveira , F. Reis , K. Purahoo , K Thomsen , W. Schiller , J. Kadlecsik