Bugzilla – Bug 5026
Signarure validation failure on GRAM/RFT interaction on some cases
Last modified: 2007-03-13 15:17:51
You need to
before you can comment on or make changes to this bug.
The issue has been reported on this thread:
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
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.