RE: Websphere 9 and CXF

This was the last hurdle... The api is addAllowedEncryptionMethod for the data not addAllowedKeyEncryptionMethod(WSSEncryption.TRIPLE_DES); The error message was correct that is not a key encryption algo. With this change, the workaround was fully tested. Thanks Colm! -Original

RE: Websphere 9 and CXF

Thank you. Agreed. I fixed that on the websphere client to use RSA OAEP. Additionally had to configure the encryption key reference type in the websphere JAX-WS client to REF_ID to make it match what CXF expects. Otherwise I was getting "ENC_KEY_INFO MUST have exactly one child element"

Dynamically changing endpoints

I'm implementing a client for a soap endpoint where the messages return different callouts to be used for individual soap operations, each endpoint supporting the same service wsdl. Does anyone have suggestions on the best way to change the endpoint for different soap operations? I could create

Re: Websphere 9 and CXF

Yes, the Encrypted Key is using RSA v1.5, whereas probably your security policy requires RSA OAEP. For example, you might have "Basic128" in your policy, but it sounds like the sender is using "Basic128Rsa15". Colm. On Wed, Oct 18, 2017 at 3:17 PM, wrote: > Hi

RE: Websphere 9 and CXF

Hi Colm, I am still working on it, it looks like a different issue than the xml ordering. Maybe you can see the issue from this information? Thanks! Mark >From the logs: 2017-10-18 10:09:33 - Found encrypted key element 2017-10-18 10:09:38 - Sym Enc Algo:

Re: Websphere 9 and CXF

What was the error you saw when you moved the EncryptedKey Element above the EncryptedData Element? What is actually stored inside the first EncryptedData Element? Colm. On Wed, Oct 18, 2017 at 1:04 PM, Mark Fuini wrote: > Thank you so much for getting back to me. This is

Re: AW: fediz_config.xml hosts

Hi Jan, Thank you for your reply. In simpleWebapp the fediz_config.xml is linked from the context.xml so does there need to be a separate fediz_config.xml for each webapp?     className="org.apache.cxf.fediz.tomcat8.FederationAuthenticator" configFile="conf/fediz_config.xml" /> I was

Re: Websphere 9 and CXF

Thank you so much for getting back to me.  This is an ongoing daily issue for us. The conclusion you came to was my analysis also.  But I not sure the actual xml ordering is part of the spec.  So their xml may be valid.  But that means web service which use event driven xml parsing are at a

Re: Websphere 9 and CXF

The problem here is that the EncryptedKey structure, which contains the ReferenceList pointing to the first EncryptedData structure, is below the EncryptedData structure. WSS4J parses the security header in order, and so when it hits the first EncryptedData structure it does not know how to

RE: cxf-java2wadl-plugin java2wadl questions

Well, actually i was referring to applicative error codes (and their descriptions) - that might be useful by users so can they understand the exact issue Thanks, Eyal -Original Message- From: Sergey Beryozkin [mailto:sberyoz...@gmail.com] Sent: 18 October, 2017 12:44 To: Eyal

AW: fediz_config.xml hosts

Hi Metthew, Fediz Config is independent of your hostname. You don't need to define your hostname in your fediz config. The only exception is when you use a reverse proxy for your application. Fediz Plugin will always use the same hostname for the wreply URL that was used within the

RE: Hide the stack trace for org.apache.cxf.interceptor.Fault

Hello, Sorry to have disturb you, my bad ! client = ClientBuilder.newBuilder().property("org.apache.cxf.logging.FaultListener", new NoOpFaultListener()) as well as client = ClientBuilder.newBuilder().property("org.apache.cxf.logging.FaultListener", new MyFaultListener ()) worked. Best

Re: cxf-java2wadl-plugin java2wadl questions

That said, while customizing a response serialization in order to show the extra statuses can help users see them, one can document it as well. For example, I do not see how the information that a given response can return 405 can be practically used. Well, one can type for example a 405

Re: cxf-java2wadl-plugin java2wadl questions

I forgot it's really about using a Maven plugin. Hmm...I guess we may need to support a custom class... Sergey On 18/10/17 07:06, Eyal Weingart wrote: Thanks again. Regarding: "Create MyWadlGenerator extending WADLGenerator, override whatever is needed, and register MyWadlGenerator as a

fediz_config.xml hosts

Hi, The example fediz_config.xml file has the format     ... which seems to describe a webapp deployed at Host localhost. How would it be configured if the webapp is deployed at a different host in Tomcat server.xml? e.g. I tried searching for the source.  I found

RE: cxf-java2wadl-plugin java2wadl questions

Thanks again. Regarding: "Create MyWadlGenerator extending WADLGenerator, override whatever is needed, and register MyWadlGenerator as a jaxrs:provider" Where exactly do i need to register the MyWadlGenerator as a jaxrs:provider? I saw it can be done in a spring file that serves cases for WADL