You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-user@axis.apache.org by Frederic Heem <fr...@telsey.it> on 2008/07/01 18:40:25 UTC
rampart and message with no parameter
Dear,
Rampart has been successfully used for messages with at least one
parameter. To be precise, sec_echo has been used with scenario3.
However, a problem arises when a message without parameter has to sent,
indeed, in this case, the body is empty and rampart refuses to send the
message because it complains that no node has to be encrypted. Does
anyone know how to tackle this problem ? One ugly hack would be to add a
fake parameter, but one has to modify the wsdl.
Frederic
______________________________________________________________________________
--- NOTICE ---
This email and any attachments are confidential and are intended for the
addressee only. If you have received this message by mistake, please contact
us immediately and then delete the message from your system. You must not
copy, distribute, disclose or act upon the contents of this email. Personal
and corporate data submitted will be used in a correct, transparent and lawful
manner. The data collected will be processed in paper or computerized form for
the performance of contractual and lawful obligations as well as for the
effective management of business relationship. The data processor is Telsey
S.p.A. The data subject may exercise all the rights set forth in art. 7 of
Law by Decree 30.06.2003 n. 196 as reported in the following url
http://www.telsey.com/privacy.asp.
______________________________________________________________________________
798t8RfNa6Dl8Ilf
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-user-help@ws.apache.org
Re: rampart and message with no parameter
Posted by Supun Kamburugamuva <su...@gmail.com>.
Hi,
If I'm right, most probably I'm. The problem is that in your policy you are
saying to encrypt the message body i.e
<sp:EncryptedParts>
<sp:Body/>
</sp:EncryptedParts>.
But you don't have a message body. So it is perfectly normal to get this
error. If this is the case please remove that part from the policy.
Supun..
On Wed, Jul 2, 2008 at 6:55 AM, Samisa Abeysinghe <sa...@wso2.com> wrote:
> Frederic Heem wrote:
>
>> Dear,
>> Rampart has been successfully used for messages with at least one
>> parameter. To be precise, sec_echo has been used with scenario3. However, a
>> problem arises when a message without parameter has to sent, indeed, in this
>> case, the body is empty and rampart refuses to send the message because it
>> complains that no node has to be encrypted. Does anyone know how to tackle
>> this problem ? One ugly hack would be to add a fake parameter, but one has
>> to modify the wsdl.
>>
>
> I think this is not a Rampart problem, rather an Axis2/C feature. If the
> payload is empty, Axis2/C thinks that there is something wrong.
> The rationale for this design was that, if there is no payload to send, why
> send an empty message.
>
> What are the semantics of you sending this message? What does that message
> do? I am trying to understand the meaning of such an empty message.
>
> Samisa...
>
> Frederic
>>
>>
>> ______________________________________________________________________________
>>
>>
>> --- NOTICE ---
>>
>> This email and any attachments are confidential and are intended for
>> the
>> addressee only. If you have received this message by mistake, please
>> contact
>> us immediately and then delete the message from your system. You must
>> not
>> copy, distribute, disclose or act upon the contents of this email.
>> Personal
>> and corporate data submitted will be used in a correct, transparent and
>> lawful
>> manner. The data collected will be processed in paper or computerized form
>> for
>> the performance of contractual and lawful obligations as well as for
>> the
>> effective management of business relationship. The data processor is
>> Telsey
>> S.p.A. The data subject may exercise all the rights set forth in art.
>> 7 of
>> Law by Decree 30.06.2003 n. 196 as reported in the following
>> url
>> http://www.telsey.com/privacy.asp.
>>
>> ______________________________________________________________________________
>>
>> 798t8RfNa6Dl8Ilf
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-c-user-help@ws.apache.org
>> ------------------------------------------------------------------------
>>
>>
>> No virus found in this incoming message.
>> Checked by AVG. Version: 8.0.101 / Virus Database: 270.4.3/1528 - Release
>> Date: 7/1/2008 7:26 AM
>>
>>
>
>
> --
> Samisa Abeysinghe Director, Engineering; WSO2 Inc.
>
> http://www.wso2.com/ - "The Open Source SOA Company"
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-user-help@ws.apache.org
>
>
Re: rampart and message with no parameter
Posted by Manjula Peiris <ma...@wso2.com>.
On Wed, 2008-07-02 at 18:52 +0530, Manjula Peiris wrote:
> There can be messages with empty bodies. For example WS-Reliable
> messaging sends such messages. I think this is a bug in Rampart/C.
> Because what following assertion says is encrypt the first child of body
> if it is there.
> <sp:EncryptedParts>
> <sp:Body/>
> </sp:EncryptedParts>
>
> So if the body is not there it should not return an error.
Rather if it is an empty body it should not return an error from
Rampart/C.
>
>
> On Wed, 2008-07-02 at 09:28 +0100, Frederic Heem wrote:
> > Samisa Abeysinghe wrote:
> > > Frederic Heem wrote:
> > >> Dear,
> > >> Rampart has been successfully used for messages with at least one
> > >> parameter. To be precise, sec_echo has been used with scenario3.
> > >> However, a problem arises when a message without parameter has to
> > >> sent, indeed, in this case, the body is empty and rampart refuses to
> > >> send the message because it complains that no node has to be
> > >> encrypted. Does anyone know how to tackle this problem ? One ugly
> > >> hack would be to add a fake parameter, but one has to modify the wsdl.
> > >
> > > I think this is not a Rampart problem, rather an Axis2/C feature. If
> > > the payload is empty, Axis2/C thinks that there is something wrong.
> > > The rationale for this design was that, if there is no payload to
> > > send, why send an empty message.
> > >
> > > What are the semantics of you sending this message? What does that
> > > message do? I am trying to understand the meaning of such an empty
> > > message.
> > >
> > The web service being developed has many messages, some of them doesn't
> > have any parameters, e.g GetDeviceList() . In this case, the body is
> > empty but the header is not empty and contains the action which is used
> > by the server to dispatch this message. Therefore, it makes sense to
> > send a message with an empty body. Without using rampart, axis2c doesn't
> > complain about the empty body and send the message which is interpreted
> > by the server correctly.
> > Regards,
> > > Samisa...
> > >
> > >> Frederic
> > >>
> > >>
> > >> ______________________________________________________________________________
> > >>
> > >>
> > >> --- NOTICE ---
> > >>
> > >> This email and any attachments are confidential and are
> > >> intended for the
> > >> addressee only. If you have received this message by mistake,
> > >> please contact
> > >> us immediately and then delete the message from your system. You
> > >> must not
> > >> copy, distribute, disclose or act upon the contents of this email.
> > >> Personal
> > >> and corporate data submitted will be used in a correct, transparent
> > >> and lawful
> > >> manner. The data collected will be processed in paper or computerized
> > >> form for
> > >> the performance of contractual and lawful obligations as well
> > >> as for the
> > >> effective management of business relationship. The data processor
> > >> is Telsey
> > >> S.p.A. The data subject may exercise all the rights set forth in
> > >> art. 7 of
> > >> Law by Decree 30.06.2003 n. 196 as reported in the
> > >> following url
> > >> http://www.telsey.com/privacy.asp.
> > >>
> > >> ______________________________________________________________________________
> > >>
> > >> 798t8RfNa6Dl8Ilf
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
> > >> For additional commands, e-mail: axis-c-user-help@ws.apache.org
> > >> ------------------------------------------------------------------------
> > >>
> > >>
> > >> No virus found in this incoming message.
> > >> Checked by AVG. Version: 8.0.101 / Virus Database: 270.4.3/1528 -
> > >> Release Date: 7/1/2008 7:26 AM
> > >>
> > >
> > >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-user-help@ws.apache.org
Re: rampart and message with no parameter
Posted by Manjula Peiris <ma...@wso2.com>.
There can be messages with empty bodies. For example WS-Reliable
messaging sends such messages. I think this is a bug in Rampart/C.
Because what following assertion says is encrypt the first child of body
if it is there.
<sp:EncryptedParts>
<sp:Body/>
</sp:EncryptedParts>
So if the body is not there it should not return an error.
On Wed, 2008-07-02 at 09:28 +0100, Frederic Heem wrote:
> Samisa Abeysinghe wrote:
> > Frederic Heem wrote:
> >> Dear,
> >> Rampart has been successfully used for messages with at least one
> >> parameter. To be precise, sec_echo has been used with scenario3.
> >> However, a problem arises when a message without parameter has to
> >> sent, indeed, in this case, the body is empty and rampart refuses to
> >> send the message because it complains that no node has to be
> >> encrypted. Does anyone know how to tackle this problem ? One ugly
> >> hack would be to add a fake parameter, but one has to modify the wsdl.
> >
> > I think this is not a Rampart problem, rather an Axis2/C feature. If
> > the payload is empty, Axis2/C thinks that there is something wrong.
> > The rationale for this design was that, if there is no payload to
> > send, why send an empty message.
> >
> > What are the semantics of you sending this message? What does that
> > message do? I am trying to understand the meaning of such an empty
> > message.
> >
> The web service being developed has many messages, some of them doesn't
> have any parameters, e.g GetDeviceList() . In this case, the body is
> empty but the header is not empty and contains the action which is used
> by the server to dispatch this message. Therefore, it makes sense to
> send a message with an empty body. Without using rampart, axis2c doesn't
> complain about the empty body and send the message which is interpreted
> by the server correctly.
> Regards,
> > Samisa...
> >
> >> Frederic
> >>
> >>
> >> ______________________________________________________________________________
> >>
> >>
> >> --- NOTICE ---
> >>
> >> This email and any attachments are confidential and are
> >> intended for the
> >> addressee only. If you have received this message by mistake,
> >> please contact
> >> us immediately and then delete the message from your system. You
> >> must not
> >> copy, distribute, disclose or act upon the contents of this email.
> >> Personal
> >> and corporate data submitted will be used in a correct, transparent
> >> and lawful
> >> manner. The data collected will be processed in paper or computerized
> >> form for
> >> the performance of contractual and lawful obligations as well
> >> as for the
> >> effective management of business relationship. The data processor
> >> is Telsey
> >> S.p.A. The data subject may exercise all the rights set forth in
> >> art. 7 of
> >> Law by Decree 30.06.2003 n. 196 as reported in the
> >> following url
> >> http://www.telsey.com/privacy.asp.
> >>
> >> ______________________________________________________________________________
> >>
> >> 798t8RfNa6Dl8Ilf
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: axis-c-user-help@ws.apache.org
> >> ------------------------------------------------------------------------
> >>
> >>
> >> No virus found in this incoming message.
> >> Checked by AVG. Version: 8.0.101 / Virus Database: 270.4.3/1528 -
> >> Release Date: 7/1/2008 7:26 AM
> >>
> >
> >
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-user-help@ws.apache.org
Re: rampart and message with no parameter
Posted by Supun Kamburugamuva <su...@gmail.com>.
>
>> The web service being developed has many messages, some of them doesn't
> have any parameters, e.g GetDeviceList() . In this case, the body is empty
> but the header is not empty and contains the action which is used by the
> server to dispatch this message. Therefore, it makes sense to send a message
> with an empty body. Without using rampart, axis2c doesn't complain about the
> empty body and send the message which is interpreted by the server
> correctly.
> Regards,
>
If you have many operations and some of them have empty bodies I suggest you
use operation level policies.
Supun..
>
> Samisa...
>>
>> Frederic
>>>
>>>
>>> ______________________________________________________________________________
>>>
>>>
>>> --- NOTICE ---
>>>
>>> This email and any attachments are confidential and are intended
>>> for the
>>> addressee only. If you have received this message by mistake, please
>>> contact
>>> us immediately and then delete the message from your system. You
>>> must not
>>> copy, distribute, disclose or act upon the contents of this email.
>>> Personal
>>> and corporate data submitted will be used in a correct, transparent and
>>> lawful
>>> manner. The data collected will be processed in paper or computerized
>>> form for
>>> the performance of contractual and lawful obligations as well as
>>> for the
>>> effective management of business relationship. The data processor is
>>> Telsey
>>> S.p.A. The data subject may exercise all the rights set forth in art.
>>> 7 of
>>> Law by Decree 30.06.2003 n. 196 as reported in the following
>>> url
>>> http://www.telsey.com/privacy.asp.
>>>
>>> ______________________________________________________________________________
>>>
>>> 798t8RfNa6Dl8Ilf
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: axis-c-user-help@ws.apache.org
>>> ------------------------------------------------------------------------
>>>
>>>
>>> No virus found in this incoming message.
>>> Checked by AVG. Version: 8.0.101 / Virus Database: 270.4.3/1528 - Release
>>> Date: 7/1/2008 7:26 AM
>>>
>>>
>>
>>
>>
>
> --
> ---
>
> Frederic Heem - Innovation Hub Senior Engineer
> Telsey Telecommunications S.p.A.
> email: frederic.heem@telsey.it
> Departement: Innovation Hub
> UK: Vanguard Centre, ATU II, Unit 8 Sir William Lyons Road University of
> Warwick Science Park CV4 7EZ Coventry
> Tel. direct phone (+39) 0422 377760
> Central Bureau Viale dell'Industria, 1
> 31055 Quinto di Treviso (TV) - Italy
> Tel.: +39 0422470840 Fax: +39 0422470920
> Web: www.telsey.com
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-user-help@ws.apache.org
>
>
Re: rampart and message with no parameter
Posted by Frederic Heem <fr...@telsey.it>.
Samisa Abeysinghe wrote:
> Frederic Heem wrote:
>> Dear,
>> Rampart has been successfully used for messages with at least one
>> parameter. To be precise, sec_echo has been used with scenario3.
>> However, a problem arises when a message without parameter has to
>> sent, indeed, in this case, the body is empty and rampart refuses to
>> send the message because it complains that no node has to be
>> encrypted. Does anyone know how to tackle this problem ? One ugly
>> hack would be to add a fake parameter, but one has to modify the wsdl.
>
> I think this is not a Rampart problem, rather an Axis2/C feature. If
> the payload is empty, Axis2/C thinks that there is something wrong.
> The rationale for this design was that, if there is no payload to
> send, why send an empty message.
>
> What are the semantics of you sending this message? What does that
> message do? I am trying to understand the meaning of such an empty
> message.
>
The web service being developed has many messages, some of them doesn't
have any parameters, e.g GetDeviceList() . In this case, the body is
empty but the header is not empty and contains the action which is used
by the server to dispatch this message. Therefore, it makes sense to
send a message with an empty body. Without using rampart, axis2c doesn't
complain about the empty body and send the message which is interpreted
by the server correctly.
Regards,
> Samisa...
>
>> Frederic
>>
>>
>> ______________________________________________________________________________
>>
>>
>> --- NOTICE ---
>>
>> This email and any attachments are confidential and are
>> intended for the
>> addressee only. If you have received this message by mistake,
>> please contact
>> us immediately and then delete the message from your system. You
>> must not
>> copy, distribute, disclose or act upon the contents of this email.
>> Personal
>> and corporate data submitted will be used in a correct, transparent
>> and lawful
>> manner. The data collected will be processed in paper or computerized
>> form for
>> the performance of contractual and lawful obligations as well
>> as for the
>> effective management of business relationship. The data processor
>> is Telsey
>> S.p.A. The data subject may exercise all the rights set forth in
>> art. 7 of
>> Law by Decree 30.06.2003 n. 196 as reported in the
>> following url
>> http://www.telsey.com/privacy.asp.
>>
>> ______________________________________________________________________________
>>
>> 798t8RfNa6Dl8Ilf
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-c-user-help@ws.apache.org
>> ------------------------------------------------------------------------
>>
>>
>> No virus found in this incoming message.
>> Checked by AVG. Version: 8.0.101 / Virus Database: 270.4.3/1528 -
>> Release Date: 7/1/2008 7:26 AM
>>
>
>
--
---
Frederic Heem - Innovation Hub Senior Engineer
Telsey Telecommunications S.p.A.
email: frederic.heem@telsey.it
Departement: Innovation Hub
UK: Vanguard Centre, ATU II, Unit 8 Sir William Lyons Road University of Warwick Science Park CV4 7EZ Coventry
Tel. direct phone (+39) 0422 377760
Central Bureau Viale dell'Industria, 1
31055 Quinto di Treviso (TV) - Italy
Tel.: +39 0422470840 Fax: +39 0422470920
Web: www.telsey.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-user-help@ws.apache.org
Re: rampart and message with no parameter
Posted by Samisa Abeysinghe <sa...@wso2.com>.
Frederic Heem wrote:
> Dear,
> Rampart has been successfully used for messages with at least one
> parameter. To be precise, sec_echo has been used with scenario3.
> However, a problem arises when a message without parameter has to
> sent, indeed, in this case, the body is empty and rampart refuses to
> send the message because it complains that no node has to be
> encrypted. Does anyone know how to tackle this problem ? One ugly hack
> would be to add a fake parameter, but one has to modify the wsdl.
I think this is not a Rampart problem, rather an Axis2/C feature. If the
payload is empty, Axis2/C thinks that there is something wrong.
The rationale for this design was that, if there is no payload to send,
why send an empty message.
What are the semantics of you sending this message? What does that
message do? I am trying to understand the meaning of such an empty message.
Samisa...
> Frederic
>
>
> ______________________________________________________________________________
>
>
> --- NOTICE ---
>
> This email and any attachments are confidential and are intended
> for the
> addressee only. If you have received this message by mistake, please
> contact
> us immediately and then delete the message from your system. You
> must not
> copy, distribute, disclose or act upon the contents of this email.
> Personal
> and corporate data submitted will be used in a correct, transparent
> and lawful
> manner. The data collected will be processed in paper or computerized
> form for
> the performance of contractual and lawful obligations as well as
> for the
> effective management of business relationship. The data processor
> is Telsey
> S.p.A. The data subject may exercise all the rights set forth in
> art. 7 of
> Law by Decree 30.06.2003 n. 196 as reported in the
> following url
> http://www.telsey.com/privacy.asp.
>
> ______________________________________________________________________________
>
> 798t8RfNa6Dl8Ilf
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-user-help@ws.apache.org
> ------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG.
> Version: 8.0.101 / Virus Database: 270.4.3/1528 - Release Date: 7/1/2008 7:26 AM
>
--
Samisa Abeysinghe
Director, Engineering; WSO2 Inc.
http://www.wso2.com/ - "The Open Source SOA Company"
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-user-help@ws.apache.org