Currently we have a running CSF2.5.
In the same domain we installed a CSF3.0

To explore CSF3.0 i first installed the lite version on my XP machine, samples etc and some eperiments running fine. Now i want to redesign out CSF2.5 stuff and run it on the CSF3.0 server. Starting with the Helloworld sample again to see if everything is running ok i get this error in the event viewer and the tracelogs:

Timestamp: 9/12/2006 8:15:54 AM
Message: Session pipe line fault - Request message doesn't validate against any of the configured assertion.
Category: Session OperationalEvent
Priority: 1
EventId: 20152
Severity: Error
Title:Session
Machine: CSF03
Application Domain: /LM/W3SVC/1/Root/Session30-1-128025224799973427
Process Id: 3620
Process Name: c:\windows\system32\inetsrv\w3wp.exe
Win32 Thread Id: 1824
Thread Name:
Extended Properties:
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

<?xml version="1.0" encoding="utf-8"?>
<log>
<outputMessage utc="9/12/2006 8:15:55 AM" messageId="urn:uuid:fb7d8883-a553-43a2-acd3-6d2aa1f364bd">
<processingStep description="Unprocessed message">
<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">
<env:Body>
<env:Fault>
<env:Code>
<env:Value>env:Sender</env:Value>
<env:Subcode>
<env:Value xmlns:prefix0="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">prefix0:Security</env:Value>
</env:Subcode>
</env:Code>
<env:Reason>
<env:Text xml:lang="en">Microsoft.Web.Services3.Security.SecurityFault: Request message doesn't validate against any of the configured assertion.
at Microsoft.ConnectedServices.Sdk.Security.DynamicAssertionServiceInputFilter.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.Messaging.SoapReceiver.FilterMessage(SoapEnvelope envelope)
at Microsoft.ConnectedServices.Sdk.Messaging.CsfService.FilterMessage(SoapEnvelope envelope)
at Microsoft.Web.Services3.Messaging.SoapReceiver.ProcessMessage(SoapEnvelope message)</env:Text>
</env:Reason>
<env:Node>http://csf03/Session30/SessionManagerAdmin.ashx</env:Node>
</env:Fault>
</env:Body>
</env:Envelope>
</processingStep>
<processingStep description="Entering SOAP filter Microsoft.ConnectedServices.InternalUtils.TraceFilters.OutputTraceFilter" />
<processingStep description="Exited SOAP filter Microsoft.ConnectedServices.InternalUtils.TraceFilters.OutputTraceFilter" />
<processingStep description="Entering SOAP filter Microsoft.ConnectedServices.Sdk.Security.DynamicAssertionServiceOutputFilter" />
<processingStep description="Exited SOAP filter Microsoft.ConnectedServices.Sdk.Security.DynamicAssertionServiceOutputFilter" />
<processingStep description="Processed message">
<env:Envelope xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:env="http://www.w3.org/2003/05/soap-envelope">
<env:Header>
<wsa:Action>http://schemas.xmlsoap.org/ws/2004/08/addressing/fault</wsa:Action>
<wsa:MessageID>urn:uuid:fb7d8883-a553-43a2-acd3-6d2aa1f364bd</wsa:MessageID>
<wsa:RelatesTo>urn:uuid:3f225ad1-13d6-407e-a8a6-86589b300415</wsa:RelatesTo>
<wsa:To>soap.tcp://csf03:9100/UiFormService</wsa:To>
<wsse:Security>
<wsu:Timestamp wsu:Id="Timestamp-95702247-a34c-4822-a16d-2c0741c2088e">
<wsu:Created>2006-09-12T08:15:55Z</wsu:Created>
<wsu:Expires>2006-09-12T08:20:55Z</wsu:Expires>
</wsu:Timestamp>
</wsse:Security>
</env:Header>
<env:Body>
<env:Fault>
<env:Code>
<env:Value>env:Sender</env:Value>
<env:Subcode>
<env:Value xmlns:prefix0="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">prefix0:Security</env:Value>
</env:Subcode>
</env:Code>
<env:Reason>
<env:Text xml:lang="en">Microsoft.Web.Services3.Security.SecurityFault: Request message doesn't validate against any of the configured assertion.
at Microsoft.ConnectedServices.Sdk.Security.DynamicAssertionServiceInputFilter.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.Messaging.SoapReceiver.FilterMessage(SoapEnvelope envelope)
at Microsoft.ConnectedServices.Sdk.Messaging.CsfService.FilterMessage(SoapEnvelope envelope)
at Microsoft.Web.Services3.Messaging.SoapReceiver.ProcessMessage(SoapEnvelope message)</env:Text>
</env:Reason>
<env:Node>http://csf03/Session30/SessionManagerAdmin.ashx</env:Node>
</env:Fault>
</env:Body>
</env:Envelope>
</processingStep>
</outputMessage>
</log>

Any clues in how to solve this problem?

Thanks!

Anita

Hi Anitha,

CSF 3.0 Lite version will not required any policies to authenticate. But CSF 3.0 full version or CSF 2.5 full version will required policy for authentication.

You can use following code to get Policy

#region Client Policy

private Policy GetClientPolicy()

UsernameOverTransportAssertion policyAssertion = new UsernameOverTransportAssertion();

policyAssertion.UsernameTokenProvider = new UsernameTokenProvider(@"username","password");

return new Policy(policyAssertion);

#endregion

and you have to add this policy into your CreateSessionRequest

MessageSender messageSender = new MessageSender();

Hope it'll solve your issue.

Rgs

Vasu