Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
fts-rest 3.4.1
-
Security Level: Public Data (This ticket is visible to anyone on the internet and will be indexed by search engines)
-
None
Description
the FTS REST operation /delegation/<dlgid>/voms should request an RFC proxy to VOMS if the already delegated proxy is RFC.
I have this problem on the new WebFTS+Kipper which i moved to RFC and in case i use the browser certificate for the delegation i end up with proxy like this:
- voms-proxy-info -file proxy_new -all
subject : /DC=ch/DC=cern/OU=Organic Units/OU=Users/CN=amanzi/CN=683749/CN=Andrea Manzi/CN=1463476583594/CN=proxy
issuer : /DC=ch/DC=cern/OU=Organic Units/OU=Users/CN=amanzi/CN=683749/CN=Andrea Manzi/CN=1463476583594
identity : /DC=ch/DC=cern/OU=Organic Units/OU=Users/CN=amanzi/CN=683749/CN=Andrea Manzi/CN=1463476583594
type : proxy
strength : 1024 bits
path : proxy_new
timeleft : 11:55:23
key usage : Digital Signature, Key Encipherment
=== VO dteam extension information ===
VO : dteam
subject : /DC=ch/DC=cern/OU=Organic Units/OU=Users/CN=amanzi/CN=683749/CN=Andrea Manzi
issuer : /C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms.hellasgrid.gr
attribute : /dteam/Role=NULL/Capability=NULL
timeleft : 11:55:23
uri : voms.hellasgrid.gr:15004
which is not valid