You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by Vivian Wang <vi...@yahoo.com> on 2008/11/05 06:24:25 UTC

What are the configurable ws-security parameters for incoming message

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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org


Re: What are the configurable ws-security parameters for incoming message

Posted by Manjula Peiris <ma...@wso2.com>.
On Wed, 2008-11-05 at 10:30 -0800, Vivian Wang wrote:
> Thanks! 
> 
> But my question is really this: In WS-Policy, what parameters need to be or can be configured for incoming message (the response message from a client point of view)? I don't see much document in rampart/c site. From a user point of view, I would like to see something like soapUI in which the configurable parameters for WS-security are very clear. Is there anything like that in rampart/c in a configuration file?
> 

https://wso2.org/library/2702


> 
> Thanks again!
> Vivian
> 
> 
> --- On Tue, 11/4/08, Samisa Abeysinghe <sa...@wso2.com> wrote:
> 
> > From: Samisa Abeysinghe <sa...@wso2.com>
> > Subject: Re: What are the configurable ws-security parameters for incoming message
> > To: "Apache AXIS C Developers List" <ax...@ws.apache.org>
> > Cc: axis-c-user@ws.apache.org, rampart-c-dev@ws.apache.org
> > Date: Tuesday, November 4, 2008, 10:59 PM
> > 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:
> > axis-c-dev-unsubscribe@ws.apache.org
> > > For additional commands, e-mail:
> > axis-c-dev-help@ws.apache.org
> > >   
> > >
> > ------------------------------------------------------------------------
> > >
> > >
> > > 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:
> > axis-c-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail:
> > axis-c-dev-help@ws.apache.org
> 
> 
>       
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
> 


Re: What are the configurable ws-security parameters for incoming message

Posted by Manjula Peiris <ma...@wso2.com>.
On Wed, 2008-11-05 at 10:30 -0800, Vivian Wang wrote:
> Thanks! 
> 
> But my question is really this: In WS-Policy, what parameters need to be or can be configured for incoming message (the response message from a client point of view)? I don't see much document in rampart/c site. From a user point of view, I would like to see something like soapUI in which the configurable parameters for WS-security are very clear. Is there anything like that in rampart/c in a configuration file?
> 

https://wso2.org/library/2702


> 
> Thanks again!
> Vivian
> 
> 
> --- On Tue, 11/4/08, Samisa Abeysinghe <sa...@wso2.com> wrote:
> 
> > From: Samisa Abeysinghe <sa...@wso2.com>
> > Subject: Re: What are the configurable ws-security parameters for incoming message
> > To: "Apache AXIS C Developers List" <ax...@ws.apache.org>
> > Cc: axis-c-user@ws.apache.org, rampart-c-dev@ws.apache.org
> > Date: Tuesday, November 4, 2008, 10:59 PM
> > 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:
> > axis-c-dev-unsubscribe@ws.apache.org
> > > For additional commands, e-mail:
> > axis-c-dev-help@ws.apache.org
> > >   
> > >
> > ------------------------------------------------------------------------
> > >
> > >
> > > 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:
> > axis-c-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail:
> > axis-c-dev-help@ws.apache.org
> 
> 
>       
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org


Re: What are the configurable ws-security parameters for incoming message

Posted by Samisa Abeysinghe <sa...@wso2.com>.
Vivian Wang wrote:
> Thanks! 
>
> But my question is really this: In WS-Policy, what parameters need to be or can be configured for incoming message (the response message from a client point of view)? I don't see much document in rampart/c site. From a user point of view, I would like to see something like soapUI in which the configurable parameters for WS-security are very clear. Is there anything like that in rampart/c in a configuration file?
>   
Nop, you do not have anything like that in Rampart/C config file. In 
fact, the policy tells it all, as I mentioned earlier. The kind and 
format of policies are in sync with WS-SecPolicy spec.Using policy, in 
place of rampart specific confing ensures interoperability.

Thanks,
Samisa...

>
> Thanks again!
> Vivian
>
>
> --- On Tue, 11/4/08, Samisa Abeysinghe <sa...@wso2.com> wrote:
>
>   
>> From: Samisa Abeysinghe <sa...@wso2.com>
>> Subject: Re: What are the configurable ws-security parameters for incoming message
>> To: "Apache AXIS C Developers List" <ax...@ws.apache.org>
>> Cc: axis-c-user@ws.apache.org, rampart-c-dev@ws.apache.org
>> Date: Tuesday, November 4, 2008, 10:59 PM
>> 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:
>>>       
>> axis-c-dev-unsubscribe@ws.apache.org
>>     
>>> For additional commands, e-mail:
>>>       
>> axis-c-dev-help@ws.apache.org
>>     
>>>   
>>>
>>>       
>> ------------------------------------------------------------------------
>>     
>>> 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:
>> axis-c-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail:
>> axis-c-dev-help@ws.apache.org
>>     
>
>
>       
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
>   
> ------------------------------------------------------------------------
>
>
> 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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org


Re: What are the configurable ws-security parameters for incoming message

Posted by Vivian Wang <vi...@yahoo.com>.
Thanks! 

But my question is really this: In WS-Policy, what parameters need to be or can be configured for incoming message (the response message from a client point of view)? I don't see much document in rampart/c site. From a user point of view, I would like to see something like soapUI in which the configurable parameters for WS-security are very clear. Is there anything like that in rampart/c in a configuration file?


Thanks again!
Vivian


--- On Tue, 11/4/08, Samisa Abeysinghe <sa...@wso2.com> wrote:

> From: Samisa Abeysinghe <sa...@wso2.com>
> Subject: Re: What are the configurable ws-security parameters for incoming message
> To: "Apache AXIS C Developers List" <ax...@ws.apache.org>
> Cc: axis-c-user@ws.apache.org, rampart-c-dev@ws.apache.org
> Date: Tuesday, November 4, 2008, 10:59 PM
> 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:
> axis-c-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail:
> axis-c-dev-help@ws.apache.org
> >   
> >
> ------------------------------------------------------------------------
> >
> >
> > 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:
> axis-c-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail:
> axis-c-dev-help@ws.apache.org


      

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org


Re: What are the configurable ws-security parameters for incoming message

Posted by Samisa Abeysinghe <sa...@wso2.com>.
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: axis-c-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
>   
> ------------------------------------------------------------------------
>
>
> 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: axis-c-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-user-help@ws.apache.org


Re: What are the configurable ws-security parameters for incoming message

Posted by Samisa Abeysinghe <sa...@wso2.com>.
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: axis-c-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
>   
> ------------------------------------------------------------------------
>
>
> 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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org