RE: [ws-sx] Issue 015: Support error handling in RequestSecurityTokenextension mechanism

WS-Trust line 367-368 (also 369-371, 430-432, and433-435)

Like ". . . If an element is found that is not understood, the recipient should fault.   The recipient should list unrecognized elements and attributes in the detail element."

Line 2058-2067 Error Handling section, add

Error that occurred (faultstring)	Unrecognized extensions found

Fault code (faultcode)		wst:UnknownExtension 

Fault detail (detail)		. . .

				<UnknownElement>element name</UnknownElement>

				<UnknownAttribute>attribute name</UnknownAttribute>

Regards,

Ching-Yun (C.Y.) Chao, Ph.D.

WebSphere Lead Security Architect

T/L: 678-3763

"Marc Goodner" <>

"Marc Goodner" <> 

01/25/2006 01:56 PM

To

Ching-Yun Chao/Austin/IBM@IBMUS, <>

cc

Subject

RE: [ws-sx] Issue 015: Support error handling in RequestSecurityToken extension   mechanism

Looking at this closer, how would you propose this be reflected in the

text of the specification?

Marc Goodner

Technical Diplomat

Microsoft Corporation

Tel: (425) 703-1903

Blog: http://spaces.msn.com/members/mrgoodner/ 

-----Original Message-----

From: Marc Goodner [mailto:] 

Sent: Wednesday, January 25, 2006 7:15 AM

To: ; 

Subject: RE: [ws-sx] Issue 015: Support error handling in

RequestSecurityToken extension mechanism

Logged as issue 015.

Marc Goodner

Technical Diplomat

Microsoft Corporation

Tel: (425) 703-1903

Blog: http://spaces.msn.com/members/mrgoodner/ 

-----Original Message-----

From:  [mailto:] 

Sent: Tuesday, January 24, 2006 6:53 PM

To: 

Subject: [ws-sx] NEW ISSUE: Support error handling in

RequestSecurityToken extension mechanism

Regarding to WS-Trust, at link:

http://www.oasis-open.org/apps/org/workgroup/ws-sx/download.php/16288/ws

-trust-1.3-spec-ed-01-r03-diff.pdf

Title: Support error handling in RequestSecurityToken extension

mechanism

Description:

The extension mechanism in the RequestSecurityToken and the

RequestSecurityTokenResponse require the recipient fault if an attribute

or an element is found that is not understood.   The recipient can be

required to return the attribute(s) or element(s) that it doesn't

understand in defined format in the fault message.  The error

information can help cross vendor interoperability and even among

different versions of the same vendor implementation.  An implementation

potentially can fall back to a mode of operation that does not use new

extensions.

Proposed Solution:  The recipient returns attribute name(s) and element

name(s) that it doesn't understand in the fault message.