Sorry for the lateness of this reply, but I'm not a GridFTP expert so
I was hoping someone who knows more than me would respond.  That said,
I wouldn't expect this to work since AFAIK GridFTP does not support
access control based on X.509 extensions such as VOMS attribute
certificates or SAML tokens.  AFAIK GridFTP only supports
identity-based access control, that is, the familiar gridmap file.

Hope this helps, and please, if you find that what I've said is wrong,
please followup with more accurate information since I, too, am
interested in this topic.

Tom Scavo
NCSA

On Tue, Sep 23, 2008 at 8:09 AM, Vipul Borikar <[EMAIL PROTECTED]> wrote:
> Hello all,
>     I am trying to access pre-WS components of Globus like gridFTP through
> VOMS credential.
> For this, I have installed the following :
> #GT4.0.7
> #VOMS server 1.8 and used it to generate VOMS certificates.
> #LCAS, LCMAPS binary RPM for Red hat is taken from the link
> http://grid-deployment.web.cern.ch/grid-deployment/download/RpmDir/WP4/
> The components installed are :
> # edg-lcas_gcc3_2_2-voms_plugins-1.1.22-1
> # edg-lcas_gcc3_2_2-1.1.22-1
> # edg-lcmaps_gcc3_2_2-0.0.30-1
> # edg-lcmaps_gcc3_2_2-voms_plugins-0.0.30-1
> # edg-lcmaps_gcc3_2_2-basic_plugins-0.0.30
> # org.glite.security.lcas-lcmaps-gt4-interface libraries from eticsoft
>
>
> Then I generate VOMS credential through voms-proxy-init in the standard
> location.
> Then when I give the command
>
> globus-url-copy -dbg gsiftp://192.168.61.197/home/globususer/tot
> file:///home/globususer/wall/tot1
>
> I get the error :
> debug: starting to get gsiftp://192.168.61.197/home/globususer/tot
> debug: connecting to gsiftp://192.168.61.197/home/globususer/tot
> debug: response from gsiftp://192.168.61.197/home/globususer/tot:
> 220 192.168.61.197 GridFTP Server 2.7 (gcc32dbg, 1204845443-63) [Globus
> Toolkit 4.0.7] ready.
>
> debug: authenticating with gsiftp://192.168.61.197/home/globususer/tot
> debug: fault on connection to gsiftp://192.168.61.197/home/globususer/tot:
> an end-of-file was reached
> debug: data callback, error an end-of-file was reached, buffer 0xb7deb008,
> length 0, offset=0, eof=true
> debug: operation complete
>
> error: an end-of-file was reached
> globus_xio: An end of file occurred.
>
> The file gets created with 0 bytes.
> Has anyone tried this?
> Attaching the file lcas_voms.mapfile and the voms-proxy-info
>
> Thanks & Regards,
> Vipul Borikar
> CDAC Banglore,India

Reply via email to