axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Damitha Kumarage <>
Subject Re: [jira] Resolved: (AXIS2C-407) Add security processed results to the message context.
Date Thu, 23 Nov 2006 08:44:52 GMT
Malinda Kaushalye Kapuruge (JIRA) wrote:

>     [ ]
>Malinda Kaushalye Kapuruge resolved AXIS2C-407.
>    Fix Version/s: Current (Nightly)
>       Resolution: Fixed
>Results of a security verification will be stored in a hashtable and inserted in to the
message context so that it can be used for another purpose in the future. For example in the
>The advantage is that the heavy process of getting the message envelope and processing
it using AXIOM functions can be  avoided with this approach. 
>All we have to do is call the function
>void * rampart_get_security_processed_result(const axis2_env_t *env,
>        axis2_msg_ctx_t *msg_ctx,
>        axis2_char_t *key);
Why we need to have return type as void *. Can't we have a definite 
structure like a property here.
Otherwise there will be freeing problems

>Here key is the key to a particular property 
>RAMPART_SPR_UT_USERNAME user of the username token
>RAMPART_SPR_UT_CREATED created time of the username token
>RAMPART_SPR_UT_NONCE nonce of the username token
>RAMPART_SPR_UT_PASSWORD_TYPE either plain text or the digest 
>RAMPART_SPR_TS_CREATED reated time of the timestamp token
>RAMPART_SPR_TS_EXPIRES expires time of the timestamp token
>If the we need to get all the security processed results call the function
>axis2_hash_t* rampart_get_security_processed_results_set(const axis2_env_t *env,
>    axis2_msg_ctx_t *msg_ctx)
better to have this function as
axis2_hash_t *rampart_get_all_security_processed_results(
    const axis2_env_t *env,
    axis2_msg_ctx_t *msg_ctx);

>>Add security processed results to the message context.
>>                Key: AXIS2C-407
>>                URL:
>>            Project: Axis2-C
>>         Issue Type: New Feature
>>         Components: rampart
>>   Affects Versions: M0.1
>>        Environment: NA
>>           Reporter: Malinda Kaushalye Kapuruge
>>        Assigned To: Malinda Kaushalye Kapuruge
>>           Priority: Minor
>>            Fix For: Current (Nightly)
>>After processing security headers it is better to add security processed results to
the message context. This will avoid the heavy SOAP header processing (which is kind of a
repetition of the handler logic) in the service end.
>>E.g. If username token is processed, add the usernametoken_processed_result property
to the msg_ctx.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message