Re: WS Security via policies - Timestamp always signed

2017-12-29 Thread Kai Rommel
value for this property is 'false'." > > So the Timestamp must be signed if it is present in the request. > > Colm. > > On Fri, Dec 22, 2017 at 7:51 PM, Kai Rommel > wrote: > > > Hi, > > > > I tested different policies and was wondering about

WS Security via policies - Timestamp always signed

2017-12-22 Thread Kai Rommel
Hi, I tested different policies and was wondering about the result. When I add http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702";> Integrity protection Information is added for the SOAP Header Timestamp and the SOAP Body. This looks good. According to the spec http://docs.oasis-open

inconsistency in used spring schemas in 3.1.10-SNAPSHOT

2017-01-18 Thread Kai Rommel
Hello, my build against our company repo fails. It is complaining about the used namespaces and the referenced spring schemas. E.g. checking following beans.xml: in cxf-rt-rs-extension-providers file: org/apache/cxf/jaxrs/provider/atom/servers.xml In 3.1.10-SNAPSHOT the spring version 4.1.9-REL

Re: ws policies InitiatorToken RecipientToken

2014-05-19 Thread Kai Rommel
es for X.509 tokens, which I've since fixed. > > Colm. > > > On Fri, May 16, 2014 at 1:07 PM, Kai Rommel >wrote: > > > Hi Colm, > > I set up a scenario and was wondering about the KeyInfo elements. > > > > > > Policy P1 for WS-Co

ws policies InitiatorToken RecipientToken

2014-05-16 Thread Kai Rommel
Hi Colm, I set up a scenario and was wondering about the KeyInfo elements. Policy P1 for WS-Consumer and WS-Provider CXF ---sends requestA > CXF <--- sends responseB--- Policy is http://cxf.apache.org/policy";> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1

Re: ws policies AlgorithmSuite

2014-01-31 Thread Kai Rommel
ing that you want both > AlgorithmSuites to be enforced. Instead you need a policy alternative, > something like: > > > > > > > > > > > Colm. > > > On Thu, Jan 30, 2014 at 6:14 PM, Kai Rom

ws policies AlgorithmSuite

2014-01-30 Thread Kai Rommel
Hi, I have a WS Consumer sending a signed and encrypted message. In the SOAP Header following algorithm is used: -http://www.w3.org/2001/04/xmlenc#";>http://www.w3.org/2001/04/xmlenc#rsa-1_5"/> In the SOAP Body: -http://www.w3.org/2001/04/xmlenc#"; Type="http://www.w3.org/2001/04/xmlenc#Content";>

Re: InitiatorToken is included in response message when AlwaysToRecipient is set

2014-01-20 Thread Kai Rommel
es/security/policy"; xmlns:wsa="http://www.w3.org/2005/08/addressing"; xmlns:wst=" http://docs.oasis-open.org/ws-sx/ws-trust/200512"; xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/07/utility"; xmlns:wsx=" http://schemas.xmlsoap.org/ws/2004/09/mex";>

InitiatorToken is included in response message when AlwaysToRecipient is set

2014-01-20 Thread Kai Rommel
Hi, I setup a request/response scenario with wss. The policy for the initiator token is set to /AlwaysToRecipient and for the recipient token to /Never. Signature and encryption is configured. The message exchange works fine and the request message looks like expected. But the response message al