mace-opensaml-users - RE: AbstractSignableXMLObject
Subject: OpenSAML user discussion
List archive
- From: "Scott Cantor" <>
- To: <>
- Subject: RE: AbstractSignableXMLObject
- Date: Fri, 15 Feb 2008 19:29:23 -0500
- Organization: The Ohio State University
> The Security header is not included in the signature. Some of its
> components are, and the id-wsf 2 spec requires that the Signature be a
> single signature referencing multiple signed elements and be a child
> of the Security header. The Timestamp and any SAML Assertion token is
> also signed.
Yeah, my mistake, sorry.
> Is there something missing in my understanding? What is not
> appropriate about this?
Just because WSF might assume one signature child, that still doesn't make
that base class appropriate. It's just not the same use case as a single
reference to the parent element.
-- Scott
- AbstractSignableXMLObject, Asa Hardcastle, 02/15/2008
- Re: AbstractSignableXMLObject, Brent Putman, 02/15/2008
- Re: AbstractSignableXMLObject, Asa Hardcastle, 02/15/2008
- Re: AbstractSignableXMLObject, Brent Putman, 02/15/2008
- RE: AbstractSignableXMLObject, Scott Cantor, 02/15/2008
- Message not available
- Re: AbstractSignableXMLObject, Brent Putman, 02/15/2008
- Re: AbstractSignableXMLObject, Asa Hardcastle, 02/15/2008
- RE: AbstractSignableXMLObject, Scott Cantor, 02/15/2008
- Re: AbstractSignableXMLObject, Asa Hardcastle, 02/15/2008
- RE: AbstractSignableXMLObject, Scott Cantor, 02/15/2008
- Re: AbstractSignableXMLObject, Asa Hardcastle, 02/15/2008
- Re: AbstractSignableXMLObject, Brent Putman, 02/15/2008
- Re: AbstractSignableXMLObject, Asa Hardcastle, 02/15/2008
- Re: AbstractSignableXMLObject, Brent Putman, 02/15/2008
Archive powered by MHonArc 2.6.16.