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: [security-services] Action A11: XML Signature requirements for SOAPProfile

The SOAP profile in the bindings-06 draft specifies that all SOAP messages
which include SAML assertions must be signed. The current signature
requirements are too restrictive; in particular, they are not compatible
with SOAP header elements that have "actor" attributes.

I propose that we change lines 828-829 and 978-979 (.pdf version) to read:

The <dsig:Signature> element MUST apply to all the SAML assertion elements
in the SOAP <Header>, and all the relevant portions of the SOAP <Body>, as
required by the application. Specific applications may require that the
signature also apply to additional elements.

The wording is a bit clumsy; feel free to fix it if you want.

(Do we need to say anything about whether the receiver should rely on
unsigned portions of the SOAP message? My first inclination is that it's up
to the application, so we shouldn't say anything. Perhaps we need something
in security considerations?)

 - irving -

The information contained in this message is confidential and is intended 
for the addressee(s) only.  If you have received this message in error or 
there are any problems please notify the originator immediately.  The 
unauthorized use, disclosure, copying or alteration of this message is 
strictly forbidden. Baltimore Technologies plc will not be liable for direct, 
special, indirect or consequential damages arising from alteration of the 
contents of this message by a third party or as a result of any virus being 
passed on.

In addition, certain Marketing collateral may be added from time to time to 
promote Baltimore Technologies products, services, Global e-Security or 
appearance at trade shows and conferences.
This footnote confirms that this email message has been swept by 
Baltimore MIMEsweeper for Content Security threats, including
computer viruses.

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

Powered by eList eXpress LLC