Rampart 1.4 UsernameToken with NoPassword

[James Robson <ja...@ymail.com>]

Can anyone help with the following?

Rampart when acting as a message receiver does not set the WssConfig handleCustomPasswordTypes property to true if <sp:NoPassword /> is used.

Is there a work around to this problem? <sp:NoPassword /> does work when sending a request, but not recieving a request.

I've attached the policy, but I think that the problem is with the RampartReceiver class.


Cheers,
James



      Search 1000's of available singles in your area at the new Yahoo!7 Dating. Get Started http://au.dating.yahoo.com/?cid=53151&pid=1011

Re: Rampart 1.4 UsernameToken with NoPassword

[Nandana Mihindukulasooriya <na...@gmail.com>]

Hi James,
         I think we already have a JIRA [1] for this. As you have mentioned,
I think we need to set this property in WssConfig. This can be done in
RampartMessageData initialization. For example, we set the
PrecisionInMilliSeconds property here. Proper way to do this is parsing the
policy and checking whether the noPassword property is set to true in the
Username token. Can you attach a patch for the JIRA ?

thanks,
nandana


[1] - http://issues.apache.org/jira/browse/RAMPART-155

On Mon, Nov 3, 2008 at 11:49 AM, James Robson <ja...@ymail.com>wrote:

> Can anyone help with the following?
>
> Rampart when acting as a message receiver does not set the WssConfig
> handleCustomPasswordTypes property to true if <sp:NoPassword /> is used.
>
> Is there a work around to this problem? <sp:NoPassword /> does work when
> sending a request, but not recieving a request.
>
> I've attached the policy, but I think that the problem is with the
> RampartReceiver class.
>
>
> Cheers,
> James
>
> ------------------------------
> Search 1000's of available singles in your area at the new Yahoo!7 Dating. Get
> Started<http://au.rd.yahoo.com/dating/mail/tagline1/*http://au.dating.yahoo.com/?cid=53151&pid=1011>
> .
>



-- 
Nandana Mihindukulasooriya
WSO2 inc.

http://nandana83.blogspot.com/
http://www.wso2.org