Re: Kerberos Authentication and WSE 3.0
- From: "ArchitectOnTheEdge" <agilegeek@xxxxxxxxx>
- Date: 27 Feb 2006 08:14:25 -0800
Ram,
It looks like you are not sending the security token correctly. The
following link should help
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag2/html/wss_ch3_impmlskerb_wse30.asp
Using the system user is not a good idea.I recommend you read the
security link
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetsec/html/SecNetAP05.asp
Hope this will help.
RAMMURALY wrote:
Hi I have been trying hard to get the kerberos authentication work with
WSE 3.0
I have a hello world service protected by a Kerberos policy file using
WSE 3.0 tool
Based on some recommendations I have done the following
1) Change ASPNET account to run under SYSTEM in machine.config
2) Given Permission "Act as Part of Operating System" for ASPNET
account
On my ASP.NET 2.0 CLIENT app i write the following lines
Dim svProxy As New localhost.ServiceWse
Dim strTargetPrincipalName As String = "host/" +
System.Net.Dns.GetHostName
Dim tok As New
Microsoft.Web.Services3.Security.Tokens.KerberosToken(strTargetPrincipalName)
svProxy.SetClientCredential(tok)
Response.Write(svProxy.HelloWorld)
I get the following error. I have absolutely no idea to fix this, i
have tried so many things but nothing did the trick, any help would be
highly appreciated.
Error Details
*****************
Exception Details: 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)
--- End of inner exception stack trace ---
--- End of inner exception stack trace ---
Thanks in Advance
Murali
.
- Follow-Ups:
- Re: Kerberos Authentication and WSE 3.0
- From: RAMMURALY
- Re: Kerberos Authentication and WSE 3.0
- References:
- Kerberos Authentication and WSE 3.0
- From: RAMMURALY
- Kerberos Authentication and WSE 3.0
- Prev by Date: Kerberos Authentication and WSE 3.0
- Next by Date: Wse 3.0 - UriFormatException: Invalid URI
- Previous by thread: Kerberos Authentication and WSE 3.0
- Next by thread: Re: Kerberos Authentication and WSE 3.0
- Index(es):
Relevant Pages
|
Loading