[
https://issues.apache.org/jira/browse/RAMPARTC-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562482#action_12562482
]
S.Uthaiyashankar commented on RAMPARTC-56:
------------------------------------------
rampart_config support is added to rampart. So, client code writers can create
a rampart_config object and set username, pasword, etc. and then attach it to
svc client's option. Following code snippet shows how to do it.
rampart_config_t* client_config = NULL;
axutil_property_t *property = NULL;
client_config = rampart_config_create(env);
if(!client_config)
{
printf("Cannot create rampart config\n");
return 0;
}
rampart_config_set_username(client_config, env, "Raigama");
rampart_config_set_password(client_config, env, "RaigamaPW");
rampart_config_set_password_type(client_config, env,
RAMPART_PASSWORD_DIGEST);
rampart_config_set_ttl(client_config, env, 10);
property = axutil_property_create_with_args(env, AXIS2_SCOPE_REQUEST ,
AXIS2_TRUE, (void *)rampart_config_free, client_config);
axis2_options_set_property(options, env, RAMPART_CLIENT_CONFIGURATION,
property);
> Avoid deploying password callback modules in the client code
> ------------------------------------------------------------
>
> Key: RAMPARTC-56
> URL: https://issues.apache.org/jira/browse/RAMPARTC-56
> Project: Rampart/C
> Issue Type: Improvement
> Components: Rampart-core
> Affects Versions: 1.2.0
> Environment: N/A
> Reporter: Malinda Kaushalye Kapuruge
> Assignee: S.Uthaiyashankar
> Fix For: 1.2.0
>
>
> Right now in order to get the password, the client has to write a password
> callback module and deploy it. And then refer the name of the dll via the
> policy descriptor. This is quite unnecessary, if we can provide a callback
> function in the client code.
> So my suggestion is that we set a pointer of the callback function in to the
> message context within the client code. Later when the rampart context is
> created, we can transfer this function pointer to the rampart context.
> In this way without changing the core functionalities we can get rid of the
> password callback modules in the client side.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
