Re: [Axis2] SAML security tokens generation

Hi Christina, Check the contents under Setting up a Security Token Service available at [1] if you want to set up Rahas. Another sample is available at [2]. If you want to supply your own name identifier in the SAML token please implement the CallbackHanlder like this[3] and specify it in the

Re: passwordCallbackClass

Hi Pavan, As far as I know you cannot completely remove the concept of password call back handler, if you want to put signature or username token. However you can programatically create and add RampartConfig. This way you can get rid of it from the policy.xml file, but still it will exit.

Re: WS:Axis2-1.1.1 Ramprt 1.1 error

Hi, This is because you haven't set the action of InflowSecurity parameter in the services.xml at server side. Please look at sample 02. parameter name=InflowSecurity action itemsTimestamp/items

Re: [Axis2] SAML/Rampart Question

the SAML assertion to the WS-Security header. I don't know of anyone having a SAML implementation with Rampart. Regards, Dimuthu -Original Message- From: Dimuthu Leelaratne [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 16, 2007 10:28 PM To: axis-user@ws.apache.org Subject: Re: [Axis2

Re: How to deploy e simple webservice in axis2

Hi Pierpaolo, Here is my favorite simplest sample. It is a Hello World sample. http://wso2.org/library/95 Cheers, Dimuthu. -- http://wso2.org On 3/1/07, Pierpaolo Pagnoni [EMAIL PROTECTED] wrote: I'm a new user in AXIS2 and I've some difficult to deploy a ws. I must build a ws

Re: Rampart 1.1 - Sample07 as policy

PROTECTED] http://www.multi-support.com Dimuthu Leelaratne dimuthu.leelarat To [EMAIL PROTECTED] axis-user@ws.apache.org cc

Re: Rampart 1.1 - Sample07 as policy

Hi Riis, Please have a look at samples/policy folder in rampart 1.1 distribution. It has 4 samples and they could help you. Cheers, Dimuthu On 2/16/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, I'm trying to change my implementation to use policies instead of the old way. But I have

Re: Rampart-1.1 samples

Hi Hailong Wang, There are two ways in which we can configure Rampart to include a UsernameToken. One way is by using the configuration file which is Axis specific. Please have a look at samples/basic/samples02/client.axis2.xml inside the rampart folder. Look at this part [1] The other is

Re: [Axis2] [rampart] Problems using rampart

and they are all working fine. I really don't know where this problem comes from. Do you have any ideas? Regards, Sebastian Dimuthu Leelaratne schrieb: Hi Sebastian, I tried to recreate the scenario as follows. 1) I used axis2-1.1.1 and rampart 1.1 and executed the first rampart smaple which

Re: [Axis2][rampart] Unknown top level PED error

Hi JF, We do not support the WS-SX WS-SecurityPolicy specification yet. Rampart supports only July 2005 version [1] In the current implementaiton you will have to include the supporting token in a bindding as shown in the sample 1 in the policy samples. Thanks, Dimuthu [1]

Re: [Axis2] [rampart] Problems using rampart

:configPathmessaging_test.config/ns2:configPath ns2:messageFactoryClassName / /ns2:addClient /soapenv:Body /soapenv:Envelope Maybe you have any ideas. Please write when you have suggestions... Regards, Sebastian Dimuthu Leelaratne schrieb: Hi Sebastian, This is not a rampart problem

Re: Configuration in Rampart 1.1

Hi Sriram, As I understand your single client can tallk to multiple services but with different security requirements. For configurations now we encourage using Policy file according to WS Security Policy specification (http://specs.xmlsoap.org/ws/2005/07/securitypolicy/ws-securitypolicy.pdf).

Re: WS-SECURITY WITH SAML2 TOKENS

Hi Evaristo,' Rampart uses opensaml-1.1 library to give support for the SAML. Currently the library doen't support SAML2. Regards, Dimuthu On 1/17/07, Evaristo José Camarero [EMAIL PROTECTED] wrote: Hi: Does Axis2 with rampart module support SAML2 Security Tokens? Regards, Evaristo

Re: [Axis2] [rampart] Problems using rampart

Hi Sebastian, This is not a rampart problem. The pointed out JIRA shows the bug. I walked through the stack trace. This happens for specific SOAP messages, when they are converted to DOOM as mentioned. I have never experienced the problem. Maybe because the SOAP messages that I use wouldn't