GridFTP Service

For large file transfers between different sites we generally recommend our UFTP Service. Another option is GridFTP, which is installed on our JUDAC system (as client and server) allowing transfers to different target sites and data centers where the service is also available.

There is some preliminary task to do if you have not used GridFTP before. You will need a personal X509 certificate in order to authenticate with GridFTP servers. If you do not have an X509 grid user certificate already, please go to our Grid registration authority or any Grid registration authority near you and request a certificate.

After you have received the signed certificate from the certificate authority, export it (in .p12 format) from your browser and save it in your $HOME on JUDAC. Keep the password of the exported keystore in mind. Execute the following commands:

$ mkdir ~/.globus
$ mv YourExportedKeystore.p12 .globus/usercred.p12
$ chmod 600 .globus/usercred.p12

Now you should be able to create a proxy certificate from the stored keystore and the selected password (if you set the name to usercred.p12) by the following command:

$ grid-proxy-init

Before accessing a GridFTP server at your preferred target site (JSC, LRZ, HLRS, etc.), you need to register the DN (Distinguished Name) of your X509 certificate. Send that DN to the responsible admin of the site where the GridFTP server is running. E.g. for JSC’s JUDAC to email:

One option to retrieve the DN from your certificate would be the following command:

$ openssl pkcs12 -in usercred.p12 -nodes | openssl x509 -noout -subject

Once registered, you should be able to transfer data between two sites by using GridFTP.


Pushing data from client (globus-url-copy) at JUDAC to a server at HLRS Hazelhen:

$ globus-url-copy -vb -p 4 ↲

Pulling data from JUDAC server to some client at a different site:

$ globus-url-copy -vb -p 4 ↲


Please contact in case of any issues regarding GridFTP.