SecurityContextToken is expected but not present

Tech-Archive recommends: Fix windows errors by optimizing your registry

I am a newbie to WSE and I am using WSE 3.0. Scenario is that I have created
server side certificate using makecert tool and added it to client side as
present in the batch file that comes with the tool.

I am trying to use usernameForCertificateSecurity with the x509 created by
me. I have created the server side policy and by debuggin i see that it does
come in the CustomUsernameTokenManager.AuthenticateToken that I have created.
Soon as this function returns the password that I have set as the token
username (also sending the same from client side) i get the favourite

"Security requirements are not satisfied because the security header is not
present in the incoming message."

exception on client side. When I trace in the inputtrace.webinfo I see that
the real exception is "Exception thrown: SecurityContextToken is expected but
not present in the security header of the incoming message."

I have set the UsernameTokenProvider on client as follows

assertion.UsernameTokenProvider = new UsernameTokenProvider(username,
username);

Anyone who can guide me what I can be missing. I have tried to duplicate the
whole sample of WSSecurityUsername that came with WSE 3.0

All help is appretiated. I really need this urgently.

Thanks.

Atif

.

Relevant Pages

  • RE: WSE 3.0 UsernameOverTransport Problem
    ... I am fairly new to WSE, in general, however I have read several ... working on integrating WSE 3.0 into an web service. ... I have verified that the client is in fact sending the Username token ... the the server side does in fact see a security header, ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • had to elevate ASPNET account user rights assignment
    ... I have a client running in our office and asp.net web service ... I finally got the wse 2.0 enabled asp.net web service ... authenticate my username and password as cleartext? ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: Implementing WSE
    ... If they match return the client supplied pwd as the return. ... Else return a predefined pwd that does not match the client supplied pwd. ... Another step you need to do is to configure the username token manager in the web.config. ... Regular web services work great and I could use them all day long but using them with WSE I get stuck. ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: Unrecogniszed SOAPAction?
    ... It discusses the SecureConversation feature in WSE. ... <response signatureOptions="IncludeAddressing, IncludeTimestamp, ... client side only. ... Security requirements are not satisfied because the security header ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: WSE 3.0, usernameOverTransportSecurity, custom Token Manager w/ securityTokenManager,
    ... the username token to the message. ... I'm attempting to learn how to use WSE 3.0 with Visual Studio 2005. ... protected override string AuthenticateToken(UsernameToken token) ... The client is to be a smart client application. ...
    (microsoft.public.dotnet.framework.webservices.enhancements)