Middleware argus interoperability
Jump to navigation
Jump to search
UMD-2
Product name | Version | Released in UMD update # | SHA-2 support | RFC proxies support | Comments | GGUS ticket |
---|---|---|---|---|---|---|
globus-gsissh | 5.5.4 | UMD2.4.0 | YES | YES | ||
DPM | 1.8.6 | UMD2.4.0 | YES | Not tested yet | ||
LFC | 1.8.6 | UMD2.4.0 | YES | Not tested yet | ||
globus-myproxy | 5.9.1 | UMD2.4.0 | YES | Not tested yet | ||
VOMS | 2.0.10 | UMD2.4.0 | YES | NO | VOMS rfc proxies only work with SHA1 user certificates | GGUS #91389 (On Hold until EMI3) |
UI | 2.0.1 | UMD2.3.0 | YES | YES | Available in production | |
globus-GridFTP | 5.2.3 | UMD2.4.1? | YES | Not tested yet | Not available in production yet | |
globus-gsisshterm | 1.3.4 | UMD2.4.1? | NO | YES | Uses a jGlobus version not compatible with SHA2 | GGUS #90815 |
UMD-3
Product name | Version | Released in UMD update # | SHA-2 support | RFC proxies support | Comments | GGUS ticket |
---|---|---|---|---|---|---|
VOMS | 3.0.0-1 | UMD3.0.0? | YES | PARTIAL | VOMS rfc proxies work with SHA1 and SHA2 user certificates.
RFC proxies are created but are not usable |
https://savannah.cern.ch/bugs/?101122 |
UI | 3.0.0-1 | UMD3.0.0? | YES | YES |
VOMS rfc proxies work with SHA1 and SHA2 user certificates. NOTE: CREAM 2 is still not compatible with RFC proxies |
|
ARGUS | 1.6.0 | UMD3.0.0? | YES | YES | ||
WN | 3.0.0-1 | UMD3.0.0? | YES | YES | (uses same VOMS clients as UI) | |
LFC | 1.8.6 | UMD3.0.0? | YES | YES |