Bug 5026 - Signarure validation failure on GRAM/RFT interaction on some cases
: Signarure validation failure on GRAM/RFT interaction on some cases
Status: ASSIGNED
: Java WS Security
Authentication
: 4.0.3
: PC Windows XP
: P3 normal
: ---
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2007-02-23 09:05 by
Modified: 2007-03-13 15:17 (History)


Attachments


Note

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


Description From 2007-02-23 09:05:59
The issue has been reported on this thread:

http://www.globus.org/mail_archive/gram-dev/2007/02/msg00014.html

Summary:

1. Service from Machine A invokes WS GRAM on Machine B
2. WS GRAM creating RFT resource using local invocation and WS secure message
on Machine B fails on signature validaton 
3. Things work fine if GRAM client is used directly to submit to Machine B WS
GRAM or if service on Machine A submits to WS GRAM on Machine A
------- Comment #1 From 2007-03-13 15:17:51 -------
Attempt to replicate the issue on test service failed. Scenario tried was
client incokign service 1, service 1 invoking service 2 in separate container,
which in turns uses local invocation with secure message to invoke service 3.
All containers used transport security and worked fine. Will try to replicate
it with 4.0.3 GRAM code.