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 Raymond Zhou <ra...@yahoo.com> on 2008/10/23 02:31:54 UTC
APIs for ws-security paramenters
Hi there,
�
I am planning to use rampart-c as a module in my axis2/c to support ws-security in a web service client application. I know I can configure the policy files in the client repository. My question is that if all these variables/parameters can be set programmably using some sort of APIs. I�want�to do this because I would like to save the parameters in a database tables instead of a local file and�I also want to be able to develop a UI for users to easily set/edit/change the values.
�
Thanks!
Raymond
Re: APIs for ws-security paramenters
Posted by Uthaiyashankar <sh...@wso2.com>.
Hi Raymond,
Raymond Zhou wrote:
> Hi, Uthaiyashankar,
>
> I might actually be able to do the patch (providing APIs). But before I go
> to talk to my boss, could you give me some estimates of the scope.
> I did not dig deep into the code, but I imagine it shouldn't be that
> complicated. I can pass the parameters from axis2/c just like
> rampart/c is currently doing for username/password, right?
>
Yes, you are correct. It is not a complicated stuff. I think you can do
it in one or two days.
>
> Another question: How do I test my web service client to make sure
> ws-security works? I need a web service server that support ws-security,
> right? How can I set up and find such a server? Any help is really
> appreciated.
>
You can use policies inside sample 5 and set up the server to test the
functionality.
Regards,
Shankar.
> Thanks a bunch!
> Frank
>
> --- On Thu, 10/23/08, Uthaiyashankar <sh...@wso2.com> wrote:
>
> From: Uthaiyashankar <sh...@wso2.com>
> Subject: Re: APIs for ws-security paramenters
> To: rampart-c-dev@ws.apache.org
> Cc: "Apache AXIS C Developers List" <ax...@ws.apache.org>
> Date: Thursday, October 23, 2008, 5:21 AM
>
> Hi Raymond,
>
> No plans as of now. Will be adding the APIs when time permits.. Do you
> need it urgently? Infact, it would be great if you can provide a patch :)
>
> Regards,
> Shankar
>
> Raymond Zhou wrote:
>
>> Hi, Uthaiyashankar,
>>
>> Thanks much for the info. I am a bit surprised that we can only set the
>>
> few parameters programmably. I don't think it's ideal for client users
> to set up so many parameters in a complicated xml file in a file system. For my
> self, I would certainly like to provide a UI for client users to configure all
> the different parameters, just like what soapUI does. but without the rampart
> APIs, I would not be able to do that. Any plans that you will be able to provide
> the APIs?
>
>>
>> Thanks again!
>> Raymond
>>
>> --- On Thu, 10/23/08, Uthaiyashankar <sh...@wso2.com> wrote:
>>
>> From: Uthaiyashankar <sh...@wso2.com>
>> Subject: Re: APIs for ws-security paramenters
>> To: "Apache AXIS C Developers List"
>>
> <ax...@ws.apache.org>
>
>> Cc: axis-c-users@ws.apache.org, rampart-c-dev@ws.apache.org
>> Date: Thursday, October 23, 2008, 3:31 AM
>>
>> Hi Raymond,
>>
>> For client side, you can set username, password, password type and time
>> to live parameters programatically. However, other options (like
>> certificate, key, etc.) have to be set using policy files. We have to
>> implement missing options. You can find more details from [1]
>>
>> Regards,
>> Shankar
>>
>> [1] https://issues.apache.org/jira/browse/RAMPARTC-56
>>
>>
>> Raymond Zhou wrote:
>>
>>
>>> Hi there,
>>>
>>> I am planning to use rampart-c as a module in my axis2/c to support
>>> ws-security in a web service client application. I know I can
>>> configure the policy files in the client repository. My question is
>>> that if all these variables/parameters can be set programmably using
>>> some sort of APIs. I want to do this because I would like to save the
>>> parameters in a database tables instead of a local file and I also
>>> want to be able to develop a UI for users to easily set/edit/change
>>> the values.
>>>
>>> Thanks!
>>> Raymond
>>>
>>>
>>>
>>>
>>
>>
>
>
>
--
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"
Re: APIs for ws-security paramenters
Posted by Uthaiyashankar <sh...@wso2.com>.
Hi Raymond,
Raymond Zhou wrote:
> Hi, Uthaiyashankar,
>
> I might actually be able to do the patch (providing APIs). But before I go
> to talk to my boss, could you give me some estimates of the scope.
> I did not dig deep into the code, but I imagine it shouldn't be that
> complicated. I can pass the parameters from axis2/c just like
> rampart/c is currently doing for username/password, right?
>
Yes, you are correct. It is not a complicated stuff. I think you can do
it in one or two days.
>
> Another question: How do I test my web service client to make sure
> ws-security works? I need a web service server that support ws-security,
> right? How can I set up and find such a server? Any help is really
> appreciated.
>
You can use policies inside sample 5 and set up the server to test the
functionality.
Regards,
Shankar.
> Thanks a bunch!
> Frank
>
> --- On Thu, 10/23/08, Uthaiyashankar <sh...@wso2.com> wrote:
>
> From: Uthaiyashankar <sh...@wso2.com>
> Subject: Re: APIs for ws-security paramenters
> To: rampart-c-dev@ws.apache.org
> Cc: "Apache AXIS C Developers List" <ax...@ws.apache.org>
> Date: Thursday, October 23, 2008, 5:21 AM
>
> Hi Raymond,
>
> No plans as of now. Will be adding the APIs when time permits.. Do you
> need it urgently? Infact, it would be great if you can provide a patch :)
>
> Regards,
> Shankar
>
> Raymond Zhou wrote:
>
>> Hi, Uthaiyashankar,
>>
>> Thanks much for the info. I am a bit surprised that we can only set the
>>
> few parameters programmably. I don't think it's ideal for client users
> to set up so many parameters in a complicated xml file in a file system. For my
> self, I would certainly like to provide a UI for client users to configure all
> the different parameters, just like what soapUI does. but without the rampart
> APIs, I would not be able to do that. Any plans that you will be able to provide
> the APIs?
>
>>
>> Thanks again!
>> Raymond
>>
>> --- On Thu, 10/23/08, Uthaiyashankar <sh...@wso2.com> wrote:
>>
>> From: Uthaiyashankar <sh...@wso2.com>
>> Subject: Re: APIs for ws-security paramenters
>> To: "Apache AXIS C Developers List"
>>
> <ax...@ws.apache.org>
>
>> Cc: axis-c-users@ws.apache.org, rampart-c-dev@ws.apache.org
>> Date: Thursday, October 23, 2008, 3:31 AM
>>
>> Hi Raymond,
>>
>> For client side, you can set username, password, password type and time
>> to live parameters programatically. However, other options (like
>> certificate, key, etc.) have to be set using policy files. We have to
>> implement missing options. You can find more details from [1]
>>
>> Regards,
>> Shankar
>>
>> [1] https://issues.apache.org/jira/browse/RAMPARTC-56
>>
>>
>> Raymond Zhou wrote:
>>
>>
>>> Hi there,
>>>
>>> I am planning to use rampart-c as a module in my axis2/c to support
>>> ws-security in a web service client application. I know I can
>>> configure the policy files in the client repository. My question is
>>> that if all these variables/parameters can be set programmably using
>>> some sort of APIs. I want to do this because I would like to save the
>>> parameters in a database tables instead of a local file and I also
>>> want to be able to develop a UI for users to easily set/edit/change
>>> the values.
>>>
>>> Thanks!
>>> Raymond
>>>
>>>
>>>
>>>
>>
>>
>
>
>
--
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://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: APIs for ws-security paramenters
Posted by Raymond Zhou <ra...@yahoo.com>.
Hi, Uthaiyashankar,
�
I�might actually be able to do the patch (providing APIs). But before I go
to talk to my boss, �could you give me some estimates of the scope.
I did not dig deep into the code, but I imagine it shouldn't be that
complicated. I can pass the parameters from axis2/c just like
rampart/c is currently doing�for username/password, right?
�
Another question: How do I test my web service client to make sure
ws-security works? I need a web service server that support ws-security,
right? How can I set up and find such a server? Any help is really
appreciated.
Thanks a bunch!
Frank
--- On Thu, 10/23/08, Uthaiyashankar <sh...@wso2.com> wrote:
From: Uthaiyashankar <sh...@wso2.com>
Subject: Re: APIs for ws-security paramenters
To: rampart-c-dev@ws.apache.org
Cc: "Apache AXIS C Developers List" <ax...@ws.apache.org>
Date: Thursday, October 23, 2008, 5:21 AM
Hi Raymond,
No plans as of now. Will be adding the APIs when time permits.. Do you
need it urgently? Infact, it would be great if you can provide a patch :)
Regards,
Shankar
Raymond Zhou wrote:
> Hi, Uthaiyashankar,
>
> Thanks much for the info. I am a bit surprised that we can only set the
few parameters programmably. I don't think it's ideal for client users
to set up so many parameters in a complicated xml file in a file system. For my
self, I would certainly like to provide a UI for client users to configure all
the different parameters, just like what soapUI does. but without the rampart
APIs, I would not be able to do that. Any plans that you will be able to provide
the APIs?
>
> Thanks again!
> Raymond
>
> --- On Thu, 10/23/08, Uthaiyashankar <sh...@wso2.com> wrote:
>
> From: Uthaiyashankar <sh...@wso2.com>
> Subject: Re: APIs for ws-security paramenters
> To: "Apache AXIS C Developers List"
<ax...@ws.apache.org>
> Cc: axis-c-users@ws.apache.org, rampart-c-dev@ws.apache.org
> Date: Thursday, October 23, 2008, 3:31 AM
>
> Hi Raymond,
>
> For client side, you can set username, password, password type and time
> to live parameters programatically. However, other options (like
> certificate, key, etc.) have to be set using policy files. We have to
> implement missing options. You can find more details from [1]
>
> Regards,
> Shankar
>
> [1] https://issues.apache.org/jira/browse/RAMPARTC-56
>
>
> Raymond Zhou wrote:
>
>> Hi there,
>>
>> I am planning to use rampart-c as a module in my axis2/c to support
>> ws-security in a web service client application. I know I can
>> configure the policy files in the client repository. My question is
>> that if all these variables/parameters can be set programmably using
>> some sort of APIs. I want to do this because I would like to save the
>> parameters in a database tables instead of a local file and I also
>> want to be able to develop a UI for users to easily set/edit/change
>> the values.
>>
>> Thanks!
>> Raymond
>>
>>
>>
>
>
>
--
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"
Re: APIs for ws-security paramenters
Posted by Raymond Zhou <ra...@yahoo.com>.
Hi, Uthaiyashankar,
I might actually be able to do the patch (providing APIs). But before I go
to talk to my boss, could you give me some estimates of the scope.
I did not dig deep into the code, but I imagine it shouldn't be that
complicated. I can pass the parameters from axis2/c just like
rampart/c is currently doing for username/password, right?
Another question: How do I test my web service client to make sure
ws-security works? I need a web service server that support ws-security,
right? How can I set up and find such a server? Any help is really
appreciated.
Thanks a bunch!
Frank
--- On Thu, 10/23/08, Uthaiyashankar <sh...@wso2.com> wrote:
From: Uthaiyashankar <sh...@wso2.com>
Subject: Re: APIs for ws-security paramenters
To: rampart-c-dev@ws.apache.org
Cc: "Apache AXIS C Developers List" <ax...@ws.apache.org>
Date: Thursday, October 23, 2008, 5:21 AM
Hi Raymond,
No plans as of now. Will be adding the APIs when time permits.. Do you
need it urgently? Infact, it would be great if you can provide a patch :)
Regards,
Shankar
Raymond Zhou wrote:
> Hi, Uthaiyashankar,
>
> Thanks much for the info. I am a bit surprised that we can only set the
few parameters programmably. I don't think it's ideal for client users
to set up so many parameters in a complicated xml file in a file system. For my
self, I would certainly like to provide a UI for client users to configure all
the different parameters, just like what soapUI does. but without the rampart
APIs, I would not be able to do that. Any plans that you will be able to provide
the APIs?
>
> Thanks again!
> Raymond
>
> --- On Thu, 10/23/08, Uthaiyashankar <sh...@wso2.com> wrote:
>
> From: Uthaiyashankar <sh...@wso2.com>
> Subject: Re: APIs for ws-security paramenters
> To: "Apache AXIS C Developers List"
<ax...@ws.apache.org>
> Cc: axis-c-users@ws.apache.org, rampart-c-dev@ws.apache.org
> Date: Thursday, October 23, 2008, 3:31 AM
>
> Hi Raymond,
>
> For client side, you can set username, password, password type and time
> to live parameters programatically. However, other options (like
> certificate, key, etc.) have to be set using policy files. We have to
> implement missing options. You can find more details from [1]
>
> Regards,
> Shankar
>
> [1] https://issues.apache.org/jira/browse/RAMPARTC-56
>
>
> Raymond Zhou wrote:
>
>> Hi there,
>>
>> I am planning to use rampart-c as a module in my axis2/c to support
>> ws-security in a web service client application. I know I can
>> configure the policy files in the client repository. My question is
>> that if all these variables/parameters can be set programmably using
>> some sort of APIs. I want to do this because I would like to save the
>> parameters in a database tables instead of a local file and I also
>> want to be able to develop a UI for users to easily set/edit/change
>> the values.
>>
>> Thanks!
>> Raymond
>>
>>
>>
>
>
>
--
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"
Re: APIs for ws-security paramenters
Posted by Uthaiyashankar <sh...@wso2.com>.
Hi Raymond,
No plans as of now. Will be adding the APIs when time permits.. Do you
need it urgently? Infact, it would be great if you can provide a patch :)
Regards,
Shankar
Raymond Zhou wrote:
> Hi, Uthaiyashankar,
>
> Thanks much for the info. I am a bit surprised that we can only set the few parameters programmably. I don't think it's ideal for client users to set up so many parameters in a complicated xml file in a file system. For my self, I would certainly like to provide a UI for client users to configure all the different parameters, just like what soapUI does. but without the rampart APIs, I would not be able to do that. Any plans that you will be able to provide the APIs?
>
> Thanks again!
> Raymond
>
> --- On Thu, 10/23/08, Uthaiyashankar <sh...@wso2.com> wrote:
>
> From: Uthaiyashankar <sh...@wso2.com>
> Subject: Re: APIs for ws-security paramenters
> To: "Apache AXIS C Developers List" <ax...@ws.apache.org>
> Cc: axis-c-users@ws.apache.org, rampart-c-dev@ws.apache.org
> Date: Thursday, October 23, 2008, 3:31 AM
>
> Hi Raymond,
>
> For client side, you can set username, password, password type and time
> to live parameters programatically. However, other options (like
> certificate, key, etc.) have to be set using policy files. We have to
> implement missing options. You can find more details from [1]
>
> Regards,
> Shankar
>
> [1] https://issues.apache.org/jira/browse/RAMPARTC-56
>
>
> Raymond Zhou wrote:
>
>> Hi there,
>>
>> I am planning to use rampart-c as a module in my axis2/c to support
>> ws-security in a web service client application. I know I can
>> configure the policy files in the client repository. My question is
>> that if all these variables/parameters can be set programmably using
>> some sort of APIs. I want to do this because I would like to save the
>> parameters in a database tables instead of a local file and I also
>> want to be able to develop a UI for users to easily set/edit/change
>> the values.
>>
>> Thanks!
>> Raymond
>>
>>
>>
>
>
>
--
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://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: APIs for ws-security paramenters
Posted by Uthaiyashankar <sh...@wso2.com>.
Hi Raymond,
No plans as of now. Will be adding the APIs when time permits.. Do you
need it urgently? Infact, it would be great if you can provide a patch :)
Regards,
Shankar
Raymond Zhou wrote:
> Hi, Uthaiyashankar,
>
> Thanks much for the info. I am a bit surprised that we can only set the few parameters programmably. I don't think it's ideal for client users to set up so many parameters in a complicated xml file in a file system. For my self, I would certainly like to provide a UI for client users to configure all the different parameters, just like what soapUI does. but without the rampart APIs, I would not be able to do that. Any plans that you will be able to provide the APIs?
>
> Thanks again!
> Raymond
>
> --- On Thu, 10/23/08, Uthaiyashankar <sh...@wso2.com> wrote:
>
> From: Uthaiyashankar <sh...@wso2.com>
> Subject: Re: APIs for ws-security paramenters
> To: "Apache AXIS C Developers List" <ax...@ws.apache.org>
> Cc: axis-c-users@ws.apache.org, rampart-c-dev@ws.apache.org
> Date: Thursday, October 23, 2008, 3:31 AM
>
> Hi Raymond,
>
> For client side, you can set username, password, password type and time
> to live parameters programatically. However, other options (like
> certificate, key, etc.) have to be set using policy files. We have to
> implement missing options. You can find more details from [1]
>
> Regards,
> Shankar
>
> [1] https://issues.apache.org/jira/browse/RAMPARTC-56
>
>
> Raymond Zhou wrote:
>
>> Hi there,
>>
>> I am planning to use rampart-c as a module in my axis2/c to support
>> ws-security in a web service client application. I know I can
>> configure the policy files in the client repository. My question is
>> that if all these variables/parameters can be set programmably using
>> some sort of APIs. I want to do this because I would like to save the
>> parameters in a database tables instead of a local file and I also
>> want to be able to develop a UI for users to easily set/edit/change
>> the values.
>>
>> Thanks!
>> Raymond
>>
>>
>>
>
>
>
--
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"
Re: APIs for ws-security paramenters
Posted by Manjula Peiris <ma...@wso2.com>.
On Wed, 2008-10-22 at 22:06 -0700, Raymond Zhou wrote:
> Hi, Uthaiyashankar,
>
> Thanks much for the info. I am a bit surprised that we can only set
> the few parameters programmably. I don't think it's ideal for client
> users to set up so many parameters in a complicated xml file in a file
> system. For my self, I would certainly like to provide a UI for client
> users to configure all the different parameters, just like what soapUI
> does. but without the rampart APIs, I would not be able to do that.
> Any plans that you will be able to provide the APIs?
>
> I don't think there are immediate plans to implement whole
> configuration API programmatically. Because when the policy become
> very complex this API will also become complex and using it will
> become harder. There is a tool [1] where you can pass these security
> configurations as command line options rather than using a policy
> file. You may worth trying it.
>
> [1] http://wso2.org/projects/wsclient
>
> Thanks,
> -Manjula.
>
>
> Thanks again!
> Raymond
>
> --- On Thu, 10/23/08, Uthaiyashankar <sh...@wso2.com> wrote:
>
> From: Uthaiyashankar <sh...@wso2.com>
> Subject: Re: APIs for ws-security paramenters
> To: "Apache AXIS C Developers List" <ax...@ws.apache.org>
> Cc: axis-c-users@ws.apache.org, rampart-c-dev@ws.apache.org
> Date: Thursday, October 23, 2008, 3:31 AM
>
> Hi Raymond,
>
> For client side, you can set username, password, password type and time
> to live parameters programatically. However, other options (like
> certificate, key, etc.) have to be set using policy files. We have to
> implement missing options. You can find more details from [1]
>
> Regards,
> Shankar
>
> [1] https://issues.apache.org/jira/browse/RAMPARTC-56
>
>
> Raymond Zhou wrote:
> > Hi there,
> >
> > I am planning to use rampart-c as a module in my axis2/c to support
> > ws-security in a web service client application. I know I can
> > configure the policy files in the client repository. My question is
> > that if all these variables/parameters can be set programmably using
> > some sort of APIs. I want to do this because I would like to save the
> > parameters in a database tables instead of a local file and I also
> > want to be able to develop a UI for users to easily set/edit/change
> > the values.
> >
> > Thanks!
> > Raymond
> >
> >
>
>
> --
> S.Uthaiyashankar
> Software Architect
> WSO2 Inc.
> http://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: APIs for ws-security paramenters
Posted by Manjula Peiris <ma...@wso2.com>.
On Wed, 2008-10-22 at 22:06 -0700, Raymond Zhou wrote:
> Hi, Uthaiyashankar,
>
> Thanks much for the info. I am a bit surprised that we can only set
> the few parameters programmably. I don't think it's ideal for client
> users to set up so many parameters in a complicated xml file in a file
> system. For my self, I would certainly like to provide a UI for client
> users to configure all the different parameters, just like what soapUI
> does. but without the rampart APIs, I would not be able to do that.
> Any plans that you will be able to provide the APIs?
>
> I don't think there are immediate plans to implement whole
> configuration API programmatically. Because when the policy become
> very complex this API will also become complex and using it will
> become harder. There is a tool [1] where you can pass these security
> configurations as command line options rather than using a policy
> file. You may worth trying it.
>
> [1] http://wso2.org/projects/wsclient
>
> Thanks,
> -Manjula.
>
>
> Thanks again!
> Raymond
>
> --- On Thu, 10/23/08, Uthaiyashankar <sh...@wso2.com> wrote:
>
> From: Uthaiyashankar <sh...@wso2.com>
> Subject: Re: APIs for ws-security paramenters
> To: "Apache AXIS C Developers List" <ax...@ws.apache.org>
> Cc: axis-c-users@ws.apache.org, rampart-c-dev@ws.apache.org
> Date: Thursday, October 23, 2008, 3:31 AM
>
> Hi Raymond,
>
> For client side, you can set username, password, password type and time
> to live parameters programatically. However, other options (like
> certificate, key, etc.) have to be set using policy files. We have to
> implement missing options. You can find more details from [1]
>
> Regards,
> Shankar
>
> [1] https://issues.apache.org/jira/browse/RAMPARTC-56
>
>
> Raymond Zhou wrote:
> > Hi there,
> >
> > I am planning to use rampart-c as a module in my axis2/c to support
> > ws-security in a web service client application. I know I can
> > configure the policy files in the client repository. My question is
> > that if all these variables/parameters can be set programmably using
> > some sort of APIs. I want to do this because I would like to save the
> > parameters in a database tables instead of a local file and I also
> > want to be able to develop a UI for users to easily set/edit/change
> > the values.
> >
> > Thanks!
> > Raymond
> >
> >
>
>
> --
> S.Uthaiyashankar
> Software Architect
> WSO2 Inc.
> http://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: APIs for ws-security paramenters
Posted by Raymond Zhou <ra...@yahoo.com>.
Hi, Uthaiyashankar,
Thanks much for the info. I am a bit surprised that we can only set the few parameters programmably. I don't think it's ideal for client users to set up so many parameters in a complicated xml file in a file system. For my self, I would certainly like to provide a UI for client users to configure all the different parameters, just like what soapUI does. but without the rampart APIs, I would not be able to do that. Any plans that you will be able to provide the APIs?
Thanks again!
Raymond
--- On Thu, 10/23/08, Uthaiyashankar <sh...@wso2.com> wrote:
From: Uthaiyashankar <sh...@wso2.com>
Subject: Re: APIs for ws-security paramenters
To: "Apache AXIS C Developers List" <ax...@ws.apache.org>
Cc: axis-c-users@ws.apache.org, rampart-c-dev@ws.apache.org
Date: Thursday, October 23, 2008, 3:31 AM
Hi Raymond,
For client side, you can set username, password, password type and time
to live parameters programatically. However, other options (like
certificate, key, etc.) have to be set using policy files. We have to
implement missing options. You can find more details from [1]
Regards,
Shankar
[1] https://issues.apache.org/jira/browse/RAMPARTC-56
Raymond Zhou wrote:
> Hi there,
>
> I am planning to use rampart-c as a module in my axis2/c to support
> ws-security in a web service client application. I know I can
> configure the policy files in the client repository. My question is
> that if all these variables/parameters can be set programmably using
> some sort of APIs. I want to do this because I would like to save the
> parameters in a database tables instead of a local file and I also
> want to be able to develop a UI for users to easily set/edit/change
> the values.
>
> Thanks!
> Raymond
>
>
--
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://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: APIs for ws-security paramenters
Posted by Raymond Zhou <ra...@yahoo.com>.
Hi, Uthaiyashankar,
�
Thanks much for the info. I am a bit surprised that we can only set the few parameters programmably. I don't think it's ideal for client users to set�up so many�parameters in�a complicated xml file in a file system. For my self, I would certainly like to provide a UI for�client�users�to configure�all the different parameters, just like what soapUI does. but without the rampart APIs, I would not be able to do that. Any plans that you will be able to provide the APIs?
�
Thanks again!
Raymond
--- On Thu, 10/23/08, Uthaiyashankar <sh...@wso2.com> wrote:
From: Uthaiyashankar <sh...@wso2.com>
Subject: Re: APIs for ws-security paramenters
To: "Apache AXIS C Developers List" <ax...@ws.apache.org>
Cc: axis-c-users@ws.apache.org, rampart-c-dev@ws.apache.org
Date: Thursday, October 23, 2008, 3:31 AM
Hi Raymond,
For client side, you can set username, password, password type and time
to live parameters programatically. However, other options (like
certificate, key, etc.) have to be set using policy files. We have to
implement missing options. You can find more details from [1]
Regards,
Shankar
[1] https://issues.apache.org/jira/browse/RAMPARTC-56
Raymond Zhou wrote:
> Hi there,
>
> I am planning to use rampart-c as a module in my axis2/c to support
> ws-security in a web service client application. I know I can
> configure the policy files in the client repository. My question is
> that if all these variables/parameters can be set programmably using
> some sort of APIs. I want to do this because I would like to save the
> parameters in a database tables instead of a local file and I also
> want to be able to develop a UI for users to easily set/edit/change
> the values.
>
> Thanks!
> Raymond
>
>
--
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://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: APIs for ws-security paramenters
Posted by Uthaiyashankar <sh...@wso2.com>.
Hi Raymond,
For client side, you can set username, password, password type and time
to live parameters programatically. However, other options (like
certificate, key, etc.) have to be set using policy files. We have to
implement missing options. You can find more details from [1]
Regards,
Shankar
[1] https://issues.apache.org/jira/browse/RAMPARTC-56
Raymond Zhou wrote:
> Hi there,
>
> I am planning to use rampart-c as a module in my axis2/c to support
> ws-security in a web service client application. I know I can
> configure the policy files in the client repository. My question is
> that if all these variables/parameters can be set programmably using
> some sort of APIs. I want to do this because I would like to save the
> parameters in a database tables instead of a local file and I also
> want to be able to develop a UI for users to easily set/edit/change
> the values.
>
> Thanks!
> Raymond
>
>
--
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://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: APIs for ws-security paramenters
Posted by Uthaiyashankar <sh...@wso2.com>.
Hi Raymond,
For client side, you can set username, password, password type and time
to live parameters programatically. However, other options (like
certificate, key, etc.) have to be set using policy files. We have to
implement missing options. You can find more details from [1]
Regards,
Shankar
[1] https://issues.apache.org/jira/browse/RAMPARTC-56
Raymond Zhou wrote:
> Hi there,
>
> I am planning to use rampart-c as a module in my axis2/c to support
> ws-security in a web service client application. I know I can
> configure the policy files in the client repository. My question is
> that if all these variables/parameters can be set programmably using
> some sort of APIs. I want to do this because I would like to save the
> parameters in a database tables instead of a local file and I also
> want to be able to develop a UI for users to easily set/edit/change
> the values.
>
> Thanks!
> Raymond
>
>
--
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"