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