Middleware argus interoperability
Jump to navigation
Jump to search
Starting from March 2013, as part of the UMD quality criteria products requiring authentication are tested for the interoperability between argus and other middleware components. The following tables collects the products tested so far during the UMD software provisioning process.
UMD-2
Product name | Version | Released in UMD update # | Argus support | Comments | GGUS ticket |
---|---|---|---|---|---|
DPM | 1.8.6 | UMD2.4.0 | YES | Not tested yet | |
dCache | not tested yet | ||||
VOMS | Not available in production | ||||
SRM | YES | Available in production | |||
CREAM-CE | not tested yet |
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 |