Hi @OsureRonald_dca3 Sorry for the delay - just had to take care of outstanding tasks from last week.
Can you let me know what version of the voms clients you are using ? Mine is :
voms-proxy-init v. 3.0.6 (voms-api-java/3.0.5 canl/1.3.3)
and with this I can reproduce the error :
voms-proxy-init --vomses /etc/vomses/sagrid-voms.sagrid.ac.za --voms sagrid
Enter GRID pass phrase for this identity:
Contacting voms.sagrid.ac.za:15001 [/DC=EU/DC=EGI/C=ZA/O=Hosts/O=ZA-UFS/CN=voms.sagrid.ac.za] "sagrid"...
Error contacting voms.sagrid.ac.za:15001 for VO sagrid: Received fatal alert: handshake_failure
Error contacting voms.sagrid.ac.za:15001 for VO sagrid: peer not authenticated
Error contacting voms.sagrid.ac.za:15001 for VO sagrid: REST and legacy VOMS endpoints failed.
None of the contacted servers for sagrid were capable of returning a valid AC for the user.
User's request for VOMS attributes could not be fulfilled.
This looks like an error on the server side :
LOG_INFO:REQUEST:Run (vomsd.cc:788):SSL Handshake error
LOG_INFO:REQUEST:Run (vomsd.cc:795):no shared cipher [err:336109761,lib:SSL routines,func:SSL3_GET_CLIENT_HELLO(file: s3_srvr.c+1387)]
After some investigation, I found that there were incorrect ciphers set on the server (SSLv3 should have been disabled), and the voms certificate had been corrupted. I've fixed it and now the proxy is issued correctly