Re: Kerberos Authentication and WSE 3.0
- From: "RAMMURALY" <RAAMMURALY@xxxxxxxxx>
- Date: 27 Feb 2006 19:36:17 -0800
Hi Many thanks,
I have followed the pattern article. I am testing this on a windows xp
box
1) I created a domain account with suggested privileges
2) I have changed the processmodel section to run under this account
3) I have created a arbitrary SPN in my domain controller for the
account
But the WSE 841 refuses to go away. This is a proof of concept
application and i am unable to get past this for more than 48 hours!!!
System.Web.Services.Protocols.SoapHeaderException:
System.Web.Services.Protocols.SoapHeaderException: Server unavailable,
please try later ---> System.ApplicationException: WSE841: An error
occured processing an outgoing fault response. --->
System.Web.Services.Protocols.SoapHeaderException:
Microsoft.Web.Services3.Security.SecurityFault: SecurityContextToken is
expected but not present in the security header of the incoming
message.
at
Microsoft.Web.Services3.Security.SecureConversationServiceReceiveSecurityFilter.ValidateSecureConversationMessageSecurity(SoapEnvelope
envelope, Security security, MessageProtectionRequirements request)
at
Microsoft.Web.Services3.Security.SecureConversationServiceReceiveSecurityFilter.ValidateMessageSecurity(SoapEnvelope
envelope, Security security)
at
Microsoft.Web.Services3.Security.ReceiveSecurityFilter.ProcessMessage(SoapEnvelope
envelope)
at Microsoft.Web.Services3.Pipeline.ProcessInputMessage(SoapEnvelope
envelope)
at Microsoft.Web.Services3.WseProtocol.FilterRequest(SoapEnvelope
requestEnvelope)
at Microsoft.Web.Services3.WseProtocol.RouteRequest(SoapServerMessage
message)
at System.Web.Services.Protocols.SoapServerProtocol.Initialize()
at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type
type, HttpContext context, HttpRequest request, HttpResponse response,
Boolean& abortProcessing)
.
- Follow-Ups:
- Re: Kerberos Authentication and WSE 3.0
- From: ArchitectOnTheEdge
- Re: Kerberos Authentication and WSE 3.0
- References:
- Kerberos Authentication and WSE 3.0
- From: RAMMURALY
- Re: Kerberos Authentication and WSE 3.0
- From: ArchitectOnTheEdge
- Kerberos Authentication and WSE 3.0
- Prev by Date: Wse 3.0 - UriFormatException: Invalid URI
- Next by Date: Question in CustomerUsernameToken and the password.
- Previous by thread: Re: Kerberos Authentication and WSE 3.0
- Next by thread: Re: Kerberos Authentication and WSE 3.0
- Index(es):
Relevant Pages
|