Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Web Services / October 2006

Tip: Looking for answers? Try searching our database.

WSE 3.0 and Kerberos: Security requirements are not satisfied  ... exception

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Mrozik - 02 Oct 2006 11:08 GMT
Hi!
I try to run sample comming with WSE 3.0 installation package  
(WSSecurityKerberosPolicyService.sln),
but I receive exception:

Calling  
http://localhost/WSSecurityKerberosPolicy/WSSecurityKerberosService.asmx

****** Exception Raised ******
<?xml version="1.0" encoding="utf-8"?><soap:Envelope  
xmlns:wsa="http://schemas.x
mlsoap.org/ws/2004/08/addressing"  
xmlns:soap="http://schemas.xmlsoap.org/soap/en
velope/"><soap:Header><wsa:Action>http://schemas.xmlsoap.org/ws/2004/08/addressi
ng/fault</wsa:Action><wsa:MessageID>urn:uuid:44e53ef8-cb66-4860-b2fb-21200189324
e</wsa:MessageID><wsa:RelatesTo>urn:uuid:b63711f0-8d3d-4fce-bb5e-70ea70599612</w
sa:RelatesTo><wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anony
mous</wsa:To></soap:Header><soap:Body><soap:Fault><faultcode>soap:Server</faultc
ode><faultstring>Server unavailable, please try  
later</faultstring><faultactor>h
ttp://localhost/WSSecurityKerberosPolicy/WSSecurityKerberosService.asmx</faultac
tor></soap:Fault></soap:Body></soap:Envelope>
Microsoft.Web.Services3.ResponseProcessingException: WSE910: An error  
happened d
uring the processing of a response message, and you can find the error in  
the in
ner exception.  You can also find the response message in the Response  
property.
 ---> System.InvalidOperationException: Security requirements are not  
satisfied
because the security header is not present in the incoming message.
   at  
Microsoft.Web.Services3.Security.SecureConversationClientReceiveSecurityFi
lter.ValidateMessageSecurity(SoapEnvelope envelope, Security security)
   at  
Microsoft.Web.Services3.Security.ReceiveSecurityFilter.ProcessMessage(Soap
Envelope envelope)
[...]

In my EventLog there is a error message:

An error occured processing an outgoing fault response.

Details of the error causing the processing failure:
System.InvalidOperationException: Send security filter on the server could  
not retrieve the operation protection requirements from the operation  
state.
   at  
Microsoft.Web.Services3.Security.SecureConversationServiceSendSecurityFilter.SecureMessage(SoapEnvelope  
envelope, Security security)
   at  
Microsoft.Web.Services3.Security.SendSecurityFilter.ProcessMessage(SoapEnvelope  
envelope)
   at Microsoft.Web.Services3.Pipeline.ProcessOutputMessage(SoapEnvelope  
envelope)
   at  
Microsoft.Web.Services3.WseProtocol.GetFilteredResponseEnvelope(SoapEnvelope  
outputEnvelope)

The SOAP fault that was being processed follows:
<soap:Envelope  
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"  
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Header>
        <wsa:Action>http://schemas.xmlsoap.org/ws/2004/08/addressing/fault</wsa:Action>
        <wsa:MessageID>urn:uuid:0997f1ff-9705-43d1-8c55-3fdf3b23b257</wsa:MessageID>
        <wsa:RelatesTo>urn:uuid:b63711f0-8d3d-4fce-bb5e-70ea70599612</wsa:RelatesTo>
        <wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To>
    </soap:Header>
    <soap:Body>
        <soap:Fault>
            <faultcode  
xmlns:prefix0="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xs
d">prefix0:InvalidSecurityToken</faultcode
>
            <faultstring>Microsoft.Web.Services3.Security.SecurityFault:  
An invalid security token was provided ---&gt;  
System.Security.SecurityException: The Kerberos credential handle could  
not be acquired. The AcquireCredentialsHandle call returned the following  
error code: Nie ma obecnie serwerów logowania dostępnych do obsługi  
żądania logowania. (in English error message is: There is no avilable  
login server for login request)

I replace targetPrincipal attribute with my data:  
targetPrincipal="host/N1054" (my computer name).

WebService and client app works on my computer (named N1054 - Windows XP  
Prof, SP 2)
- computer is in domain.

Best regards

Pawel
Mrozik - 02 Oct 2006 15:15 GMT
> Hi!
> I try to run sample comming with WSE 3.0 installation package  
> (WSSecurityKerberosPolicyService.sln),
> but I receive exception:

[....]
I found that it is connected with permission local ASPNET user
- after deploy to 2003 server it works fine.

One more question - can client be authenticated using
Kerberos and WSE when work on Windows 2000?
When I run my test client app on Windows 2000 Sp 4 IO receive exception:

System.InvalidOperationException: WSE909: The key retrieval for  
KerberosToken is not supported on Windows 2000 server.
   at  
Microsoft.Web.Services3.Security.Tokens.Kerberos.KerberosContext.get_Sessi
onKey()
   at Microsoft.Web.Services3.Security.Tokens.KerberosToken.InitializeKey()
   at Microsoft.Web.Services3.Security.Tokens.KerberosToken.get_Key()

Pawel

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.