Yes, there's a default depth limit imposed on proxy chains:
http://bugzilla.globus.org/bugzilla/show_bug.cgi?id=4994
You can increase it by patching the source code; the three patches
required are at http://www.globus.org/mail_archive/csec-commit/2007/06/threads.html
It has also been fixed in the 4.2.* series.
Charles
On Oct 20, 2008, at 9:49 PM, Wonjun Lee wrote:
Dear gt-user,
Do you know how many delegations could be available when submitting
a job?
For example, when I submit a job to gatekeeper A, the job is
submitting another
job to gatekeeper B. I used -J option (i.e. globusrun-ws -submit -
J ......).
Like this, repeating, I would like the job to be executed at
gatekeeper X.
When I tried this, I could delegate the credential and execute a job
after 4
gatekeepers. But at certain point, it makes error something like.
-------------------------
globusrun-ws: ignoring error while streaming
gsiftp://server-F.research.purdue.edu:2811/users/wjlee96/28359760-9f13-11dd-8edf-0002b365cbdc.0.stdout
:
globus_ftp_client: the server responded with an error
530 530-globus_xio: Authentication Error
530-OpenSSL Error: s3_srvr.c:2010: in library: SSL routines, function
SSL3_GET_CLIENT_CERTIFICATE: no certificate returned
530-globus_gsi_callback_module: Could not verify credential
-------------------------
Do you if this is problem of job delegatiion?
Thank you!
Wonjun
