Subject: Re: Websphere 9 and CXF
The Basic Security Profile mandates that EncryptedData structures must come
after EncryptedKey structures that reference them:
http://www.ws-i.org/profiles/basicsecurityprofile-1.1.html#EncryptedKey_Precedes_EncryptedData
Your best bet is to re-order the header on the
8, 2017 6:57 AM
> To: users@cxf.apache.org
> Subject: 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 he
Message-
From: Colm O hEigeartaigh [mailto:cohei...@apache.org]
Sent: Wednesday, October 18, 2017 6:57 AM
To: users@cxf.apache.org
Subject: Re: Websphere 9 and CXF
The problem here is that the EncryptedKey structure, which contains the
ReferenceList pointing to the first EncryptedData structure
-
From: markfu...@yahoo.com.INVALID [mailto:markfu...@yahoo.com.INVALID]
Sent: Wednesday, October 18, 2017 12:30 PM
To: users@cxf.apache.org; cohei...@apache.org
Subject: RE: Websphere 9 and CXF
Thank you. Agreed. I fixed that on the websphere client to use RSA OAEP.
Additionally had to
he.tomcat.websocket.server.WsFilter.doFilter(
> WsFilter.java:52)
>
>
>
>
>
> From: Colm O hEigeartaigh [ <mailto:cohei...@apache.org>
> mailto:cohei...@apache.org]
> Sent: Wednesday, October 18, 2017 9:44 AM
> To: <mailto:markfu...@yahoo.c
(AbstractHTTPServlet.java:276)
>
> at org.apache.catalina.core.ApplicationFilterChain.
> internalDoFilter(ApplicationFilterChain.java:291)
>
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> ApplicationFilterChain.java:206)
>
> at org.apache.tomcat.w
igh [mailto:cohei...@apache.org]
Sent: Wednesday, October 18, 2017 9:44 AM
To: markfu...@yahoo.com
Cc: users@cxf.apache.org
Subject: 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 fi
9IssuerName>
> >... > X509SerialNumber>
> >
> >
> >
> >
> >
> > ...
> >
> >
> >
> >
rg/2001/04/xmlenc#Element";>
> http://www.w3.org/
> 2001/04/xmlenc#aes128-cbc">
>
> ...
>
>
>
>
> http://docs.oasis-open.org/wss/2004/01/oasis-
> 200401-wss-wssecur
http://www.w3.org/
> 2001/04/xmlenc#aes128-cbc">
>
> ...
>
>
>
>
> http://docs.oasis-open.org/wss/2004/01/oasis-
> 200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wssec
="wssecurity_signature_id_21">
http://www.w3.org/2001/04/xmlenc#";
Id="wssecurity_encryption_id_26"
Type="http://www.w3.org/2001/04/xmlenc#Content";>
http://www.w3.org/2001/04/xmlenc#aes128-cbc";>
...
-Original Message-
From: Colm O hEi
Can you give an example of the websphere request that CXF does not parse
correctly?
Colm.
On Mon, Oct 16, 2017 at 10:14 PM, wrote:
> Hi,
>
>
>
> I am trying to get the websphere 9 container's built in security engine to
> programmatically generate a soap JAX-WS secure client request to a CXF we
12 matches
Mail list logo