Re: have to remove patented algorithms (IDEA, MDC2 and RC5) in OpenSSL, will this affect SSL and ws-security?
On Fri, Jul 17, 2009 at 4:58 AM, Gordon Brown wrote: > Hi List, > > A quick question. Due to company policy, I have to remove the patented > algorithms from OpenSSL and build the library from the source code. The > algorithms I need to remove are the following: IDEA, MDC2 and RC5. I am > wondering if this removal will affect the support of SSL in axis2/c and > ws-security in rampart/c. These algorithms are not used by Axis2/C or Rampart/C. AFAIK, removing these algorithms will not affect Axis2/C and Rampart/C. Regards, Shankar > > Please advise. Thanks in advance! > > Gordon > -- S.Uthaiyashankar Software Architect WSO2 Inc. http://wso2.com/ - "The Open Source SOA Company"
Re: have to remove patented algorithms (IDEA, MDC2 and RC5) in OpenSSL, will this affect SSL and ws-security?
Yes, I did some debugging, but this seems to be a bug in axis2/c library. Or maybe I need to do something like call some APIs so that the status will be set and so users can get the status? My question is this, does a user need to specifically do something in order for get_http_status_code to work? if yes, what needs to be done? There doesn't seem to any info in the documentation. Thanks! Vivian From: Rajika Kumarasiri To: Apache AXIS C Developers List Sent: Wednesday, July 15, 2009 7:37:50 PM Subject: Re: how to get the http status code May be some debugging will help? > Rajika >On Thu, Jul 16, 2009 at 5:45 AM, Vivian Wang wrote: >> >> Hi There, >> >> I am using axis2/c to make web service client call, like this: >> >> axiom_node_t * node = >> axis2_svc_client_send_receive(_wsf_service_client, _env, payload); >> >> After this, I am trying to use the following API to get the http status >> code, >> >> AXIS2_EXTERN int AXIS2_CALL >> axis2_svc_client_get_http_status_code(axis2_svc_client_t * svc_client, const >> axutil_env_t * env); >> >> I am expecting 408 for time out, 200 for success. However, I am always >> getting 0. How do I get the proper status code? >> >> Thanks! >> Vivian >> >> >>
have to remove patented algorithms (IDEA, MDC2 and RC5) in OpenSSL, will this affect SSL and ws-security?
Hi List, A quick question. Due to company policy, I have to remove the patented algorithms from OpenSSL and build the library from the source code. The algorithms I need to remove are the following: IDEA, MDC2 and RC5.. I am wondering if this removal will affect the support of SSL in axis2/c and ws-security in rampart/c. Please advise. Thanks in advance! Gordon
Re: How do I know ws-security is enabled programmatically?
In the latest svn there is a method to get the axis2_conf_ctx_t from the svc_client. You can also create the axis2_conf_ctx_t and then pass it to svc_client creation method. Yes, you can use axis2_conf_is_engaged method. Supun. On Thu, Mar 12, 2009 at 11:09 AM, Raymond Zhou wrote: > Hi Supun, > > Can you please point me to how I could get axis2_conf_ctx from svc_client? > It doesn't seem possible. > > I find out another way though, from axis2_conf.h, you have the following > interface: > > AXIS2_EXTERN axis2_conf_t *AXIS2_CALL axis2_conf_create( > const axutil_env_t * env); > So you can create one axis2_conf_t, then in this same inferface, you have: > > AXIS2_EXTERN axis2_bool_t AXIS2_CALL axis2_conf_is_engaged(axis2_conf_t * > conf, > const axutil_env_t * env, const axutil_qname_t * module_name); > You can now figure out if rampart is engaged, is this a right approach? The > drawback is that If service client already create one axis2_conf_t, this way > create the same structure twice. > > Thanks! > Ray > > > --- On *Tue, 3/10/09, Supun Kamburugamuva * wrote: > > > From: Supun Kamburugamuva > Subject: Re: How do I know ws-security is enabled programmatically? > To: "Apache AXIS C User List" > Date: Tuesday, March 10, 2009, 4:01 AM > > When you create the svc_client you create the axis2_conf_ctx. This holds > all the axis2 configurations. You can access the axis2_conf_ctx from > svc_client and you can access the axis2_conf_t from axis2_conf_ctx_t. > axis2_conf_t contains the list of all the engaged modules. > > Have a look at conf.c file. > > Supun. > > On Tue, Mar 10, 2009 at 8:41 AM, Raymond Zhou > http://us.mc464.mail.yahoo.com/mc/compose?to=raywang...@yahoo.com> > > wrote: > >> Hi Manjula, >> >> Maybe my writing is a bit confusing, my question is not really about >> setting the policy file programmatically, my question is about how I know >> the ws-security is enabled programmatically (which means that the rampart/c >> module is engaged in axis2/c configuration file). I need to know this >> because my client code need to support both ws-security enabled and >> ws-security disabled (the normal case), so that in the case of no >> ws-security I don't have to read the policy file and set any ws-securit >> related parameters programmatically. >> >> Thanks! >> Ray >> >> --- On *Tue, 3/10/09, Manjula Peiris >> http://us.mc464.mail.yahoo.com/mc/compose?to=manj...@wso2.com> >> >* wrote: >> >> >> From: Manjula Peiris >> http://us.mc464.mail.yahoo.com/mc/compose?to=manj...@wso2.com> >> > >> Subject: Re: How do I know ws-security is enabled programmatically? >> To: "Apache AXIS C User List" >> http://us.mc464.mail.yahoo.com/mc/compose?to=axis-c-u...@ws.apache.org> >> > >> Date: Tuesday, March 10, 2009, 3:12 AM >> >> >> when you engage rampart there should be a policy to construct the >> message. Please see Rampart/c samples for more info. >> >> On Mon, 2009-03-09 at 00:20 -0700, Raymond Zhou wrote: >> > >> > A quick question. I am using rampart/c to provide ws-security for a >> > web service client application. How do I know ws-security is enabled >> > programmatically? I understand that in order to use ws-security I need >> > to do something in the configuration file axis2.xml and I also need to >> > put rampart/c as a module. But I also need to set the security policy >> > into the web service client object programmatically, right? Then I >> > need to know whether or not ws-security is enabled, and if not, I >> > don't need to set the policy (there is none actually) into the ws >> > client object. >> > >> > Thanks! >> > Ray >> > >> >> >> > > > -- > Software Engineer, WSO2 Inc > http://wso2.org > supunk.blogspot.com > > > > -- Software Engineer, WSO2 Inc http://wso2.org supunk.blogspot.com
Re: How do I know ws-security is enabled programmatically?
Hi Supun, Can you please point me to how I could get axis2_conf_ctx from svc_client? It doesn't seem possible. I find out another way though, from axis2_conf.h, you have the following interface: AXIS2_EXTERN axis2_conf_t *AXIS2_CALL axis2_conf_create(const axutil_env_t * env); So you can create one axis2_conf_t, then in this same inferface, you have: AXIS2_EXTERN axis2_bool_t AXIS2_CALL axis2_conf_is_engaged(axis2_conf_t * conf, const axutil_env_t * env, const axutil_qname_t * module_name); You can now figure out if rampart is engaged, is this a right approach? The drawback is that If service client already create one axis2_conf_t, this way create the same structure twice. Thanks! Ray --- On Tue, 3/10/09, Supun Kamburugamuva wrote: From: Supun Kamburugamuva Subject: Re: How do I know ws-security is enabled programmatically? To: "Apache AXIS C User List" Date: Tuesday, March 10, 2009, 4:01 AM When you create the svc_client you create the axis2_conf_ctx. This holds all the axis2 configurations. You can access the axis2_conf_ctx from svc_client and you can access the axis2_conf_t from axis2_conf_ctx_t. axis2_conf_t contains the list of all the engaged modules. Have a look at conf.c file. Supun. On Tue, Mar 10, 2009 at 8:41 AM, Raymond Zhou wrote: Hi Manjula, Maybe my writing is a bit confusing, my question is not really about setting the policy file programmatically, my question is about how I know the ws-security is enabled programmatically (which means that the rampart/c module is engaged in axis2/c configuration file). I need to know this because my client code need to support both ws-security enabled and ws-security disabled (the normal case), so that in the case of no ws-security I don't have to read the policy file and set any ws-securit related parameters programmatically. Thanks! Ray --- On Tue, 3/10/09, Manjula Peiris wrote: From: Manjula Peiris Subject: Re: How do I know ws-security is enabled programmatically? To: "Apache AXIS C User List" Date: Tuesday, March 10, 2009, 3:12 AM when you engage rampart there should be a policy to construct the message. Please see Rampart/c samples for more info. On Mon, 2009-03-09 at 00:20 -0700, Raymond Zhou wrote: > > A quick question. I am using rampart/c to provide ws-security for a > web service client application. How do I know ws-security is enabled > programmatically? I understand that in order to use ws-security I need > to do something in the configuration file axis2.xml and I also need to > put rampart/c as a module. But I also need to set the security policy > into the web service client object programmatically, right? Then I > need to know whether or not ws-security is enabled, and if not, I > don't need to set the policy (there is none actually) into the ws > client object. > > Thanks! > Ray > -- Software Engineer, WSO2 Inc http://wso2.org supunk.blogspot.com
Re: How do I know ws-security is enabled programmatically?
I think in this case you should engage rampart programmatically from your client code. Engaging in the conf file is not the right solution. call axis2_svc_client_engage_module(svc_client, env, "rampart"); to engage it programmatically. For the secure case, create svc_client engage rampart set policy call svc_client send_receive For the non-secure case create svc_client call svc_client send_receive -Manjula. On Mon, 2009-03-09 at 20:41 -0700, Raymond Zhou wrote: > Hi Manjula, > > Maybe my writing is a bit confusing, my question is not really about > setting the policy file programmatically, my question is about how I > know the ws-security is enabled programmatically (which means that > the rampart/c module is engaged in axis2/c configuration file). I need > to know this because my client code need to support both ws-security > enabled and ws-security disabled (the normal case), so that in the > case of no ws-security I don't have to read the policy file and set > any ws-securit related parameters programmatically. > > Thanks! > Ray > > --- On Tue, 3/10/09, Manjula Peiris wrote: > > > From: Manjula Peiris > Subject: Re: How do I know ws-security is enabled > programmatically? > To: "Apache AXIS C User List" > Date: Tuesday, March 10, 2009, 3:12 AM > > when you engage rampart there should be a policy to construct > the > message. Please see Rampart/c samples for more info. > > On Mon, 2009-03-09 at 00:20 -0700, Raymond Zhou wrote: > > > > A quick question. I am using rampart/c to provide > ws-security for a > > web service client application. How do I know ws-security is > enabled > > programmatically? I understand that in order to use > ws-security I need > > to do something in the configuration file axis2.xml and I > also need to > > put rampart/c as a module. But I also need to set the > security policy > > into the web service client object programmatically, right? > Then I > > need to know whether or not ws-security is enabled, and if > not, I > > don't need to set the policy (there is none actually) into > the ws > > client object. > > > > Thanks! > > Ray > > > > >
Re: How do I know ws-security is enabled programmatically?
When you create the svc_client you create the axis2_conf_ctx. This holds all the axis2 configurations. You can access the axis2_conf_ctx from svc_client and you can access the axis2_conf_t from axis2_conf_ctx_t. axis2_conf_t contains the list of all the engaged modules. Have a look at conf.c file. Supun. On Tue, Mar 10, 2009 at 8:41 AM, Raymond Zhou wrote: > Hi Manjula, > > Maybe my writing is a bit confusing, my question is not really about > setting the policy file programmatically, my question is about how I know > the ws-security is enabled programmatically (which means that the rampart/c > module is engaged in axis2/c configuration file). I need to know this > because my client code need to support both ws-security enabled and > ws-security disabled (the normal case), so that in the case of no > ws-security I don't have to read the policy file and set any ws-securit > related parameters programmatically. > > Thanks! > Ray > > --- On *Tue, 3/10/09, Manjula Peiris * wrote: > > > From: Manjula Peiris > Subject: Re: How do I know ws-security is enabled programmatically? > To: "Apache AXIS C User List" > Date: Tuesday, March 10, 2009, 3:12 AM > > > when you engage rampart there should be a policy to construct the > message. Please see Rampart/c samples for more info. > > On Mon, 2009-03-09 at 00:20 -0700, Raymond Zhou wrote: > > > > A quick question. I am using rampart/c to provide ws-security for a > > web service client application. How do I know ws-security is enabled > > programmatically? I understand that in order to use ws-security I need > > to do something in the configuration file axis2.xml and I also need to > > put rampart/c as a module. But I also need to set the security policy > > into the web service client object programmatically, right? Then I > > need to know whether or not ws-security is enabled, and if not, I > > don't need to set the policy (there is none actually) into the ws > > client object. > > > > Thanks! > > Ray > > > > > -- Software Engineer, WSO2 Inc http://wso2.org supunk.blogspot.com
Re: How do I know ws-security is enabled programmatically?
Hi, Raymond Zhou writes: > Maybe my writing is a bit confusing, my question is not really about setting > the policy file programmatically, my question is about how I know the > ws-security is enabled programmatically (which means that the rampart/c > module > is engaged in axis2/c configuration file). I need to know this because my > client code need to support both ws-security enabled and ws-security disabled > (the normal case), so that in the case of no ws-security I don't have to read > the policy file and set any ws-securit related parameters programmatically. You can see whether your client sends ws-security headers when ws-security enabled otherwise it should not send ws-security headers. thanks, Dinesh
Re: How do I know ws-security is enabled programmatically?
Hi Manjula, Maybe my writing is a bit confusing, my question is not really about setting the policy file programmatically, my question is about how I know the ws-security is enabled programmatically (which means that the rampart/c module is engaged in axis2/c configuration file). I need to know this because my client code need to support both ws-security enabled and ws-security disabled (the normal case), so that in the case of no ws-security I don't have to read the policy file and set any ws-securit related parameters programmatically. Thanks! Ray --- On Tue, 3/10/09, Manjula Peiris wrote: From: Manjula Peiris Subject: Re: How do I know ws-security is enabled programmatically? To: "Apache AXIS C User List" Date: Tuesday, March 10, 2009, 3:12 AM when you engage rampart there should be a policy to construct the message. Please see Rampart/c samples for more info. On Mon, 2009-03-09 at 00:20 -0700, Raymond Zhou wrote: > > A quick question. I am using rampart/c to provide ws-security for a > web service client application. How do I know ws-security is enabled > programmatically? I understand that in order to use ws-security I need > to do something in the configuration file axis2.xml and I also need to > put rampart/c as a module. But I also need to set the security policy > into the web service client object programmatically, right? Then I > need to know whether or not ws-security is enabled, and if not, I > don't need to set the policy (there is none actually) into the ws > client object. > > Thanks! > Ray >
Re: How do I know ws-security is enabled programmatically?
when you engage rampart there should be a policy to construct the message. Please see Rampart/c samples for more info. On Mon, 2009-03-09 at 00:20 -0700, Raymond Zhou wrote: > > A quick question. I am using rampart/c to provide ws-security for a > web service client application. How do I know ws-security is enabled > programmatically? I understand that in order to use ws-security I need > to do something in the configuration file axis2.xml and I also need to > put rampart/c as a module. But I also need to set the security policy > into the web service client object programmatically, right? Then I > need to know whether or not ws-security is enabled, and if not, I > don't need to set the policy (there is none actually) into the ws > client object. > > Thanks! > Ray >
How do I know ws-security is enabled programmatically?
Hi All, A quick question. I am using rampart/c to provide ws-security for a web service client application. How do I know ws-security is enabled programmatically? I understand that in order to use ws-security I need to do something in the configuration file axis2.xml and I also need to put rampart/c as a module. But I also need to set the security policy into the web service client object programmatically, right? Then I need to know whether or not ws-security is enabled, and if not, I don't need to set the policy (there is none actually) into the ws client object. Thanks! Ray
Re: What are the configurable ws-security parameters for incoming message
Rampart/C makes use of WS-Policy for configuring how it behaves. Samisa... Vivian Wang wrote: Hi, I am trying to use rampart/c along with axis2/c to support WS-security. Just wonder, what are the configurable ws-security parameters for incoming message, especially from a web service client point of view, which means, as a web service client, what can be configured to decrypt/interpret the response message from the web server. I've read through the manuals and also gone through the examples, but still I am afraid I don't have a complete picture about what can be configured. Is there any detailed document for this? I was also looking at soapUI, a free tool for web service testing, which also supports WS-security. In their manual, they have the following statements: Incoming WSS configurations are used to process incoming messages (responses, MockRequest and monitor requests/response) and decrypt/validate their encrypted/signed content. Since the WS-Security headers of an incoming message contain most of the information required to decrypt or validate a message, the only configuration needed by soapUI is which keystores that contain referenced keys and certificates for decryption and signature validation. Is this statement also true to rampart/c? I mean, the only configuration one need to do is which keystores that contain referenced keys and certificates for decryption and signature validation? Thanks much in advance! Vivian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Internal Virus Database is out of date. Checked by AVG - http://www.avg.com Version: 8.0.175 / Virus Database: 270.8.5/1759 - Release Date: 10/31/2008 4:10 PM -- Samisa Abeysinghe Director, Engineering; WSO2 Inc. http://www.wso2.com/ - "The Open Source SOA Company" - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis2] rampart problem using WS-SECURITY
Yes, this will be perfect. Thanks, -Dave. -Original Message- From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED] Sent: Thursday, November 16, 2006 9:19 PM To: Apache AXIS C User List Subject: Re: [Axis2] rampart problem using WS-SECURITY > In future I will try to insert security results as properties (e.g. > user id) to the message context after processing a security header, so > that we don't need to repeat the same processing in the service. +1. That is much user friendly. Samisa... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] rampart problem using WS-SECURITY
In future I will try to insert security results as properties (e.g. user id) to the message context after processing a security header, so that we don't need to repeat the same processing in the service. +1. That is much user friendly. Samisa... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] rampart problem using WS-SECURITY
Dave Meier wrote: Hi Kaushalye, I've got this all working now. Thanks for all your help. Not a problem :) I have a question: Is there a way to get the userid that was passed in the Security header from inside the server side implementation of a web service method? Yes. You can get the SOAP envelope from the msg ctx. And then get the Security header and process the Usernametoken. You can get the logic by going thru the invoke() method of rampart_in_handler.c Basically, I want to have my callback dll authenticate, but in my business logic on the server (a different dll), I still need to know what the userid is in order to perform the actions in the context of that user. I don't really care about the password as I know at that point that the client side has passed in the correct password, since it matches what I return from my callback dll. In future I will try to insert security results as properties (e.g. user id) to the message context after processing a security header, so that we don't need to repeat the same processing in the service. Thanks! -Dave. -Original Message- From: Kaushalye Kapuruge [mailto:[EMAIL PROTECTED] Sent: Thursday, November 16, 2006 12:17 AM To: Apache AXIS C User List Subject: Re: [Axis2] rampart problem using WS-SECURITY Hi Dave, Usernametoken building precess can be failed for following reasons. 1. Failure to specify the password either using Axis2 property "password" or using a callback module. (I think you are using callbacks) 2. Failure to specify callback module (path) correctly. 3. Failure to load the callback module (DLL in your case) correctly. 4. There is no such user in the system. i.e. The callback module cannot give a password for the user specified. If you can send the debug trace I might be able to identify where exactly the error is. I'll try to include more detailed log entries than this to make the debugging more easier. Cheers, Kaushalye Dave Meier wrote: Hi Kau, Sorry, I did some more testing back without using rampart. At first I was getting the same error that showed with rampart. After some fiddling around I got that working again and then set it up with Rampart again. Now I don't get the same error but it is failing with A different error "[rampart][rampart_out_handler] UsernmaeToken build failed. ERROR": [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_in_handler]Inflow Security found [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_in_handler] Validating UsernameToken [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_in_handler] Validating UsernameToken SUCCESS [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_in_handler] Validating Timestamp [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_in_handler] Validating Timestamp is SUCCESS [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase Dispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler addressing_based_dispatcher within the phase Dispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\addr_disp.c(108) Checking for service using WSA enpoint address : http://localhost:8181/axis2/services/ttwebservices [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\addr_disp.c(138) Service found using WSA enpoint address [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler request_uri_based_dispatcher within the phase Dispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler soap_action_based_dispatcher within the phase Dispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\soap_action_disp.c(108) Checking for operation using SOAPAction : [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler soap_message_body_based_dispatcher within the phase Dispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\soap_body_disp.c(198) Checking for operation using SOAP message body's first child's local name : CreatePrimaryItem [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\soap_body_disp.c(207) Operation found using SOAP message body's first child's local name [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase PostDispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler dispatch_post_conditions_evaluator within the phase PostDispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler context_handler within the phase PostDispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase PolicyDetermination [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invo
RE: [Axis2] rampart problem using WS-SECURITY
Hi Kaushalye, I've got this all working now. Thanks for all your help. I have a question: Is there a way to get the userid that was passed in the Security header from inside the server side implementation of a web service method? Basically, I want to have my callback dll authenticate, but in my business logic on the server (a different dll), I still need to know what the userid is in order to perform the actions in the context of that user. I don't really care about the password as I know at that point that the client side has passed in the correct password, since it matches what I return from my callback dll. Thanks! -Dave. -Original Message- From: Kaushalye Kapuruge [mailto:[EMAIL PROTECTED] Sent: Thursday, November 16, 2006 12:17 AM To: Apache AXIS C User List Subject: Re: [Axis2] rampart problem using WS-SECURITY Hi Dave, Usernametoken building precess can be failed for following reasons. 1. Failure to specify the password either using Axis2 property "password" or using a callback module. (I think you are using callbacks) 2. Failure to specify callback module (path) correctly. 3. Failure to load the callback module (DLL in your case) correctly. 4. There is no such user in the system. i.e. The callback module cannot give a password for the user specified. If you can send the debug trace I might be able to identify where exactly the error is. I'll try to include more detailed log entries than this to make the debugging more easier. Cheers, Kaushalye Dave Meier wrote: > Hi Kau, > > Sorry, I did some more testing back without using rampart. At first I > was getting the same error that showed with rampart. After some > fiddling around I got that working again and then set it up with > Rampart again. Now I don't get the same error but it is failing with A > different error "[rampart][rampart_out_handler] UsernmaeToken build > failed. ERROR": > > [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_in_handler]Inflow > Security found > [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_in_handler] > Validating UsernameToken [Tue Nov 14 21:42:32 2006] [info] > [rampart][rampart_in_handler] Validating UsernameToken SUCCESS [Tue > Nov 14 21:42:32 2006] [info] [rampart][rampart_in_handler] Validating > Timestamp [Tue Nov 14 21:42:32 2006] [info] > [rampart][rampart_in_handler] Validating Timestamp is SUCCESS [Tue Nov > 14 21:42:32 2006] [debug] > ..\..\modules\core\engine\engine.c(762) Invoking phase Dispatch [Tue > Nov 14 21:42:32 2006] [debug] > ..\..\modules\core\engine\phase.c(356) Invoke the handler > addressing_based_dispatcher within the phase Dispatch [Tue Nov 14 > 21:42:32 2006] [debug] > ..\..\modules\core\engine\addr_disp.c(108) Checking for service using > WSA enpoint address : > http://localhost:8181/axis2/services/ttwebservices > [Tue Nov 14 21:42:32 2006] [debug] > ..\..\modules\core\engine\addr_disp.c(138) Service found using WSA > enpoint address [Tue Nov 14 21:42:32 2006] [debug] > ..\..\modules\core\engine\phase.c(356) Invoke the handler > request_uri_based_dispatcher within the phase Dispatch [Tue Nov 14 > 21:42:32 2006] [debug] > ..\..\modules\core\engine\phase.c(356) Invoke the handler > soap_action_based_dispatcher within the phase Dispatch [Tue Nov 14 > 21:42:32 2006] [debug] > ..\..\modules\core\engine\soap_action_disp.c(108) Checking for > operation using SOAPAction : > [Tue Nov 14 21:42:32 2006] [debug] > ..\..\modules\core\engine\phase.c(356) Invoke the handler > soap_message_body_based_dispatcher within the phase Dispatch [Tue Nov > 14 21:42:32 2006] [debug] > ..\..\modules\core\engine\soap_body_disp.c(198) Checking for operation > using SOAP message body's first child's local name : CreatePrimaryItem > [Tue Nov 14 21:42:32 2006] [debug] > ..\..\modules\core\engine\soap_body_disp.c(207) Operation found using > SOAP message body's first child's local name [Tue Nov 14 21:42:32 > 2006] [debug] > ..\..\modules\core\engine\engine.c(762) Invoking phase PostDispatch > [Tue Nov 14 21:42:32 2006] [debug] > ..\..\modules\core\engine\phase.c(356) Invoke the handler > dispatch_post_conditions_evaluator within the phase PostDispatch [Tue > Nov 14 21:42:32 2006] [debug] > ..\..\modules\core\engine\phase.c(356) Invoke the handler > context_handler within the phase PostDispatch [Tue Nov 14 21:42:32 > 2006] [debug] > ..\..\modules\core\engine\engine.c(762) Invoking phase > PolicyDetermination [Tue Nov 14 21:42:32 2006] [debug] > ..\..\modules\core\engine\engine.c(762) Invoking phase > PolicyDetermination [Tue Nov 14 21:42:32 2006] [debug] > ..\..\modules\core\engine\engine.c(762) Invoking phase MessageOut [Tue > Nov 14 21:42:32 2006] [debug] > ..\..\modules\core\engine\phase.c(356) Invoke
Re: [Axis2] rampart problem using WS-SECURITY
Hi Dave, Usernametoken building precess can be failed for following reasons. 1. Failure to specify the password either using Axis2 property "password" or using a callback module. (I think you are using callbacks) 2. Failure to specify callback module (path) correctly. 3. Failure to load the callback module (DLL in your case) correctly. 4. There is no such user in the system. i.e. The callback module cannot give a password for the user specified. If you can send the debug trace I might be able to identify where exactly the error is. I'll try to include more detailed log entries than this to make the debugging more easier. Cheers, Kaushalye Dave Meier wrote: Hi Kau, Sorry, I did some more testing back without using rampart. At first I was getting the same error that showed with rampart. After some fiddling around I got that working again and then set it up with Rampart again. Now I don't get the same error but it is failing with A different error "[rampart][rampart_out_handler] UsernmaeToken build failed. ERROR": [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_in_handler]Inflow Security found [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_in_handler] Validating UsernameToken [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_in_handler] Validating UsernameToken SUCCESS [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_in_handler] Validating Timestamp [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_in_handler] Validating Timestamp is SUCCESS [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase Dispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler addressing_based_dispatcher within the phase Dispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\addr_disp.c(108) Checking for service using WSA enpoint address : http://localhost:8181/axis2/services/ttwebservices [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\addr_disp.c(138) Service found using WSA enpoint address [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler request_uri_based_dispatcher within the phase Dispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler soap_action_based_dispatcher within the phase Dispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\soap_action_disp.c(108) Checking for operation using SOAPAction : [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler soap_message_body_based_dispatcher within the phase Dispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\soap_body_disp.c(198) Checking for operation using SOAP message body's first child's local name : CreatePrimaryItem [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\soap_body_disp.c(207) Operation found using SOAP message body's first child's local name [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase PostDispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler dispatch_post_conditions_evaluator within the phase PostDispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler context_handler within the phase PostDispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase PolicyDetermination [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase PolicyDetermination [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase MessageOut [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler AddressingOutHandler within the phase MessageOut [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler RampartOutHandler within the phase MessageOut [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_out_handler] building UsernmaeToken [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_out_handler] UsernmaeToken build failed. ERROR [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\engine.c(445) Axis2 engine receive successful [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase MessageOut [Tue Nov 14 21:42:32 2006] [info] Request served successfully Thanks, -Dave. -Original Message- From: Dave Meier [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 14, 2006 9:27 PM To: Apache AXIS C User List Subject: RE: [Axis2] rampart problem using WS-SECURITY Hi Kau, 1. I used the Inflow/Outflow parameters like what is in the samples: UsernameToken Timestamp BILL passwordText D:/ttaxiswsse/Debug/ttwebserviceswsse.dll rdCallbackClass> 360 UsernameToken Timestamp D:/t
Re: [Axis2] rampart problem using WS-SECURITY
Dave Meier wrote: Well it appears to be just a problem with my callback dll on outflow as I took out the outflow portion in my axis2.xml and now it works. I can't figure out why my server side method was not being called before, but at least it's working well now. Hope you didn't spend much time looking into it. No problem.:) Glad that you have a solution. Thanks, -Dave. -Original Message- From: Dave Meier Sent: Tuesday, November 14, 2006 9:47 PM To: 'Apache AXIS C User List' Subject: RE: [Axis2] rampart problem using WS-SECURITY Hi Kau, Sorry, I did some more testing back without using rampart. At first I was getting the same error that showed with rampart. After some fiddling around I got that working again and then set it up with Rampart again. Now I don't get the same error but it is failing with A different error "[rampart][rampart_out_handler] UsernmaeToken build failed. ERROR": [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_in_handler]Inflow Security found [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_in_handler] Validating UsernameToken [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_in_handler] Validating UsernameToken SUCCESS [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_in_handler] Validating Timestamp [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_in_handler] Validating Timestamp is SUCCESS [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase Dispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler addressing_based_dispatcher within the phase Dispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\addr_disp.c(108) Checking for service using WSA enpoint address : http://localhost:8181/axis2/services/ttwebservices [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\addr_disp.c(138) Service found using WSA enpoint address [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler request_uri_based_dispatcher within the phase Dispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler soap_action_based_dispatcher within the phase Dispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\soap_action_disp.c(108) Checking for operation using SOAPAction : [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler soap_message_body_based_dispatcher within the phase Dispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\soap_body_disp.c(198) Checking for operation using SOAP message body's first child's local name : CreatePrimaryItem [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\soap_body_disp.c(207) Operation found using SOAP message body's first child's local name [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase PostDispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler dispatch_post_conditions_evaluator within the phase PostDispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler context_handler within the phase PostDispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase PolicyDetermination [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase PolicyDetermination [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase MessageOut [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler AddressingOutHandler within the phase MessageOut [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler RampartOutHandler within the phase MessageOut [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_out_handler] building UsernmaeToken [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_out_handler] UsernmaeToken build failed. ERROR [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\engine.c(445) Axis2 engine receive successful [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase MessageOut [Tue Nov 14 21:42:32 2006] [info] Request served successfully Thanks, -Dave. ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ---
RE: [Axis2] rampart problem using WS-SECURITY
Well it appears to be just a problem with my callback dll on outflow as I took out the outflow portion in my axis2.xml and now it works. I can't figure out why my server side method was not being called before, but at least it's working well now. Hope you didn't spend much time looking into it. Thanks, -Dave. -Original Message- From: Dave Meier Sent: Tuesday, November 14, 2006 9:47 PM To: 'Apache AXIS C User List' Subject: RE: [Axis2] rampart problem using WS-SECURITY Hi Kau, Sorry, I did some more testing back without using rampart. At first I was getting the same error that showed with rampart. After some fiddling around I got that working again and then set it up with Rampart again. Now I don't get the same error but it is failing with A different error "[rampart][rampart_out_handler] UsernmaeToken build failed. ERROR": [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_in_handler]Inflow Security found [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_in_handler] Validating UsernameToken [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_in_handler] Validating UsernameToken SUCCESS [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_in_handler] Validating Timestamp [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_in_handler] Validating Timestamp is SUCCESS [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase Dispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler addressing_based_dispatcher within the phase Dispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\addr_disp.c(108) Checking for service using WSA enpoint address : http://localhost:8181/axis2/services/ttwebservices [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\addr_disp.c(138) Service found using WSA enpoint address [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler request_uri_based_dispatcher within the phase Dispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler soap_action_based_dispatcher within the phase Dispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\soap_action_disp.c(108) Checking for operation using SOAPAction : [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler soap_message_body_based_dispatcher within the phase Dispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\soap_body_disp.c(198) Checking for operation using SOAP message body's first child's local name : CreatePrimaryItem [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\soap_body_disp.c(207) Operation found using SOAP message body's first child's local name [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase PostDispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler dispatch_post_conditions_evaluator within the phase PostDispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler context_handler within the phase PostDispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase PolicyDetermination [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase PolicyDetermination [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase MessageOut [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler AddressingOutHandler within the phase MessageOut [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler RampartOutHandler within the phase MessageOut [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_out_handler] building UsernmaeToken [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_out_handler] UsernmaeToken build failed. ERROR [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\engine.c(445) Axis2 engine receive successful [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase MessageOut [Tue Nov 14 21:42:32 2006] [info] Request served successfully Thanks, -Dave. ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis2] rampart problem using WS-SECURITY
Hi Kau, Sorry, I did some more testing back without using rampart. At first I was getting the same error that showed with rampart. After some fiddling around I got that working again and then set it up with Rampart again. Now I don't get the same error but it is failing with A different error "[rampart][rampart_out_handler] UsernmaeToken build failed. ERROR": [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_in_handler]Inflow Security found [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_in_handler] Validating UsernameToken [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_in_handler] Validating UsernameToken SUCCESS [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_in_handler] Validating Timestamp [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_in_handler] Validating Timestamp is SUCCESS [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase Dispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler addressing_based_dispatcher within the phase Dispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\addr_disp.c(108) Checking for service using WSA enpoint address : http://localhost:8181/axis2/services/ttwebservices [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\addr_disp.c(138) Service found using WSA enpoint address [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler request_uri_based_dispatcher within the phase Dispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler soap_action_based_dispatcher within the phase Dispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\soap_action_disp.c(108) Checking for operation using SOAPAction : [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler soap_message_body_based_dispatcher within the phase Dispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\soap_body_disp.c(198) Checking for operation using SOAP message body's first child's local name : CreatePrimaryItem [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\soap_body_disp.c(207) Operation found using SOAP message body's first child's local name [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase PostDispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler dispatch_post_conditions_evaluator within the phase PostDispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler context_handler within the phase PostDispatch [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase PolicyDetermination [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase PolicyDetermination [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase MessageOut [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler AddressingOutHandler within the phase MessageOut [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler RampartOutHandler within the phase MessageOut [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_out_handler] building UsernmaeToken [Tue Nov 14 21:42:32 2006] [info] [rampart][rampart_out_handler] UsernmaeToken build failed. ERROR [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\engine.c(445) Axis2 engine receive successful [Tue Nov 14 21:42:32 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase MessageOut [Tue Nov 14 21:42:32 2006] [info] Request served successfully Thanks, -Dave. -Original Message- From: Dave Meier [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 14, 2006 9:27 PM To: Apache AXIS C User List Subject: RE: [Axis2] rampart problem using WS-SECURITY Hi Kau, 1. I used the Inflow/Outflow parameters like what is in the samples: UsernameToken Timestamp BILL passwordText D:/ttaxiswsse/Debug/ttwebserviceswsse.dll 360 UsernameToken Timestamp D:/ttaxiswsse/Debug/ttwebserviceswsse.dll 2. Here is the trace of incoming and outgoing soap. I am using Visual Studio 2005 C# for the client side: Incoming: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"; xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wsse curity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssec urity-utility-1.0.xsd"> urn:uuid:527b7049-198f-4725-a2d7-bc861b4d36b3 http://sch
RE: [Axis2] rampart problem using WS-SECURITY
Hi Kau, 1. I used the Inflow/Outflow parameters like what is in the samples: UsernameToken Timestamp BILL passwordText D:/ttaxiswsse/Debug/ttwebserviceswsse.dll 360 UsernameToken Timestamp D:/ttaxiswsse/Debug/ttwebserviceswsse.dll 2. Here is the trace of incoming and outgoing soap. I am using Visual Studio 2005 C# for the client side: Incoming: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"; xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wsse curity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssec urity-utility-1.0.xsd"> urn:uuid:527b7049-198f-4725-a2d7-bc861b4d36b3 http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anony mous http://localhost:8181/axis2/services/ttwebservices 2006-11-15T05:22:08Z 2006-11-15T05:23:08Z http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssec urity-utility-1.0.xsd" wsu:Id="SecurityToken-b7689ab1-70e9-4472-8386-0880eb2180fe"> bill http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-t oken-profile-1.0#PasswordText">b vVR7Rzg8oLtLfg5NjxWV1g== 2006-11-15T05:22:08Z 16 BUG Image Builder my title my desc bill 2006-01-01T00:12:12 bill 2006-01-01T00:12:12 true Waiting joe FOUND_IN_VERSION v1.1 FUNCTIONAL_AREA Help Outgoing: http://schemas.xmlsoap.org/soap/envelope/";> When I use the same client code without WS-SECURITY and take rampart out of the axis2.xml, my web service method does get called and everything gets returned correctly to the client. Thanks, -Dave. -Original Message- From: Kaushalye Kapuruge [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 14, 2006 9:02 PM To: Apache AXIS C User List Subject: Re: [Axis2] rampart problem using WS-SECURITY Hi, I need some information from you to figure out what exactly is the problem. 1. Have you specified the Outflow/InflowSecurity parameters correctly using axis2.xml If you have any questions on this do not hesitate to ask me. Have a look at the sample axis2.xml file in rampart/samples/client/echo/data/un_ts_axis2.xml. 2. Is it possible to send a trace of outgoing message. (You may use TCPMonitor for this) BTW from log entries I can see that Rampart has done the validation correct. But in the message building has failed in the server side. This "might" be due to improper settings in the server side. Try the latest code. But do not use the encryption yet:) It is still under development. Cheers, Kau Dave Meier wrote: > Hi, > > Okay, I got the latest code. I had to add "#include > " to the rampart_encryption.c file in order to > get it to link on Windows. Now it returns an empty message as it's > not invoking my service method: > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> > > > > > The log below shows "[error] > ..\..\modules\core\receivers\raw_xml_in_out_msg_recv.c(114) Impl > object for service 'ttwebservices' not set in message receiver. 0 :: No Error". > > Please let me know if there is something I am doing wrong. I'll go > look at the source code to see if I can figure it out. > > > [Tue Nov 14 11:24:07 2006] [info] [rampart][rampart_in_handler]Inflow > Security found > [Tue Nov 14 11:24:07 2006] [info] [rampart][rampart_in_handler] > Validating UsernameToken [Tue Nov 14 11:24:07 2006] [info] > [rampart][rampart_in_handler] Validating UsernameToken SUCCESS [Tue > Nov 14 11:24:07 2006] [info] [rampart][rampart_in_handler] Validating > Timestamp [Tue Nov 14 11:24:07 2006] [info] > [rampart][rampart_in_handler] Validating Timestamp is SUCCESS [Tue Nov > 14 11:24:07 2006] [debug] > ..\..\modules\core\engine\engine.c(762) Invoking phase Dispatch [Tue > Nov 14 11:24:07 2006] [debug] > ..\..\modules\core\engine\phase.c(356)
Re: [Axis2] rampart problem using WS-SECURITY
Hi, I need some information from you to figure out what exactly is the problem. 1. Have you specified the Outflow/InflowSecurity parameters correctly using axis2.xml If you have any questions on this do not hesitate to ask me. Have a look at the sample axis2.xml file in rampart/samples/client/echo/data/un_ts_axis2.xml. 2. Is it possible to send a trace of outgoing message. (You may use TCPMonitor for this) BTW from log entries I can see that Rampart has done the validation correct. But in the message building has failed in the server side. This "might" be due to improper settings in the server side. Try the latest code. But do not use the encryption yet:) It is still under development. Cheers, Kau Dave Meier wrote: Hi, Okay, I got the latest code. I had to add "#include " to the rampart_encryption.c file in order to get it to link on Windows. Now it returns an empty message as it's not invoking my service method: http://schemas.xmlsoap.org/soap/envelope/";> The log below shows "[error] ..\..\modules\core\receivers\raw_xml_in_out_msg_recv.c(114) Impl object for service 'ttwebservices' not set in message receiver. 0 :: No Error". Please let me know if there is something I am doing wrong. I'll go look at the source code to see if I can figure it out. [Tue Nov 14 11:24:07 2006] [info] [rampart][rampart_in_handler]Inflow Security found [Tue Nov 14 11:24:07 2006] [info] [rampart][rampart_in_handler] Validating UsernameToken [Tue Nov 14 11:24:07 2006] [info] [rampart][rampart_in_handler] Validating UsernameToken SUCCESS [Tue Nov 14 11:24:07 2006] [info] [rampart][rampart_in_handler] Validating Timestamp [Tue Nov 14 11:24:07 2006] [info] [rampart][rampart_in_handler] Validating Timestamp is SUCCESS [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase Dispatch [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler addressing_based_dispatcher within the phase Dispatch [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\addr_disp.c(108) Checking for service using WSA enpoint address : http://localhost:8181/axis2/services/ttwebservices [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\addr_disp.c(138) Service found using WSA enpoint address [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler request_uri_based_dispatcher within the phase Dispatch [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler soap_action_based_dispatcher within the phase Dispatch [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\soap_action_disp.c(108) Checking for operation using SOAPAction : [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler soap_message_body_based_dispatcher within the phase Dispatch [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\soap_body_disp.c(198) Checking for operation using SOAP message body's first child's local name : CreatePrimaryItem [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\soap_body_disp.c(207) Operation found using SOAP message body's first child's local name [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase PostDispatch [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler dispatch_post_conditions_evaluator within the phase PostDispatch [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler context_handler within the phase PostDispatch [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase PolicyDetermination [Tue Nov 14 11:24:07 2006] [error] ..\..\modules\core\receivers\raw_xml_in_out_msg_recv.c(114) Impl object for service 'ttwebservices' not set in message receiver. 0 :: No Error [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\engine.c(445) Axis2 engine receive successful [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase MessageOut [Tue Nov 14 11:24:07 2006] [info] Request served successfully Thanks, -Dave. -Original Message- From: Dave Meier [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 14, 2006 7:35 AM To: Apache AXIS C User List Subject: RE: [Axis2] rampart problem using WS-SECURITY Thanks for the quick fix - I'll go try it out right now. I am using Visual Studio 2005 C# on the client side. We'll be supporting C#, Axis2 Java and Axis2C for our client side implementations. Other projects here already use Axis2 for Java. -Dave. -Original Message- From: Kaushalye Kapuruge [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 14, 2006 1:24 AM To: Apache AXIS C User List Subject: Re: [Axis2] rampart problem using WS-SECURITY Kaushalye Kapuruge wrote: Dave Meier wrote:
RE: [Axis2] rampart problem using WS-SECURITY
Forgot to mention two other changes I made to my copy of the code: 1. In asym_ctx.c: renamed "oxs_asym_ctx_create_asym_ctx" method to "oxs_asym_ctx_create" as that is what's defined in the header file. 2. In rampart_encryption.c, added an ampersand to the last argument in this call as it takes an "axiom_node_t **enc_type_node": enc_status = oxs_xml_enc_encrypt_node(env, enc_ctx, node_to_enc, &enc_data_node); -Dave. -Original Message- From: Dave Meier [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 14, 2006 11:41 AM To: Apache AXIS C User List Subject: RE: [Axis2] rampart problem using WS-SECURITY Hi, Okay, I got the latest code. I had to add "#include " to the rampart_encryption.c file in order to get it to link on Windows. Now it returns an empty message as it's not invoking my service method: http://schemas.xmlsoap.org/soap/envelope/";> The log below shows "[error] ..\..\modules\core\receivers\raw_xml_in_out_msg_recv.c(114) Impl object for service 'ttwebservices' not set in message receiver. 0 :: No Error". Please let me know if there is something I am doing wrong. I'll go look at the source code to see if I can figure it out. [Tue Nov 14 11:24:07 2006] [info] [rampart][rampart_in_handler]Inflow Security found [Tue Nov 14 11:24:07 2006] [info] [rampart][rampart_in_handler] Validating UsernameToken [Tue Nov 14 11:24:07 2006] [info] [rampart][rampart_in_handler] Validating UsernameToken SUCCESS [Tue Nov 14 11:24:07 2006] [info] [rampart][rampart_in_handler] Validating Timestamp [Tue Nov 14 11:24:07 2006] [info] [rampart][rampart_in_handler] Validating Timestamp is SUCCESS [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase Dispatch [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler addressing_based_dispatcher within the phase Dispatch [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\addr_disp.c(108) Checking for service using WSA enpoint address : http://localhost:8181/axis2/services/ttwebservices [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\addr_disp.c(138) Service found using WSA enpoint address [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler request_uri_based_dispatcher within the phase Dispatch [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler soap_action_based_dispatcher within the phase Dispatch [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\soap_action_disp.c(108) Checking for operation using SOAPAction : [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler soap_message_body_based_dispatcher within the phase Dispatch [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\soap_body_disp.c(198) Checking for operation using SOAP message body's first child's local name : CreatePrimaryItem [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\soap_body_disp.c(207) Operation found using SOAP message body's first child's local name [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase PostDispatch [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler dispatch_post_conditions_evaluator within the phase PostDispatch [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler context_handler within the phase PostDispatch [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase PolicyDetermination [Tue Nov 14 11:24:07 2006] [error] ..\..\modules\core\receivers\raw_xml_in_out_msg_recv.c(114) Impl object for service 'ttwebservices' not set in message receiver. 0 :: No Error [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\engine.c(445) Axis2 engine receive successful [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase MessageOut [Tue Nov 14 11:24:07 2006] [info] Request served successfully Thanks, -Dave. -Original Message- From: Dave Meier [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 14, 2006 7:35 AM To: Apache AXIS C User List Subject: RE: [Axis2] rampart problem using WS-SECURITY Thanks for the quick fix - I'll go try it out right now. I am using Visual Studio 2005 C# on the client side. We'll be supporting C#, Axis2 Java and Axis2C for our client side implementations. Other projects here already use Axis2 for Java. -Dave. -Original Message- From: Kaushalye Kapuruge [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 14, 2006 1:24 AM To: Apache AXIS C User List Subject: Re: [Axis2] rampart problem using WS-SECURITY Kaushalye Kapuruge wrote: > Dave Meier wrote: >> I have the rampart module hooked up and my password callback is >>
RE: [Axis2] rampart problem using WS-SECURITY
Hi, Okay, I got the latest code. I had to add "#include " to the rampart_encryption.c file in order to get it to link on Windows. Now it returns an empty message as it's not invoking my service method: http://schemas.xmlsoap.org/soap/envelope/";> The log below shows "[error] ..\..\modules\core\receivers\raw_xml_in_out_msg_recv.c(114) Impl object for service 'ttwebservices' not set in message receiver. 0 :: No Error". Please let me know if there is something I am doing wrong. I'll go look at the source code to see if I can figure it out. [Tue Nov 14 11:24:07 2006] [info] [rampart][rampart_in_handler]Inflow Security found [Tue Nov 14 11:24:07 2006] [info] [rampart][rampart_in_handler] Validating UsernameToken [Tue Nov 14 11:24:07 2006] [info] [rampart][rampart_in_handler] Validating UsernameToken SUCCESS [Tue Nov 14 11:24:07 2006] [info] [rampart][rampart_in_handler] Validating Timestamp [Tue Nov 14 11:24:07 2006] [info] [rampart][rampart_in_handler] Validating Timestamp is SUCCESS [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase Dispatch [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler addressing_based_dispatcher within the phase Dispatch [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\addr_disp.c(108) Checking for service using WSA enpoint address : http://localhost:8181/axis2/services/ttwebservices [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\addr_disp.c(138) Service found using WSA enpoint address [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler request_uri_based_dispatcher within the phase Dispatch [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler soap_action_based_dispatcher within the phase Dispatch [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\soap_action_disp.c(108) Checking for operation using SOAPAction : [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler soap_message_body_based_dispatcher within the phase Dispatch [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\soap_body_disp.c(198) Checking for operation using SOAP message body's first child's local name : CreatePrimaryItem [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\soap_body_disp.c(207) Operation found using SOAP message body's first child's local name [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase PostDispatch [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler dispatch_post_conditions_evaluator within the phase PostDispatch [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler context_handler within the phase PostDispatch [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase PolicyDetermination [Tue Nov 14 11:24:07 2006] [error] ..\..\modules\core\receivers\raw_xml_in_out_msg_recv.c(114) Impl object for service 'ttwebservices' not set in message receiver. 0 :: No Error [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\engine.c(445) Axis2 engine receive successful [Tue Nov 14 11:24:07 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase MessageOut [Tue Nov 14 11:24:07 2006] [info] Request served successfully Thanks, -Dave. -Original Message- From: Dave Meier [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 14, 2006 7:35 AM To: Apache AXIS C User List Subject: RE: [Axis2] rampart problem using WS-SECURITY Thanks for the quick fix - I'll go try it out right now. I am using Visual Studio 2005 C# on the client side. We'll be supporting C#, Axis2 Java and Axis2C for our client side implementations. Other projects here already use Axis2 for Java. -Dave. -Original Message- From: Kaushalye Kapuruge [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 14, 2006 1:24 AM To: Apache AXIS C User List Subject: Re: [Axis2] rampart problem using WS-SECURITY Kaushalye Kapuruge wrote: > Dave Meier wrote: >> I have the rampart module hooked up and my password callback is >> called correctly. But after successful validation, my web service >> method does not get called. Instead I get back the following response: >> >> > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> >> >> >> >> soapenv:MustUnderstand >> Header not understood >> >> >> >> >> This occurs after the userid and password have already been validated. >> Here are the log entries: >> >> [Mon Nov 13 17:01:14 2006] [debug] >> ..\..\modules\core\transport\http\http_worker.c(204) Client HTTP
RE: [Axis2] rampart problem using WS-SECURITY
Thanks for the quick fix - I'll go try it out right now. I am using Visual Studio 2005 C# on the client side. We'll be supporting C#, Axis2 Java and Axis2C for our client side implementations. Other projects here already use Axis2 for Java. -Dave. -Original Message- From: Kaushalye Kapuruge [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 14, 2006 1:24 AM To: Apache AXIS C User List Subject: Re: [Axis2] rampart problem using WS-SECURITY Kaushalye Kapuruge wrote: > Dave Meier wrote: >> I have the rampart module hooked up and my password callback is >> called correctly. But after successful validation, my web service >> method does not get called. Instead I get back the following response: >> >> > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> >> >> >> >> soapenv:MustUnderstand >> Header not understood >> >> >> >> >> This occurs after the userid and password have already been validated. >> Here are the log entries: >> >> [Mon Nov 13 17:01:14 2006] [debug] >> ..\..\modules\core\transport\http\http_worker.c(204) Client HTTP >> version >> HTTP/1.1 >> [Mon Nov 13 17:01:14 2006] [debug] >> ..\..\axiom\src\soap\soap_builder.c(840) Identified soap version is >> soap11 >> [Mon Nov 13 17:01:14 2006] [debug] >> ..\..\modules\core\engine\engine.c(762) Invoking phase TransportIn >> [Mon Nov 13 17:01:14 2006] [debug] >> ..\..\modules\core\engine\engine.c(762) Invoking phase PreDispatch >> [Mon Nov 13 17:01:14 2006] [debug] >> ..\..\modules\core\engine\phase.c(356) Invoke the handler >> AddressingInHandler within the phase PreDispatch [Mon Nov 13 17:01:14 >> 2006] [info] Starting addressing in handler . >> [Mon Nov 13 17:01:14 2006] [debug] >> ..\..\modules\core\engine\phase.c(356) Invoke the handler >> RampartInHandler within the phase PreDispatch [Mon Nov 13 17:01:14 >> 2006] [info] [rampart][rampart_in_handler]Inflow >> Security found >> [Mon Nov 13 17:01:14 2006] [info] [rampart][rampart_in_handler] >> Validating UsernameToken [Mon Nov 13 17:01:14 2006] [info] >> [rampart][rampart_in_handler] Validating UsernameToken SUCCESS [Mon >> Nov 13 17:01:14 2006] [info] [rampart][rampart_in_handler] >> Validating Timestamp [Mon Nov 13 17:01:14 2006] [info] >> [rampart][rampart_in_handler] Validating Timestamp is SUCCESS [Mon >> Nov 13 17:01:14 2006] [debug] >> ..\..\modules\core\engine\engine.c(762) Invoking phase Dispatch [Mon >> Nov 13 17:01:14 2006] [debug] >> ..\..\modules\core\engine\phase.c(356) Invoke the handler >> addressing_based_dispatcher within the phase Dispatch [Mon Nov 13 >> 17:01:14 2006] [debug] >> ..\..\modules\core\engine\addr_disp.c(99) Checking for service using >> WSA enpoint address : >> http://localhost:8181/axis2/services/ttwebservices >> [Mon Nov 13 17:01:14 2006] [debug] >> ..\..\modules\core\engine\addr_disp.c(129) Service found using WSA >> enpoint address [Mon Nov 13 17:01:14 2006] [debug] >> ..\..\modules\core\engine\phase.c(356) Invoke the handler >> request_uri_based_dispatcher within the phase Dispatch [Mon Nov 13 >> 17:01:14 2006] [debug] >> ..\..\modules\core\engine\phase.c(356) Invoke the handler >> soap_action_based_dispatcher within the phase Dispatch [Mon Nov 13 >> 17:01:14 2006] [debug] >> ..\..\modules\core\engine\soap_action_disp.c(106) Checking for >> operation using SOAPAction : [Mon Nov 13 17:01:14 2006] [debug] >> ..\..\modules\core\engine\phase.c(356) Invoke the handler >> soap_message_body_based_dispatcher within the phase Dispatch [Mon Nov >> 13 17:01:14 2006] [debug] >> ..\..\modules\core\engine\soap_body_disp.c(196) Checking for >> operation using SOAP message body's first child's local name : >> CreatePrimaryItem [Mon Nov 13 17:01:14 2006] [debug] >> ..\..\modules\core\engine\soap_body_disp.c(205) Operation found using >> SOAP message body's first child's local name [Mon Nov 13 17:01:14 >> 2006] [debug] >> ..\..\modules\core\engine\engine.c(762) Invoking phase PostDispatch >> [Mon Nov 13 17:01:14 2006] [debug] >> ..\..\modules\core\engine\phase.c(356) Invoke the handler >> dispatch_post_conditions_evaluator within the phase PostDispatch [Mon >> Nov 13 17:01:14 2006] [debug] >> ..\..\modules\core\engine\phase.c(356) Invoke the handler >> context_handler within the phase PostDispatch [Mon Nov 13 17:01:14 >> 2006] [debug] >> ..\..\modules\core\engine\engine.c(762) Invoking phase >> PolicyDeterminatio
Re: [Axis2] rampart problem using WS-SECURITY
Dave Meier wrote: I have the rampart module hooked up and my password callback is called correctly. But after successful validation, my web service method does not get called. Instead I get back the following response: http://schemas.xmlsoap.org/soap/envelope/";> soapenv:MustUnderstand Header not understood This occurs after the userid and password have already been validated. Here are the log entries: [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\transport\http\http_worker.c(204) Client HTTP version HTTP/1.1 [Mon Nov 13 17:01:14 2006] [debug] ..\..\axiom\src\soap\soap_builder.c(840) Identified soap version is soap11 [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase TransportIn [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase PreDispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler AddressingInHandler within the phase PreDispatch [Mon Nov 13 17:01:14 2006] [info] Starting addressing in handler . [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler RampartInHandler within the phase PreDispatch [Mon Nov 13 17:01:14 2006] [info] [rampart][rampart_in_handler]Inflow Security found [Mon Nov 13 17:01:14 2006] [info] [rampart][rampart_in_handler] Validating UsernameToken [Mon Nov 13 17:01:14 2006] [info] [rampart][rampart_in_handler] Validating UsernameToken SUCCESS [Mon Nov 13 17:01:14 2006] [info] [rampart][rampart_in_handler] Validating Timestamp [Mon Nov 13 17:01:14 2006] [info] [rampart][rampart_in_handler] Validating Timestamp is SUCCESS [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase Dispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler addressing_based_dispatcher within the phase Dispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\addr_disp.c(99) Checking for service using WSA enpoint address : http://localhost:8181/axis2/services/ttwebservices [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\addr_disp.c(129) Service found using WSA enpoint address [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler request_uri_based_dispatcher within the phase Dispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler soap_action_based_dispatcher within the phase Dispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\soap_action_disp.c(106) Checking for operation using SOAPAction : [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler soap_message_body_based_dispatcher within the phase Dispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\soap_body_disp.c(196) Checking for operation using SOAP message body's first child's local name : CreatePrimaryItem [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\soap_body_disp.c(205) Operation found using SOAP message body's first child's local name [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase PostDispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler dispatch_post_conditions_evaluator within the phase PostDispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler context_handler within the phase PostDispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase PolicyDetermination [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase MessageOut [Mon Nov 13 17:01:14 2006] [info] Request served successfully I did have mustUnderstand set in the request like this: " Rampart_in_handler should set this relaying attribute to false after processing. Thanks for pointing this out. BTW, are you using a rampart in the client side as well? Or is it another implementation? :) 'Coz rampart doesn't set mustUnderstand=1. How can I get around this? Thanks, -Dave. ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] rampart problem using WS-SECURITY
Kaushalye Kapuruge wrote: Dave Meier wrote: I have the rampart module hooked up and my password callback is called correctly. But after successful validation, my web service method does not get called. Instead I get back the following response: http://schemas.xmlsoap.org/soap/envelope/";> soapenv:MustUnderstand Header not understood This occurs after the userid and password have already been validated. Here are the log entries: [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\transport\http\http_worker.c(204) Client HTTP version HTTP/1.1 [Mon Nov 13 17:01:14 2006] [debug] ..\..\axiom\src\soap\soap_builder.c(840) Identified soap version is soap11 [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase TransportIn [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase PreDispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler AddressingInHandler within the phase PreDispatch [Mon Nov 13 17:01:14 2006] [info] Starting addressing in handler . [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler RampartInHandler within the phase PreDispatch [Mon Nov 13 17:01:14 2006] [info] [rampart][rampart_in_handler]Inflow Security found [Mon Nov 13 17:01:14 2006] [info] [rampart][rampart_in_handler] Validating UsernameToken [Mon Nov 13 17:01:14 2006] [info] [rampart][rampart_in_handler] Validating UsernameToken SUCCESS [Mon Nov 13 17:01:14 2006] [info] [rampart][rampart_in_handler] Validating Timestamp [Mon Nov 13 17:01:14 2006] [info] [rampart][rampart_in_handler] Validating Timestamp is SUCCESS [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase Dispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler addressing_based_dispatcher within the phase Dispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\addr_disp.c(99) Checking for service using WSA enpoint address : http://localhost:8181/axis2/services/ttwebservices [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\addr_disp.c(129) Service found using WSA enpoint address [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler request_uri_based_dispatcher within the phase Dispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler soap_action_based_dispatcher within the phase Dispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\soap_action_disp.c(106) Checking for operation using SOAPAction : [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler soap_message_body_based_dispatcher within the phase Dispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\soap_body_disp.c(196) Checking for operation using SOAP message body's first child's local name : CreatePrimaryItem [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\soap_body_disp.c(205) Operation found using SOAP message body's first child's local name [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase PostDispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler dispatch_post_conditions_evaluator within the phase PostDispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler context_handler within the phase PostDispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase PolicyDetermination [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase MessageOut [Mon Nov 13 17:01:14 2006] [info] Request served successfully I did have mustUnderstand set in the request like this: " Rampart_in_handler should set this relaying attribute to false after processing. Thanks for pointing this out. BTW, are you using a rampart in the client side as well? Or is it another implementation? :) 'Coz rampart doesn't set mustUnderstand=1. How can I get around this? Get the latest code from the svn. Cheers, Thanks, -Dave. ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional command
Re: [Axis2] rampart problem using WS-SECURITY
Kaushalye Kapuruge wrote: Dave Meier wrote: I have the rampart module hooked up and my password callback is called correctly. But after successful validation, my web service method does not get called. Instead I get back the following response: http://schemas.xmlsoap.org/soap/envelope/";> soapenv:MustUnderstand Header not understood This occurs after the userid and password have already been validated. Here are the log entries: [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\transport\http\http_worker.c(204) Client HTTP version HTTP/1.1 [Mon Nov 13 17:01:14 2006] [debug] ..\..\axiom\src\soap\soap_builder.c(840) Identified soap version is soap11 [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase TransportIn [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase PreDispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler AddressingInHandler within the phase PreDispatch [Mon Nov 13 17:01:14 2006] [info] Starting addressing in handler . [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler RampartInHandler within the phase PreDispatch [Mon Nov 13 17:01:14 2006] [info] [rampart][rampart_in_handler]Inflow Security found [Mon Nov 13 17:01:14 2006] [info] [rampart][rampart_in_handler] Validating UsernameToken [Mon Nov 13 17:01:14 2006] [info] [rampart][rampart_in_handler] Validating UsernameToken SUCCESS [Mon Nov 13 17:01:14 2006] [info] [rampart][rampart_in_handler] Validating Timestamp [Mon Nov 13 17:01:14 2006] [info] [rampart][rampart_in_handler] Validating Timestamp is SUCCESS [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase Dispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler addressing_based_dispatcher within the phase Dispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\addr_disp.c(99) Checking for service using WSA enpoint address : http://localhost:8181/axis2/services/ttwebservices [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\addr_disp.c(129) Service found using WSA enpoint address [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler request_uri_based_dispatcher within the phase Dispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler soap_action_based_dispatcher within the phase Dispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\soap_action_disp.c(106) Checking for operation using SOAPAction : [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler soap_message_body_based_dispatcher within the phase Dispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\soap_body_disp.c(196) Checking for operation using SOAP message body's first child's local name : CreatePrimaryItem [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\soap_body_disp.c(205) Operation found using SOAP message body's first child's local name [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase PostDispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler dispatch_post_conditions_evaluator within the phase PostDispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler context_handler within the phase PostDispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase PolicyDetermination [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase MessageOut [Mon Nov 13 17:01:14 2006] [info] Request served successfully I did have mustUnderstand set in the request like this: " Rampart_in_handler should set this relaying attribute to false after processing. Thanks for pointing this out. BTW, are you using a rampart in the client side as well? Or is it another implementation? :) 'Coz rampart doesn't set mustUnderstand=1. How can I get around this? Get the latest code from the svn. Cheers, Thanks, -Dave. ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional command
RE: [Axis2] rampart problem using WS-SECURITY
I have the rampart module hooked up and my password callback is called correctly. But after successful validation, my web service method does not get called. Instead I get back the following response: http://schemas.xmlsoap.org/soap/envelope/";> soapenv:MustUnderstand Header not understood This occurs after the userid and password have already been validated. Here are the log entries: [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\transport\http\http_worker.c(204) Client HTTP version HTTP/1.1 [Mon Nov 13 17:01:14 2006] [debug] ..\..\axiom\src\soap\soap_builder.c(840) Identified soap version is soap11 [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase TransportIn [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase PreDispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler AddressingInHandler within the phase PreDispatch [Mon Nov 13 17:01:14 2006] [info] Starting addressing in handler . [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler RampartInHandler within the phase PreDispatch [Mon Nov 13 17:01:14 2006] [info] [rampart][rampart_in_handler]Inflow Security found [Mon Nov 13 17:01:14 2006] [info] [rampart][rampart_in_handler] Validating UsernameToken [Mon Nov 13 17:01:14 2006] [info] [rampart][rampart_in_handler] Validating UsernameToken SUCCESS [Mon Nov 13 17:01:14 2006] [info] [rampart][rampart_in_handler] Validating Timestamp [Mon Nov 13 17:01:14 2006] [info] [rampart][rampart_in_handler] Validating Timestamp is SUCCESS [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase Dispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler addressing_based_dispatcher within the phase Dispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\addr_disp.c(99) Checking for service using WSA enpoint address : http://localhost:8181/axis2/services/ttwebservices [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\addr_disp.c(129) Service found using WSA enpoint address [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler request_uri_based_dispatcher within the phase Dispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler soap_action_based_dispatcher within the phase Dispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\soap_action_disp.c(106) Checking for operation using SOAPAction : [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler soap_message_body_based_dispatcher within the phase Dispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\soap_body_disp.c(196) Checking for operation using SOAP message body's first child's local name : CreatePrimaryItem [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\soap_body_disp.c(205) Operation found using SOAP message body's first child's local name [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase PostDispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler dispatch_post_conditions_evaluator within the phase PostDispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\phase.c(356) Invoke the handler context_handler within the phase PostDispatch [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase PolicyDetermination [Mon Nov 13 17:01:14 2006] [debug] ..\..\modules\core\engine\engine.c(762) Invoking phase MessageOut [Mon Nov 13 17:01:14 2006] [info] Request served successfully I did have mustUnderstand set in the request like this: " How can I get around this? Thanks, -Dave. ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: WS-Security
If you're not worried about performance this is an option. However, I personally wouldn't recommend it as a design that I'd be happy with. If Samisa is right about the username/passwd in the SOAP Haader then you might not have to resort to such drastic measures :-) Let's work out what you're missing and then see if we can put it in. "Patrick Heffernan" <[EMAIL PROTECTED]> 12/05/2005 19:29 Please respond to "Apache AXIS C User List" To "'Apache AXIS C User List'" cc Subject RE: WS-Security Could I use JNI and call the java classes/methods generated by wsdl2ws from my C++ application? Thoughts on this approach? pat -Original Message- From: Patrick Heffernan [mailto:[EMAIL PROTECTED] Sent: Thursday, May 12, 2005 11:12 AM To: 'Apache AXIS C User List' Subject: RE: WS-Security Hi Samisa, Dinesh, and John, Thanks for taking on my WS-Security question. I've got a Linux C++ application that I'm modifying to send web services requests to a Microsoft WS server that is implementing the Web Services Enhancements (WSE) package that includes WS-Security. I have no choice in the server as we are a third party developer that is integrating our product into an existing system (and we're not a Microsoft shop to boot -- so not taking on a MS WS client!). I've had them turn off the security stuff on the dev system we're testing against so I can continue my application dev/testing but the WS-Security obviously needs to be in place for us to go to production. This is the format of soap messages I am required to support: http://webservices.cox.com/CustomerProfile/GetProfileByAccountNumberAndSiteId http://iwslib/cox.web.services.profile/ServiceCustomer.asmx uuid:0c58b657-0242-4e43-9bf7-68904b9e6294 2005-05-11T14:41:07Z 2005-05-11T14:46:07Z webserviceuser aa xmOrtuc7SgN2QoFJgBk8uw== 2005-05-11T14:41:07Z qRU8kf9YQDtevGGRLqbJ7k5biuc= FMEJoIBD7T0uXY3eizSz0oiwzRE= wdST6LxVV+0XOZ7xqhVe9zIJ2G4= 2MJUGSiUzDLBFyDAH0OrJP46R6k= cqRYyBRHatKNRvAQM01OrvBERyw= j6AxeTlBcpfKuVJHD1TvoMuEaes= IwEDjgV/jC/HjyXPxyzaF738eZc= 0 It sounds like you guys have done alot of good work on this. What are the chances of getting it completed in the near future? Other than me trying to hack something to make it work, do I have any other options? Thanks again, pat -Original Message- From: John Hawkins [mailto:[EMAIL PROTECTED] Sent: Thursday, May 12, 2005 3:30 AM To: Apache AXIS C User List Subject: Re: WS-Security So, it doesn't sound like we're that far off - if we just implement the getSOAPBodyAsString() method then we would be able to have ws-security on client-side (at least)? Din%$h <[EMAIL PROTECTED]> 12/05/2005 10:21 Please respond to "Apache AXIS C User List" To Apache AXIS C User List cc Subject Re: WS-Security Hi John, Let me breif what we tried to do. When Client make a request , we get the Body from the serializer and Encrypt it again set those encrypted Body to the message. At the server end we got the encrypted message from the deserializer and decrypted it. and get the original message. For the response flow also scenario remains same. We hoped to do it using an handler. Since there was a method called getBodyAsString(), (as I remember). We creadted DOM tree using that body. ( If we could get Object Model that was easier). giving soap message as a String I was able to Encrypt it and Giving that Encrypt message I was able to got that original message too. Since there wasn't a way to get acess to the Body( getSoapBodyAsString () or any other method which can access body didn't implemented at that time). We didn't able to integrate it with axis using a handler. regards, Dinesh On 5/12/05, John Hawkins <[EMAIL PROTECTED]> wrote: Hi Dinesh, Can I ask - how you wanted that soap body? Would you need a byte stream or an object model? Was this client or server side or both? Was it on the outgoing or incoming message or both? cheers, John. Din%$h <[EMAIL PROTECTED]> 1
RE: WS-Security
Title: Message
I mean
wsdl2java instead of wsdl2ws.
pat
-Original Message-From: Patrick
Heffernan [mailto:[EMAIL PROTECTED] Sent:
Thursday, May 12, 2005 11:29 AMTo: 'Apache AXIS C User
List'Subject: RE: WS-Security
Could I use JNI and call the java classes/methods generated by wsdl2ws
from my C++ application? Thoughts on this approach?
pat
-Original Message-From: Patrick
Heffernan [mailto:[EMAIL PROTECTED] Sent:
Thursday, May 12, 2005 11:12 AMTo: 'Apache AXIS C User
List'Subject: RE: WS-Security
Hi
Samisa, Dinesh, and John,
Thanks for taking on my WS-Security question.
I've got a Linux C++ application that I'm modifying to send web
services requests to a Microsoft WS server that is implementing the Web
Services Enhancements (WSE) package that includes WS-Security. I have
no choice in the server as we are a third party developer that is
integrating our product into an existing system (and we're not a Microsoft
shop to boot -- so not taking on a MS WS client!). I've had them turn
off the security stuff on the dev system we're testing against so I can
continue my application dev/testing but the WS-Security obviously needs to
be in place for us to go to production.
This is the format of soap messages I am required to
support:
http://webservices.cox.com/CustomerProfile/GetProfileByAccountNumberAndSiteId
http://iwslib/cox.web.services.profile/ServiceCustomer.asmx
uuid:0c58b657-0242-4e43-9bf7-68904b9e6294
2005-05-11T14:41:07Z
2005-05-11T14:46:07Z
webserviceuser
aa
xmOrtuc7SgN2QoFJgBk8uw==
2005-05-11T14:41:07Z
qRU8kf9YQDtevGGRLqbJ7k5biuc=
FMEJoIBD7T0uXY3eizSz0oiwzRE=
wdST6LxVV+0XOZ7xqhVe9zIJ2G4=
2MJUGSiUzDLBFyDAH0OrJP46R6k=
cqRYyBRHatKNRvAQM01OrvBERyw=
j6AxeTlBcpfKuVJHD1TvoMuEaes=
IwEDjgV/jC/HjyXPxyzaF738eZc=
0
It sounds like you guys have done alot of good work
on this. What are the chances of getting it completed in the near
future? Other than me trying to hack something to make it work, do I
have any other options?
Thanks again,
pat
-Original Message-From: John Hawkins
[mailto:[EMAIL PROTECTED] Sent: Thursday, May 12, 2005 3:30
AMTo: Apache AXIS C User ListSubject: Re:
WS-SecuritySo, it
doesn't sound like we're that far off - if we just implement the
getSOAPBodyAsString() method then we would be able to have ws-security on
client-side (at least)?
Din%$h
<[EMAIL PROTECTED]>
12/05/2005 10:21
Please respond
to"Apache AXIS C User
List"
To
Apache AXIS C User
List
cc
Subject
Re:
WS-Security
Hi John, Let me breif what we tried to
do. When Client make a request , we get the Body from
the serializer and Encrypt it again set those encrypted Body to the
RE: WS-Security
Title: Message
Could
I use JNI and call the java classes/methods generated by wsdl2ws from my C++
application? Thoughts on this approach?
pat
-Original Message-From: Patrick
Heffernan [mailto:[EMAIL PROTECTED] Sent:
Thursday, May 12, 2005 11:12 AMTo: 'Apache AXIS C User
List'Subject: RE: WS-Security
Hi
Samisa, Dinesh, and John,
Thanks for taking on my WS-Security question.
I've
got a Linux C++ application that I'm modifying to send web services requests
to a Microsoft WS server that is implementing the Web Services Enhancements
(WSE) package that includes WS-Security. I have no choice in the server
as we are a third party developer that is integrating our product into an
existing system (and we're not a Microsoft shop to boot -- so not taking on a
MS WS client!). I've had them turn off the security stuff on the dev
system we're testing against so I can continue my application dev/testing but
the WS-Security obviously needs to be in place for us to go to
production.
This
is the format of soap messages I am required to support:
http://webservices.cox.com/CustomerProfile/GetProfileByAccountNumberAndSiteId
http://iwslib/cox.web.services.profile/ServiceCustomer.asmx
uuid:0c58b657-0242-4e43-9bf7-68904b9e6294
2005-05-11T14:41:07Z
2005-05-11T14:46:07Z
webserviceuser
aa
xmOrtuc7SgN2QoFJgBk8uw==
2005-05-11T14:41:07Z
qRU8kf9YQDtevGGRLqbJ7k5biuc=
FMEJoIBD7T0uXY3eizSz0oiwzRE=
wdST6LxVV+0XOZ7xqhVe9zIJ2G4=
2MJUGSiUzDLBFyDAH0OrJP46R6k=
cqRYyBRHatKNRvAQM01OrvBERyw=
j6AxeTlBcpfKuVJHD1TvoMuEaes=
IwEDjgV/jC/HjyXPxyzaF738eZc=
0
It sounds like you guys have done alot of good work
on this. What are the chances of getting it completed in the near
future? Other than me trying to hack something to make it work, do I
have any other options?
Thanks again,
pat
-Original Message-From: John Hawkins
[mailto:[EMAIL PROTECTED] Sent: Thursday, May 12, 2005 3:30
AMTo: Apache AXIS C User ListSubject: Re:
WS-SecuritySo, it
doesn't sound like we're that far off - if we just implement the
getSOAPBodyAsString() method then we would be able to have ws-security on
client-side (at least)?
Din%$h
<[EMAIL PROTECTED]>
12/05/2005 10:21
Please respond
to"Apache AXIS C User
List"
To
Apache AXIS C User
List
cc
Subject
Re:
WS-Security
Hi John, Let me breif what we tried to
do. When Client make a request , we get the Body from
the serializer and Encrypt it again set those encrypted Body to the message.
At the server end we got the encrypted message from the deserializer and
decrypted it. and get the original message. For the response flow also
scenario remains same. We hoped to do it using an handler.Since
there was a method called getBodyAsString(), (as I remember). We creadted
DOM tree using that body. ( If we could get Object Model that was easier).
giving soap message as a String I was able to Encrypt it and Giving
that Encrypt message I was able to got that original message
too.Since there wasn't a way to get acess to the Body(
getSoapBodyAsString () or any other method which can access body
didn't implemented at that time). We didn
RE: WS-Security
Title: Message
Hi
Samisa, Dinesh, and John,
Thanks
for taking on my WS-Security question.
I've
got a Linux C++ application that I'm modifying to send web services requests to
a Microsoft WS server that is implementing the Web Services Enhancements (WSE)
package that includes WS-Security. I have no choice in the server as we
are a third party developer that is integrating our product into an existing
system (and we're not a Microsoft shop to boot -- so not taking on a MS WS
client!). I've had them turn off the security stuff on the dev system
we're testing against so I can continue my application dev/testing but the
WS-Security obviously needs to be in place for us to go to
production.
This
is the format of soap messages I am required to support:
http://webservices.cox.com/CustomerProfile/GetProfileByAccountNumberAndSiteId
http://iwslib/cox.web.services.profile/ServiceCustomer.asmx
uuid:0c58b657-0242-4e43-9bf7-68904b9e6294
2005-05-11T14:41:07Z
2005-05-11T14:46:07Z
webserviceuser
aa
xmOrtuc7SgN2QoFJgBk8uw==
2005-05-11T14:41:07Z
qRU8kf9YQDtevGGRLqbJ7k5biuc=
FMEJoIBD7T0uXY3eizSz0oiwzRE=
wdST6LxVV+0XOZ7xqhVe9zIJ2G4=
2MJUGSiUzDLBFyDAH0OrJP46R6k=
cqRYyBRHatKNRvAQM01OrvBERyw=
j6AxeTlBcpfKuVJHD1TvoMuEaes=
IwEDjgV/jC/HjyXPxyzaF738eZc=
0
It sounds like you guys have done alot of good work on
this. What are the chances of getting it completed in the near
future? Other than me trying to hack something to make it work, do I have
any other options?
Thanks again,
pat
-Original Message-From: John Hawkins
[mailto:[EMAIL PROTECTED] Sent: Thursday, May 12, 2005 3:30
AMTo: Apache AXIS C User ListSubject: Re:
WS-SecuritySo, it
doesn't sound like we're that far off - if we just implement the
getSOAPBodyAsString() method then we would be able to have ws-security on
client-side (at least)?
Din%$h
<[EMAIL PROTECTED]>
12/05/2005 10:21
Please respond
to"Apache AXIS C User
List"
To
Apache AXIS C User
List
cc
Subject
Re:
WS-Security
Hi
John, Let me breif what we tried to do.
When Client make a request , we get the Body from the serializer and
Encrypt it again set those encrypted Body to the message. At the server end we
got the encrypted message from the deserializer and decrypted it. and get the
original message. For the response flow also scenario remains same. We hoped
to do it using an handler.Since there was a method called
getBodyAsString(), (as I remember). We creadted DOM tree using that body. ( If
we could get Object Model that was easier). giving soap message as a
String I was able to Encrypt it and Giving that Encrypt message I was able to
got that original message too.Since there wasn't a way to get
acess to the Body( getSoapBodyAsString () or any other method which can
access body didn't implemented at that time). We didn't able to integrate it
with axis using a handler.regards,DineshOn 5/12/05, John Hawkins <[EMAIL PROTECTED]> wrote:
Hi Dinesh,
Can I ask - how you wanted that
soap body? Would you need a byte stream or an object model? Was this client or server
side or both? Was it on the outgoing or incoming message or both? cheers, John.
Din%$h <[EMAIL PROTECTED]>
12/05/2005 08:07
Please respond
to"Apache AXIS C User List"
To
Apache
AXIS C User List <axis-c-user@ws.apache.org
>
cc
Re: WS-Security
So, it doesn't sound like we're that far off - if we just implement the getSOAPBodyAsString() method then we would be able to have ws-security on client-side (at least)? Din%$h <[EMAIL PROTECTED]> 12/05/2005 10:21 Please respond to "Apache AXIS C User List" To Apache AXIS C User List cc Subject Re: WS-Security Hi John, Let me breif what we tried to do. When Client make a request , we get the Body from the serializer and Encrypt it again set those encrypted Body to the message. At the server end we got the encrypted message from the deserializer and decrypted it. and get the original message. For the response flow also scenario remains same. We hoped to do it using an handler. Since there was a method called getBodyAsString(), (as I remember). We creadted DOM tree using that body. ( If we could get Object Model that was easier). giving soap message as a String I was able to Encrypt it and Giving that Encrypt message I was able to got that original message too. Since there wasn't a way to get acess to the Body( getSoapBodyAsString () or any other method which can access body didn't implemented at that time). We didn't able to integrate it with axis using a handler. regards, Dinesh On 5/12/05, John Hawkins <[EMAIL PROTECTED]> wrote: Hi Dinesh, Can I ask - how you wanted that soap body? Would you need a byte stream or an object model? Was this client or server side or both? Was it on the outgoing or incoming message or both? cheers, John. Din%$h <[EMAIL PROTECTED]> 12/05/2005 08:07 Please respond to "Apache AXIS C User List" To Apache AXIS C User List <axis-c-user@ws.apache.org > cc Subject Re: WS-Security Hi, Both Sameera and my self had worked on this (WSS4C). We needed to get body of Soap Message through a handler.( from Serilizer). But Unfortunately It was not implemented at that time.( It was commented /* To do */). There were some threads discussing about those methods. We were unable to get access to the Body of the Soap message through a handler.So we stopped at that point. ( Until those methods are implemented ) http://wiki.apache.org/ws/WSS4C I don't know whether some one is working on this Project now. thanx, Dinesh On 5/12/05, Samisa Abeysinghe <[EMAIL PROTECTED] > wrote: There were some efforts and there were some improvements proposed to the current engine to help implement WS-Security ,like opening up the SOAP body in handlers. But we did not hear from anyone on this lately. Is there anyone working on WS-Sec at the moment? Thanks, Samisa... -Original Message- From: Patrick Heffernan [mailto:[EMAIL PROTECTED] ] Sent: Thursday, May 12, 2005 12:14 PM To: axis-c-user@ws.apache.org Subject: WS-Security I apologize if I've missed this in some publication. What is the plan for Axis C++ support WS-Security? I've got a project that requires the WSE Username/Password token and I'm trying to determine what options are available to me. Thanks, pat -- W.Dinesh Premalal [EMAIL PROTECTED] http://www.cse.mrt.ac.lk/~premalwd/ -- W.Dinesh Premalal [EMAIL PROTECTED] http://www.cse.mrt.ac.lk/~premalwd/
Re: WS-Security
Hi John, Let me breif what we tried to do. When Client make a request , we get the Body from the serializer and Encrypt it again set those encrypted Body to the message. At the server end we got the encrypted message from the deserializer and decrypted it. and get the original message. For the response flow also scenario remains same. We hoped to do it using an handler. Since there was a method called getBodyAsString(), (as I remember). We creadted DOM tree using that body. ( If we could get Object Model that was easier). giving soap message as a String I was able to Encrypt it and Giving that Encrypt message I was able to got that original message too. Since there wasn't a way to get acess to the Body( getSoapBodyAsString () or any other method which can access body didn't implemented at that time). We didn't able to integrate it with axis using a handler. regards, Dinesh On 5/12/05, John Hawkins <[EMAIL PROTECTED]> wrote: Hi Dinesh, Can I ask - how you wanted that soap body? Would you need a byte stream or an object model? Was this client or server side or both? Was it on the outgoing or incoming message or both? cheers, John. Din%$h <[EMAIL PROTECTED]> 12/05/2005 08:07 Please respond to "Apache AXIS C User List" To Apache AXIS C User List <axis-c-user@ws.apache.org > cc Subject Re: WS-Security Hi, Both Sameera and my self had worked on this (WSS4C). We needed to get body of Soap Message through a handler.( from Serilizer). But Unfortunately It was not implemented at that time.( It was commented /* To do */). There were some threads discussing about those methods. We were unable to get access to the Body of the Soap message through a handler.So we stopped at that point. ( Until those methods are implemented ) http://wiki.apache.org/ws/WSS4C I don't know whether some one is working on this Project now. thanx, Dinesh On 5/12/05, Samisa Abeysinghe <[EMAIL PROTECTED] > wrote: There were some efforts and there were some improvements proposed to the current engine to help implement WS-Security ,like opening up the SOAP body in handlers. But we did not hear from anyone on this lately. Is there anyone working on WS-Sec at the moment? Thanks, Samisa... -Original Message- From: Patrick Heffernan [mailto:[EMAIL PROTECTED] ] Sent: Thursday, May 12, 2005 12:14 PM To: axis-c-user@ws.apache.org Subject: WS-Security I apologize if I've missed this in some publication. What is the plan for Axis C++ support WS-Security? I've got a project that requires the WSE Username/Password token and I'm trying to determine what options are available to me. Thanks, pat -- W.Dinesh Premalal [EMAIL PROTECTED] http://www.cse.mrt.ac.lk/~premalwd/ -- W.Dinesh Premalal[EMAIL PROTECTED]http://www.cse.mrt.ac.lk/~premalwd/
Re: WS-Security
Hi Dinesh, Can I ask - how you wanted that soap body? Would you need a byte stream or an object model? Was this client or server side or both? Was it on the outgoing or incoming message or both? cheers, John. Din%$h <[EMAIL PROTECTED]> 12/05/2005 08:07 Please respond to "Apache AXIS C User List" To Apache AXIS C User List cc Subject Re: WS-Security Hi, Both Sameera and my self had worked on this (WSS4C). We needed to get body of Soap Message through a handler.( from Serilizer). But Unfortunately It was not implemented at that time.( It was commented /* To do */). There were some threads discussing about those methods. We were unable to get access to the Body of the Soap message through a handler.So we stopped at that point. ( Until those methods are implemented ) http://wiki.apache.org/ws/WSS4C I don't know whether some one is working on this Project now. thanx, Dinesh On 5/12/05, Samisa Abeysinghe <[EMAIL PROTECTED]> wrote: There were some efforts and there were some improvements proposed to the current engine to help implement WS-Security ,like opening up the SOAP body in handlers. But we did not hear from anyone on this lately. Is there anyone working on WS-Sec at the moment? Thanks, Samisa... -Original Message- From: Patrick Heffernan [mailto:[EMAIL PROTECTED] ] Sent: Thursday, May 12, 2005 12:14 PM To: axis-c-user@ws.apache.org Subject: WS-Security I apologize if I've missed this in some publication. What is the plan for Axis C++ support WS-Security? I've got a project that requires the WSE Username/Password token and I'm trying to determine what options are available to me. Thanks, pat -- W.Dinesh Premalal [EMAIL PROTECTED] http://www.cse.mrt.ac.lk/~premalwd/
Re: WS-Security
Hi, Both Sameera and my self had worked on this (WSS4C). We needed to get body of Soap Message through a handler.( from Serilizer). But Unfortunately It was not implemented at that time.( It was commented /* To do */). There were some threads discussing about those methods. We were unable to get access to the Body of the Soap message through a handler.So we stopped at that point. ( Until those methods are implemented ) http://wiki.apache.org/ws/WSS4C I don't know whether some one is working on this Project now. thanx, DineshOn 5/12/05, Samisa Abeysinghe <[EMAIL PROTECTED]> wrote: There were some efforts and there were some improvements proposed to thecurrent engine to help implement WS-Security ,like opening up the SOAPbody in handlers. But we did not hear from anyone on this lately. Is there anyone working on WS-Sec at the moment?Thanks,Samisa...-Original Message-From: Patrick Heffernan [mailto:[EMAIL PROTECTED] ]Sent: Thursday, May 12, 2005 12:14 PMTo: axis-c-user@ws.apache.orgSubject: WS-SecurityI apologize if I've missed this in some publication. What is the plan for Axis C++ support WS-Security? I've got a project that requires theWSE Username/Password token and I'm trying to determine what options areavailable to me.Thanks, pat -- W.Dinesh Premalal[EMAIL PROTECTED]http://www.cse.mrt.ac.lk/~premalwd/
RE: WS-Security
There were some efforts and there were some improvements proposed to the current engine to help implement WS-Security ,like opening up the SOAP body in handlers. But we did not hear from anyone on this lately. Is there anyone working on WS-Sec at the moment? Thanks, Samisa... -Original Message- From: Patrick Heffernan [mailto:[EMAIL PROTECTED] Sent: Thursday, May 12, 2005 12:14 PM To: axis-c-user@ws.apache.org Subject: WS-Security I apologize if I've missed this in some publication. What is the plan for Axis C++ support WS-Security? I've got a project that requires the WSE Username/Password token and I'm trying to determine what options are available to me. Thanks, pat
WS-Security
I apologize if I've missed this in some publication. What is the plan for Axis C++ support WS-Security? I've got a project that requires the WSE Username/Password token and I'm trying to determine what options are available to me. Thanks, pat
