Bug 5621 - gram2 credential refresh problems in 4.0.5
: gram2 credential refresh problems in 4.0.5
Status: RESOLVED WONTFIX
: GRAM
gt2 Gatekeeper/Jobmanager
: 4.0.5
: Macintosh All
: P2 normal
: ---
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2007-10-17 12:36 by
Modified: 2012-09-12 09:18 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2007-10-17 12:36:31
Dear all,

I am experiencing the following problem in GT4.0.5 using the prews GRAM.
If my server tries to refresh the credentials for a long running job before the
proxy expires (it uses its own host credentials), it gets back the following
error from the jobmanager: an authentication operation failed. However, I am
sure that the credential used is valid and is correct because the server is
downloading a fresh proxy from a MyProxy server, and the credential is obtained
through gss_import_cred(). After importing the credential, it is  checked using
gss_inquire_cred(), gss_display_name() etc to validate the distinguished name
and the credential lifetime.

I am using the gcc32dbgpthr flavor, and refreshing the credentials using
globus_gram_client_register_job_refresh_credentials().

In particular, besides setting the credential to be used as the second
argument, I am also setting the third argument which is the globus gram client
attribute. The attribute is at first initialized using
globus_gram_client_attr_init(), then I use
globus_gram_client_attr_set_credential() to set for the attribute the same
credential I will use for the refresh operation (the same used for the second
argument).

I am sure that the distinguished name associated to the credential is in the
remote machine grid-mapfile and is authorized (the same proxy downloaded from
Myproxy is ok to submit a job to the remote machine). I am also sure that the
jobid (the irst argument of the
globus_gram_client_register_job_refresh_credentials() function) is correct
(using globus-job-status I see the job is active).

The same code was working without any problems in previous GT releases.
Any clue about?

I am i doing something wrong due to changes in the GT4.05 prews GRAM?

Thank you in advance,
Massimo
------- Comment #1 From 2007-10-23 14:34:13 -------
Just a short note: There's a test in Gram (globus_gram_client_test)
that indicates that credential refresh at least seems to work in 4.0.5:

globus-gram-client-activate-test................ok                           
globus-gram-client-callback-contact-test........ok                           
globus-gram-client-cancel-test..................ok                           
globus-gram-client-nonblocking-register-test....ok                           
globus-gram-client-refresh-credentials-test.....ok                           
globus-gram-client-register-test................ok                           
globus-gram-client-register-callback-test.......ok                           
globus-gram-client-register-cancel-test.........ok                           
globus-gram-client-ping-test....................ok                           
globus-gram-client-status-test..................ok                           
globus-gram-client-stop-manager-test............ok                           
globus-gram-client-two-phase-commit-test........ok                           
globus-gram-client-register-ping-test...........ok                           
globus-gram-client-stdio-size-test..............ok

But i don't know what really happens
in globus-gram-client-refresh-credentials-test
------- Comment #2 From 2012-09-12 09:18:22 -------
Doing some bugzilla cleanup...  Resolving old GRAM3 and GRAM4 issues that are
no longer relevant since we've moved on to GRAM5.  Also, we're now tracking
issues in jira.  Any new issues should be added here:

http://jira.globus.org/secure/VersionBoard.jspa?selectedProjectId=10363