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

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

{\rtf1\ansi\ansicpg936\deff0\deflang1033\deflangfe2052{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\lang2052\f0\fs20 Hi Howard,
\par
\par From the trace log from the client-side, it seems the kerberos policy assertion is not applied on the application. Though you've used the PolicyAttribute in the client-side proxy's partial class file to apply the PolicyAssertion, I would still suggest you try using code to apply the Polcy on the WSE client proxy class, (using the SetPolicy method instead of attribute) to see whether it helps. I remember that the WSE kerberos example's client proxy always use code to programmatically apply the policy assertion.
\par
\par Regards,
\par
\par Steven Cheng
\par Microsoft Online Community Support
\par
\par
\par ==================================================
\par
\par When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue.
\par
\par ==================================================
\par
\par
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par
\par
\par }

Relevant Pages