Bug 5387 - Persistent notification fails expecting default credentials
: Persistent notification fails expecting default credentials
Status: RESOLVED FIXED
: Java WS Core
globus_wsrf_core
: unspecified
: PC Windows XP
: P3 normal
: 4.2.0
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2007-06-18 16:03 by
Modified: 2007-06-19 13:18 (History)


Attachments


Note

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


Description From 2007-06-18 16:03:48
In a configuration where container has host credentials configured, during
recovery the following issue was seen. This occurs when GRAm attempts to cancel
the notification subscription once a notification is received from RFT

2007-06-18 12:00:13,801 ERROR exec.StateMachine
[RunQueueThread_1,processCompletedStagingJob:2767] Unable to destroy transfer.
AxisFault
 faultCode:
{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}General
 faultSubcode: 
 faultString: Proxy file (/tmp/x509up_u1504) not found.
 faultActor: 
 faultNode: 
 faultDetail: 
   
{http://xml.apache.org/axis/}stackTrace:org.globus.gsi.GlobusCredentialException:
Proxy file (/tmp/x509up_u1504) not found.
    at
org.globus.gsi.GlobusCredential.<init>(GlobusCredential.java:102)
    at
org.globus.gsi.GlobusCredential.reloadDefaultCredential(GlobusCredential.java:544)
    at
org.globus.gsi.GlobusCredential.getDefaultCredential(GlobusCredential.java:529)
    at
org.globus.wsrf.impl.security.authentication.signature.X509WSSignedSOAPEnvelopeBuilder.getCredential(X509WSSignedSOAPEnvelopeBuilder.java:82)
    at
org.globus.wsrf.impl.security.authentication.signature.X509WSSignedSOAPEnvelopeBuilder.buildMessage(X509WSSignedSOAPEnvelopeBuilder.java:100)
    at
org.globus.wsrf.impl.security.authentication.securemsg.X509SignHandler.handleMessage(X509SignHandler.java:107)
    at
org.globus.wsrf.impl.security.authentication.securemsg.X509SignHandler.handleResponse(X509SignHandler.java:65)

This happens with recovery of persistence subscription. When the Subject object
associated is recovered, the private credentials are not restored. I have
replicated it with java ws core tests.
------- Comment #1 From 2007-06-18 22:03:36 -------
Fix committed to branch and test were improved to cover this specific user
case. Martin has verified the patch fixes the issue with GRAM. Reassinging this
bug to trunk code, relevant patch needs to be merged there.
------- Comment #2 From 2007-06-19 13:18:17 -------
Fix committed to trunk and tests added to cover this specific use case. Updated
branch fix to cover Subject objects that are read-only.