I tried to run full test on my box. JDK 1.6 with Maven 3.0.3.
I got the a check style error
cxf/branches/2.5.x-fixes/rt/ws/addr/src/main/java/org/apache/cxf/ws/addressing/ContextUtils.java:492:33:
Nested if-else depth is 4 (max allowed is 3).
Audit done.
I checked the CI it doesn't have this
If you want to authenticate with an X.509 certificate over TLS, you
need a policy that uses the TransportBinding (that doesn't require
client authentication), and specify an EndorsingSupportingToken which
contains an X509 Token. Something like:
wsp:Policy wsu:Id=DoubleItTransportEndorsingPolicy
Colm,
How I do validate X509 certificate and authenticate user?
I did not find any interceptor for X509 certificate.
--
View this message in context:
http://cxf.547215.n5.nabble.com/Custom-X509TokenValidator-tp5708191p5708260.html
Sent from the cxf-dev mailing list archive at Nabble.com.
The policy I attached in the last mail will cause the client to sign
the Timestamp using the private key associated with the X.509
certificate. Client authentication then takes place on the receiving
side by verifying the signature, and verifying trust in the signing
cert. You don't have to add
Interesting... I'm not seeing a checkstyle failure it with Java 7 or in
Eclipse either. (using Maven 3.0.4 though) Honestly, not sure what would
cause the difference. Bizarre. Feel free to fix though. Someone else
may run into it.
Dan
On Tuesday, May 22, 2012 03:44:05 PM Willem
