#208 Certificate upload with and without RFC option

[Karolis (EGI)]

Hi,

If user is using RFC complaint proxy at SSP portal upload form he ticks RFC
box, then gUSE is using it's own RFC implementation.

Output produced after upload:

"Message: Upload successful."

If user is not using RFC complaint proxy at SSP portal upload form he does not
tick RFC box, then gUSE is using "voms-proxy-init".

Output produced after upload:

Message: Upload successful.
Your identity: /O=dutchgrid/O=users/O=egi/CN=Karolis Eigelis
Creating proxy
..................................................................................................................................
Done
Proxy Verify OK
Your proxy is valid until: Sat Jul 12 11:04:48 2014
A proxy valid for 3398 hours (141.6 days) for user ekar now exists on
myproxy.hellasgrid.gr.

Also please notice in the output the number of hours created, which is wrong -
default value in the upload web form is 10, so how it became 3398 hours ?

the problem is that if using current RFC complaint proxy produced by gUSE and
not "voms-proxy-init" it randomly fails on submitting the job to authenticate
to
VOMS or WMS or gives various errors for DCIBridge.

Solution could be either improve or remove it.

e.g. gUSE could use in both cases "voms-proxy-init", and give
the "--rfc" parameter to the "voms-proxy-init" if RFC box is ticked.

Regards,
Karolis

[Gabor Hermann]

Dear Istvan, please comment the issue