Why am I getting WSE2008: KerberosToken is expected but not present in the security header of the incoming message.

I'm working with a WSE3 client and WSE3 server. I'm getting the above error
when my client tries to call a Web Service method on the server.

Debugging the problem, I tried using the QuickStart WSSecurityKerberos
Policy sample. When I use the QuickStart sample everything works just fine
(both client and server applications are running on the same Windows 2003 R2
Server machine -- a 64-bit machine w/ 4 Intel Xeon 2.8GHz processors, w/ 4GB
of RAM).

However, when I take the identical wse3policy.config settings from client
and server (each) and put them into a 2nd application on that same machine
(also with client app and server app running on same box), the output
processing of the client includes Wse2PiplelinePolicy+LegacyFilterWrapper.

I'm thinking that this is the crux of the problem, but I do not know how to
fix it.

When turn detailed tracing on and look at the client-side
OutputTrace.webinfo in my application, indeed I do *not* see any Kerberos
info. Here is a partial paste of that trace:

<outputMessage utc="4/17/2006 1:24:46 PM"
messageId="urn:uuid:3daeb0fb-49f3-4c17-bb87-4bfca210c00b">
<processingStep description="Unprocessed message">
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
<soap:Body>
<ImagingFolioStore
xmlns="urn:digimarc.com:ImageServer:WebServices">
<folio xmlns="urn:digimarc.com:imaging">
...
</folio>
</ImagingFolioStore>
</soap:Body>
</soap:Envelope>
</processingStep>
<processingStep description="Entering SOAP filter
Microsoft.Web.Services3.Security.Wse2PipelinePolicy+LegacyFilterWrapper" />
<processingStep description="Exited SOAP filter
Microsoft.Web.Services3.Security.Wse2PipelinePolicy+LegacyFilterWrapper" />
<processingStep description="Entering SOAP filter
Microsoft.Web.Services3.Security.Wse2PipelinePolicy+LegacyFilterWrapper" />
<processingStep description="Exited SOAP filter
Microsoft.Web.Services3.Security.Wse2PipelinePolicy+LegacyFilterWrapper" />
<processingStep description="Processed message">

On the other hand, here is the OutputTrace.webinfo from the
WSSecurityKerberos Policy sample. Note that it contains Kerberos processing:

<outputMessage utc="4/14/2006 9:10:54 PM"
messageId="urn:uuid:e3e4d2ca-e4fe-4362-87a5-11d5898886c6">
<processingStep description="Unprocessed message">
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
<soap:Body>
<StockQuoteRequest
xmlns="http://stockservice.contoso.com/wse/samples/2005/10";>
<symbols>
<Symbol>FABRIKAM</Symbol>
<Symbol>CONTOSO</Symbol>
</symbols>
</StockQuoteRequest>
</soap:Body>
</soap:Envelope>
</processingStep>
<processingStep description="Entering SOAP filter
Microsoft.Web.Services3.Design.KerberosAssertion+ClientOutputFilter" />
<processingStep description="Exited SOAP filter
Microsoft.Web.Services3.Design.KerberosAssertion+ClientOutputFilter" />
<processingStep description="Processed message">

Why the differences? How do I fix?

Howard Hoffman



.

Relevant Pages