Bug 5026 – Signarure validation failure on GRAM/RFT interaction on some cases

Bug 5026 - Signarure validation failure on GRAM/RFT interaction on some cases

Summary:

Signarure validation failure on GRAM/RFT interaction on some cases

Status:	ASSIGNED

Product:	Java WS Security
Component:	Authentication
Version:	4.0.3
Platform:	PC Windows XP

Importance:	P3 normal
Target Milestone:	---
Assigned To:	Rachana Ananthakrishnan

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2007-02-23 09:05 by Rachana Ananthakrishnan
Modified:	2007-03-13 15:17 (History)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

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

Description From Rachana Ananthakrishnan 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 Rachana Ananthakrishnan 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.