Components using TLS/SSL authentication and code providers

The following tables summarizes all EMI components that (in perfect situation) should use common authentication TLS library. The first table enumerates components which on one hand can provide source code for the library implementation and on another hand its contents can be reduced or completely eliminated. The latter table contains only those components that we will have to refactor to use the library.

Components providing the the authentication code

Component name PT Language Cli/Srv/Both Other notes
UNICORE Gateway UNICORE Security Java Both most work for UNICORE
UNICORE security libs UNICORE Security Java Both most work for UNICORE
VOMS VOMS java+C both  
ARC Container ARC Container C++, Python and Java bindings Both Serves as underlying code for most other ARC components
gLite Trustmanager glite java security Java Both also used in OSG, distributed also through vdt and EPEL
gLite L&B CESNET security C Both
GridSite CESNET security C Both

Other (not included above) components which shall use common authentication library

Component name PT Language Cli/Srv/Both Other notes
UNICORE XUUDB Server UNICORE Security Java Server  
UNICORE XUUDB Client UNICORE Security Java Client  
UVOS client UNICORE Security Java Client phase out - low prio
UVOS server UNICORE Security Java Server phase out - low prio
UNICORE WSRFlite UNICORE Service Hosting Java Server  
UNICORE/X UNICORE Service Hosting Java Both  
all components of: UNICORE Client and APIs Java client  
UNICORE XNJS UNICORE Target System Access Java Both (?) Big question mark here - TLS is a VERY optional and limited feature so integration need is to be investigated; low prio
glite FTS glite data management Java Server uses glite trustmanager
glite CREAM CREAM Java Server uses glite trustmanager
glite WMS WMS? Java Client uses glite trustmanager
VOMS admin VOMS Java Server uses glite trustmanager
Argus Argus java+C both server and java clients uses both glite trustmanager and VOMS code
Pseudonymity Service gLite security Java Both server and java clients uses both glite trustmanager and VOMS code
STS gLite security Java Server in design / early implementation phase
Proxy Renewal CESNET security C Client mainly proxy handling to be addressed
arcproxy ARC security utils C++ Client combines functionality of grid-proxy-init/info, voms-proxy-init/info and myproxy tools

SLCS - removed from the list on Valery's request. Doesn't use glite trustmanager.

-- KrzysztofBenedyczak - 29-Sep-2010

Edit | Attach | Watch | Print version | History: r11 < r10 < r9 < r8 < r7 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r11 - 2010-12-18 - OxanaSmirnova
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EMI All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback