Problems with UsernameToken security scenario for a proxy service

Hi, I couldn't find an example of applying usernametoken auth. scenario to a proxy service, so I tried it by myself with no success: JDK = 1.5 Update 15 WSO2 ESB = 2.0.2 WIN XP Pro 2002 SP2 Scenario 1: Access WSO2 ESB GUI Admin to create a proxy service (http transport only) for an unsecured web service, hosted at Tomcat[6.0.18]+Axis2[1.4.1] bundle on the same host. Accessing the created proxy from a stand-alone java web service consumer works just fine. Scenario 2: Access WSO2 ESB GUI Admin to apply UsernameToken authentication to the proxy, created in scenario 1 and modify your stand-alone java web service consumer to provide a message sent with a proper security header. When choosing to apply UsernameToken authentication by going to Home > Manage > Service > List > Service Dashboard > Security for the service, and then checking UsernameToken from Basic Scenario list, regardless of permission settings (admin, everyone or whatever else created by your own) all calls to the proxy fail on General security error (WSSecurityEngine: Callback supplied no password for ). When choosing to apply UsernameToken authentication by using policy attachment with a custom callback handler, referenced from a policy file, all calls to the proxy fail on Read Timeout error, never reaching the target service, but failing somewhere at the ESB's front. Again, consumer messages have a valid security sctructure (varified by tcpmon). Has anyone ever succeeded to run this scenario?