RE: [ws-sx-comment] Fault Ambiguity

[Paul Cotton <Paul.Cotton@microsoft.com>]

> The WS-S specification provides little detail on the fault definitions

 

If this is related to WS-Security should you not send this to the TC recently created to do WS-Security maintenance?  See:

http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wss-m

 

/paulc

 

Paul Cotton, Microsoft Canada

17 Eleanor Drive, Ottawa, Ontario K2E 6A3

Tel: (425) 705-9596 Fax: (425) 936-7329

 

From: Tom Link [mailto:tomlink@us.ibm.com]
Sent: Friday, November 19, 2010 3:53 PM
To: ws-sx-comment@lists.oasis-open.org
Subject: [ws-sx-comment] Fault Ambiguity

 

While testing in the WSTF group, we have observed an ambiguous specification for some faults. For a message that contains no security attempting to connect to a secured service, what is the appropriate fault?

The two faults we have observed from different runtimes are wsse:FailedCheck and wsse:InvalidSecurity. The WS-S specification provides little detail on the fault definitions.

wsse:InvalidSecurity - An error was discovered processing the <wsse:Security> header.
wsse:FailedCheck - The signature or decryption was invalid

Tom Link

IBM WebSphere Web Services Interoperability
Building 503 Room E204
4205 South Miami Blvd,  Durham,  NC, 27703
Office:   919-543-4370
Mobile: 919-244-3982

tomlink@us.ibm.com    AIM: tomlinkusa YM: tomlinkusa GM: tomlinkusa MSN: tomlink@csi.com