OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

security-services message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: RE: [security-services] Action A9: Error handling for SOAP profil e


Rich,

One of us is missing some context here. The proposed error message
has nothing to do with the concrete transport or binding for SOAP.

The SOAP Profile of SAML describes a message format in which SAML assertions
are added as headers to SOAP messages. This leads to the question: what
happens when the intended recipient (of the assertion) cannot process
it for some reason? We are proposing that a Client.SAML be returned
for this special case. Other than that the normal SOAP processing
model applies.

- prateek

>>>If the receiving party understands the SAML assertion in the 
>>SOAP header,
>>> but considers the assertion invalid, the receiving party 
>>SHOULD return a
>>> SOAP message with a <Fault> element as the message body.
>>
>>Do you really want error codes like that to depend on the transport?
>>	/r$


- prateek


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC