XML signature validation

[Sandy]

Thank you Brent.

The SP is built with OpenSAML Java(2.6.3). Like you correctly guessed, at
the moment I am looking to resolve a Credential from KeyInfo. I checked
xmltooling and it does have resolvers, but I think I'll need to understand
about the resolvers and which resolvers to use. Thank you for the pointer.

Thank you for the advise on establishing trust. I now understand how
important it is and I would implement it. The more complex example at the
bottom serves as a great resource for this.

If there happen to be examples citing the usage of credential resolvers and
a basic signature trust engine, it would be great to know them. I plan on
using a local trust store at the SP for establishing the trust.

Thank you,
Sundeep


*List:       shibboleth-dev <http://marc.info/?l=shibboleth-dev&r=1&w=2>
Subject:    Re: XML signature validation
From:       Brent Putman <putmanb () georgetown ! edu>
Date:       2014-12-15 18:38:35
<http://marc.info/?l=shibboleth-dev&r=1&b=201412&w=2>
Message-ID: 548F2AAB.10400 () georgetown ! edu
<http://marc.info/?i=548F2AAB.10400%20%28%29%20georgetown%20%21%20edu>
[Download message RAW
<http://marc.info/?l=shibboleth-dev&m=141866872901636&q=raw>]*
*[Attachment #2 (multipart/alternative)]*
<http://marc.info/?l=shibboleth-dev&m=141866872901636&q=p2>


On 12/15/14 1:22 PM, Sandy wrote:
>
>
> 1. Is it a good practice to use the public key from the SAML assertion?

That's a complicated question.  The short answer is, you can literally
extract the key from the Signature's KeyInfo and cryptographically
verify the signature with it - but you can't *only* do that.  One way or
another, you have to verify the trust of the key using out-of-band
information, such as SAML metadata.

> 2. If yes, are there any existing utility methods - that I'm unaware
> of - to create or validate the signature without having to append and
> pre-pend the markers.

Yes, there are lots of ways to build the cert from the base64-encoded
DER without the PEM headers/footers.  Those are not really part of the
encoding.  You didn't say what your SP is built with, but if it's
OpenSAML Java (or I assume also C++) then we have helpers in xmltooling
for that purposes.  But we also have higher level components, for
example which resolve a Credential from a KeyInfo, or which wrap that in
the entire trust-establishment process (TrustEngine).

> 3. Why are the markers stripped off from the x509certificate in
> idp-metadata.xml.

They're not specified nor allowed by the spec which defines the KeyInfo
structure (the XML Signature specification).

The headers/footers that you're calling "markers" are from PEM format,
used on disk, in MIME email, etc.  The use case here doesn't specify
that format.

>
> For the record, I have followed
>
> https://wiki.shibboleth.net/confluence/display/OpenSAML/OSTwoUserManJavaDSIG
>
>
> page, which was helpful, but the method call
> 'getVerificationCredential()' was not clear, which is what I was
> trying to implement.
>

Ok.  It's deliberately left unclear, b/c it's just a sketch of the API.
You typically wouldn't want to actually do that in the real world, at
least not *just* that.  Note the big red box above about "Trust
Establishment", don't ignore that.

The more complex example below that with the TrustEngine is conceptually
what you really have to do.   There's layers of abstraction in there,
but ultimately you have to verify the trust of the signing key or else
you have zero security.  You can't just trust what is in the Signature's
KeyInfo.


On Mon, Dec 15, 2014 at 7:22 PM, Sandy <sundeep.nitw at gmail.com> wrote:
>
> Hello,
>
> I have turned ON signing responses and assertions for my SP. I am able to
> see that the IdP is signing both in the assertion. While validating the
> signature at SP, I am trying to use the public key sent in the XML
> signature. I am obtaining the public key from the XML DOM, but I have to
> pre-pend '-----BEGIN CERTIFICATE-----' and append '-----END
> CERTIFICATE-----' to generate an java.security.cert.X509Certificate object.
> Upon further investigation, I see that these lines are being removed while
> generating the idp-metadata.xml(at
> MetadataGeneratorParameters.getCertificateContents()).
>
> 1. Is it a good practice to use the public key from the SAML assertion?
> 2. If yes, are there any existing utility methods - that I'm unaware of -
> to create or validate the signature without having to append and pre-pend
> the markers.
> 3. Why are the markers stripped off from the x509certificate in
> idp-metadata.xml.
>
> For the record, I have followed
>
>
> https://wiki.shibboleth.net/confluence/display/OpenSAML/OSTwoUserManJavaDSIG
>
> page, which was helpful, but the method call 'getVerificationCredential()'
> was not clear, which is what I was trying to implement.
>
> Thank you,
> Sundeep
>
> P.S.: My apologies for posting this question first in the users list. It
> belongs to the dev list. My bad! As always, I appreciate your patience.
> Thank you.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/dev/attachments/20141215/e6d0a542/attachment.html