Weare getting

"Microsoft.Web.Services2.Security.SecurityFault: The security tokencould not be authenticated or authorized ---> System.Exception: WSE562: The incoming username token contains a password hash. The built-in UsernameTokenManager does not support this type of UsernameToken. Please see the documentation for more details on the UsernameTokenManager.AuthenticateToken method."

when passing an invalid Username to our web service.

This is the same error you get when you try to send the password hashed without setting up a custom UsernameTokenManager. We have in fact set up a custom UsernameTokenManager and are sending hashed passwords,but all is good except in this test case when a bad username is passed in. We spent quite a bit of time digging into this one until we figured out we had fat-fingeredan invalidUsername in the unit-testing code on the client side.

This error is very misleading. I'd like any Microsoft WSE people to take noteand to ask if anyone has any ideas for a workaround that identifies the problemin a better fashion.Thanks.

-BillyB