[
https://issues.apache.org/jira/browse/RAMPART-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608283#action_12608283
]
Nandana Mihindukulasooriya commented on RAMPART-178:
----------------------------------------------------
I think this something Rampart Handlers should do, not the password callback
handler. Will implement this feature in Rampart.
I think getting the null is quite reasonable. Because this
currentMessageContext property is set by the message receiver, so it won't be
available at Password callback handler ( As password callback is being called
before the flow comes to Message Receiver ). This currentMessageContext is to
be used by Service Impl or units after message recievers.
> Easily obtain UserNameToken information at the Service
> ------------------------------------------------------
>
> Key: RAMPART-178
> URL: https://issues.apache.org/jira/browse/RAMPART-178
> Project: Rampart
> Issue Type: New Feature
> Affects Versions: 1.4
> Reporter: Stefan Lischke
> Assignee: Nandana Mihindukulasooriya
> Priority: Trivial
>
> We talked about this feature in the ML [1] and the proposed way [2] is very
> complicated.
> So i propose to set the username (not the password) information as property
> to the messageContext, to get it easily and quickly in the service.
> I did this very easily myself:
> In the PWCBHanlder
> MessageContext msgCtx = MessageContext.getCurrentMessageContext();
> msgCtx.setProperty("username", pwcb.getIdentifer());
> [1] http://markmail.org/message/gya424dzg5hyid4w
> [2] http://wso2.org/library/169
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
