On 08/29/2016 07:46 AM, Colm O hEigeartaigh wrote:
You can get the signing certificate via the WSS4J result set which is
stored on the CXF Message Context after WS-Security processing. There is an
example in a unit tests here in the cxf-rt-ws-security module:
This should address this issue:
http://git-wip-us.apache.org/repos/asf/cxf/commit/502db47a
More work will be done on the client side too later on, with
CompletableFuture to be supported OOB.
Sergey
On 30/08/16 09:47, Sergey Beryozkin wrote:
Hi Muse
Thanks for starting experimenting with
It's traditional. We wait for the last minute to get our talk proposals
in for conferences.
Well, the last minute has arrived. The CFP for ApacheCon Seville closes
on September 9th, which is less than 2 weeks away. It's time to get your
talks in, so that we can make this the best ApacheCon yet.
Hi Allan
I would not be too concerned about Server being a standard header - it
is of purely informative purpose anyway so if dropping it can improve
something for the server then it is worth it :-)
Cheers, Sergey
On 30/08/16 04:25, Allan C. wrote:
Hi Sergey,
I've tested the setup you
Ok, after some more digging the problem seems to be the following:
If I start up both services on "http://localhost/service; and
"http://localhost/service/v2; respectively we can successfully process SOAP
requests on "http://localhost/service/v2;. When we try to use the other service
we get
Using wsp:Optional="true" is definitely supported for newer versions of CXF
(although I'm not sure if it is for CXF 2.5.4, which is quite an old
release), as it's used in one of the existing WS-Security system tests.
Perhaps the issue was fixed in this bug:
Hi Muse
Thanks for starting experimenting with it.
It is fair to say that this feature requires more work - it is being
planned.
I'll add a missing @Provider annotation and that alone will let this
provider be auto discovered too with CXF 3.1.8 (with a
cxf.jaxrs.classes-scan -
Hi all,
Im using CXF and want to set some custom HTTP headers. I implemented a
javax.xml.ws.handler.soap.SOAPHandler and accessed the
SOAPMessageContext in the handleMessage method. But setting my custom
header prevents something from setting the SOAPAction header. I
realized, that at the
Hello
I am trying to implement WS-Trust including a policy that CXF uses to validate
the received token on our application server. This part we have achieved
successfully.
Be we have an additional security model which uses the TLS protocol and data
from the SOAP request body to validate
