Dynamic encryption user name

2015-10-02 Thread anpoky
I have a CXF WebService (as server) with WSS Security and now I would like to use a public certificate for encryption based on the sender. I know there is the property ws-security.encryption.username=useReqSigCert This comes already close to what I would like to do. However, in my setup, there

No mtom before message encryption

2015-10-02 Thread anpoky
Hi, The WSS policy for server says: So the mtom is turned on. The out message body must be signed and encrypted. The server not yet encrypted response has got a base64binary element and when mtom is on, the serializer puts the content of this element

Re: Dynamic encryption user name

2015-10-02 Thread anpoky
I found the answer by myself. A custom inteceptor just needs to override the property: message.put("security.encryption.username", userAlias); Then the wss4j interceptor uses the right certificate out of the keystore. -- View this message in context:

Re: Auto discover providers JAXRSServerFactoryBean

2015-10-02 Thread Sergey Beryozkin
Hi Some info is here: http://cxf.apache.org/docs/jaxrs-services-configuration.html#JAXRSServicesConfiguration-Auto-discoveryofrootresourcesandproviders Also, the last sentence at

Re: Auto discover providers JAXRSServerFactoryBean

2015-10-02 Thread Peter De Winter
Hi Sergey, Thanks for the info. Could you just tell me if auto discovered providers, we are using the spring discovery method, should also automatically be registered in the jaxrsserverfactorybean? That would be expected behavior, not? This does not seem to happen in our case. We are using

Re: Soap 1.1 endpoint already registered on address

2015-10-02 Thread sanjay0522
I also was getting the same issue , The problem was that inside the web.xml , I was refering to my spring-beans.xml file and inside that I configured all the bean as usual , the issue was that I didnt added the cxf.xml import. some time back it was there and but when I removed it I could see the