[
https://issues.apache.org/jira/browse/RAMPARTC-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561951#action_12561951
]
Supun Kamburugamuva commented on RAMPARTC-56:
---------------------------------------------
This is a good way to solve the problem allowing future expansions as well. How
are we going to set this structure to the svc client? One option is introducing
a new option to the svc client. But as Rampart is becoming a very important
part in axis2/c we should have a separate method in svc client to set this
structure. I think we should discuss this on axis2-c dev as well.
> 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.
