RE: Axis2 - Rampart: Clientside Policy Configuration

, 2009 at 7:08 PM, Berner, Nicolas ber...@secaron.de wrote: Hi everybody, I´m playing around with Axis2 (1.41) and Rampart (1.4). The Policy Configuration works fine. I attach a Policy to my Axis2-Service and generate the client from wsdl. So my client is already configured for my desired

Axis2 - Rampart: Clientside Policy Configuration

Hi everybody, I´m playing around with Axis2 (1.41) and Rampart (1.4). The Policy Configuration works fine. I attach a Policy to my Axis2-Service and generate the client from wsdl. So my client is already configured for my desired security operations. Until now I configured the clientside

Rampart: Encryption - Alias is null

Hi! My Client ist trying to decrypt an encrypted message. It doesn´t work because the result of (PasswordCallbackHandler) pc.getIdentifier() is null. You can see this in the stacktrace. org.apache.axis2.AxisFault: WSDoAllReceiver: security processing failed at

[AXIS2] Repository Problem

Hi! I´m just learning to use Axis2 in combination with rampart. I have a service FlexSimple running and it is configured to include a timestamp into each outgoing SOAP-message. Wiring the message over tcpmon one can see that it works fine. On the client-side I have the consuming

Compliant to WS-I Specs?

Hi everybody! Is Axis2(Rampart) compliant to WS-I Basic Security Profile and/or WS-I Reliable Security Profile? Kind regards, Nicolas Berner Secaron AG Ludwigstr. 45 85399 Hallbergmoos Tel. +49 811 9594 - 170 Fax +49 811 9594 - 220 __ Secaron AG,