Getting rid of custom authentication in the quick starts.

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I have the latest CTP of VS 2005 and the very latest Beta of WSE 3.0. And
they are working just peachy.

Although I have read quite a bit on WSE 3 (and watched a whole brunch of the
videos), I missed something pretty important, namely the following from Mike
Taulty's blog (mtaulty.com)

>> when a UsernameToken arrives at a WSE service then by default the
>> UsernameTokenManager attempts to use the credentials supplied to log in
>> to
>> Windows. If that doesn't work, the message gets bounced.

Wow, how could I have missed that?

In any event, let's say I want to change the WSSecurityUserNamePolicy
QuickStart and take out the CustomAuthentication.
How would I do this?

I get rid of CustomUsernameTokenManager, right?

Get rid of the following elements in the web.config?
<security>
Or
<securityTokenManager>
Or
<add
type="Microsoft.Web.Services3.QuickStart.CustomUsernameTokenManager"
namespace="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
localName="UsernameToken" xmlns=""/>


My attempts are greeted with a WSE910 error which seems to mean "You not
even close Error"

Thanks in advance,
Mark Bosley


.