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 Manjula Peiris <ma...@wso2.com> on 2008/01/21 06:23:43 UTC
Re: WS-SecureConversation specific policy assertion support for
neethi
Hi Sankar,
When keeping the BootstrapPolicy I think it is good to store it as a
(neethi_policy_t *) inside SecureConversationToken. Do you have any
different plans ?
-Thnaks,
Manjula.
On Mon, 2008-01-21 at 10:10 +0530, Uthaiyashankar wrote:
> Hi devs,
>
> We are implementing WS-SecureConversation support to rampart/C. In order
> to do that, there are some secure conversation specific
> WS-SecurityPolicy assertions which are needed to be implemented in
> neethi. The assertions are,
>
> * SecurityContextToken assertion
> * SecureConversationToken assertion
> * BootstrapPolicy assertion
>
> The modification of neethi will be introducing support for above
> assertions. Since, it is just an addition (based on Ws-SecurityPolicy
> specification), modification to existing neethi codes will be minimal.
>
> Any comments or suggestions are invited.
>
> Regards,
> Shankar.
>
>
> ---------------------------------------------------------------------
> 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: WS-SecureConversation specific policy assertion support for neethi
Posted by Uthaiyashankar <sh...@wso2.com>.
Manjula Peiris wrote:
> Hi Sankar,
>
> When keeping the BootstrapPolicy I think it is good to store it as a
> (neethi_policy_t *) inside SecureConversationToken. Do you have any
> different plans ?
>
Exactly, that is the plan I am having. I guess, it will be the best way
to implement.
Regards,
Shankar.
> -Thnaks,
> Manjula.
>
>
> On Mon, 2008-01-21 at 10:10 +0530, Uthaiyashankar wrote:
>
>> Hi devs,
>>
>> We are implementing WS-SecureConversation support to rampart/C. In order
>> to do that, there are some secure conversation specific
>> WS-SecurityPolicy assertions which are needed to be implemented in
>> neethi. The assertions are,
>>
>> * SecurityContextToken assertion
>> * SecureConversationToken assertion
>> * BootstrapPolicy assertion
>>
>> The modification of neethi will be introducing support for above
>> assertions. Since, it is just an addition (based on Ws-SecurityPolicy
>> specification), modification to existing neethi codes will be minimal.
>>
>> Any comments or suggestions are invited.
>>
>> Regards,
>> Shankar.
>>
>>
>> ---------------------------------------------------------------------
>> 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: WS-SecureConversation specific policy assertion support for neethi
Posted by Uthaiyashankar <sh...@wso2.com>.
Manjula Peiris wrote:
> Hi Sankar,
>
> When keeping the BootstrapPolicy I think it is good to store it as a
> (neethi_policy_t *) inside SecureConversationToken. Do you have any
> different plans ?
>
Exactly, that is the plan I am having. I guess, it will be the best way
to implement.
Regards,
Shankar.
> -Thnaks,
> Manjula.
>
>
> On Mon, 2008-01-21 at 10:10 +0530, Uthaiyashankar wrote:
>
>> Hi devs,
>>
>> We are implementing WS-SecureConversation support to rampart/C. In order
>> to do that, there are some secure conversation specific
>> WS-SecurityPolicy assertions which are needed to be implemented in
>> neethi. The assertions are,
>>
>> * SecurityContextToken assertion
>> * SecureConversationToken assertion
>> * BootstrapPolicy assertion
>>
>> The modification of neethi will be introducing support for above
>> assertions. Since, it is just an addition (based on Ws-SecurityPolicy
>> specification), modification to existing neethi codes will be minimal.
>>
>> Any comments or suggestions are invited.
>>
>> Regards,
>> Shankar.
>>
>>
>> ---------------------------------------------------------------------
>> 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