<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 4/30/16 11:00 AM, Stefan Rasmusson
wrote:<br>
</div>
<blockquote
cite="mid:CACdgychhTbcD+kMYm7rWC+jKJZoO1BU2W5vWZXM6M4wrZ5w0Pg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div>
<div class="gmail_signature">I love the new handlers,</div>
</div>
</div>
</div>
</blockquote>
<br>
Excellent! The intent is that the message processing model for
server-side and client-side is the same, So you can use many/most of
the same handlers for both, for example for SAML message processing.<br>
<br>
<blockquote
cite="mid:CACdgychhTbcD+kMYm7rWC+jKJZoO1BU2W5vWZXM6M4wrZ5w0Pg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div>
<div class="gmail_signature"> Im
using SAMLOutboundProtocolMessageSigningHandler to sign
SOAP. Is there anyone for validating on the other side? I
could not find a obvious candidate.</div>
</div>
</div>
</div>
</blockquote>
<br>
Absolutely. SAMLProtocolMessageXMLSignatureSecurityHandler. In the
same package.<br>
<br>
There's probably a slight bit of more work to do there, as many of
the inbound handlers like this one would require things to be
populated in the inbound MessageContext, like a
SignatureValidationParameters with a TrustEngine, etc. That sort of
thing is likely a bit different on the server- vs client-side,
because of the environmental differences, and is one of the things
I'm working on right now. The existing server-side code is
implemented as a ProfileAction processing a ProfileRequestContext,
which doesn't work for the SOAP client case.<br>
<br>
<br>
<blockquote
cite="mid:CACdgychhTbcD+kMYm7rWC+jKJZoO1BU2W5vWZXM6M4wrZ5w0Pg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div>
<div class="gmail_signature"><br>
</div>
The validateJCEProviders and validateNonSunJAXP, are they
gone?
<div class="gmail_signature"><br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
The former is still there. It's an Initializer impl,
org.opensaml.xmlsec.config.JavaCryptoValidationInitializer.<br>
<br>
The latter is consciously removed in v3, since we no longer require
use of a non-Sun JAXP (e.g. an endorsed Xerces). The only reason
for that was that older versions of Sun/Oracle Java shipped with a
buggy Xerces embedded. That's not the case anymore, as far as we
know.<br>
<br>
<br>
<blockquote
cite="mid:CACdgychhTbcD+kMYm7rWC+jKJZoO1BU2W5vWZXM6M4wrZ5w0Pg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div>
<div class="gmail_signature">Also I couldn't seem to find
the AbstractPipelineHttpSOAPClient in the 3.1.1 version so
I using the 3.3.0-SNAPSHOT.</div>
</div>
</div>
</div>
</blockquote>
<br>
All the new SOAP client stuff was released in 3.2.0, so you could
use that rather than the SNAPSHOT.<br>
<br>
<br>
<blockquote
cite="mid:CACdgychhTbcD+kMYm7rWC+jKJZoO1BU2W5vWZXM6M4wrZ5w0Pg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div>
<div class="gmail_signature"> What is the ETA on releasing
3.3.0?</div>
</div>
</div>
</div>
</blockquote>
<br>
<br>
I don't think we have an exact date yet, but it's still a few months
away. Roughly sometime in the fall.<br>
<br>
<br>
<br>
</body>
</html>