Publishing error "Cannot find signature in message"

[Nayabk]

Hello,
I get the following error when a user publishes the site:
The site cannot be published to the specified location.
FTP error: An unknown error has occurred. There was an exception running the extensions specified in the config file. ---> Cannot find signature in message.

Here is the relevant info from application.log:

2008-06-01 21:45:39,445 [1] ERROR SWsoft.SiteBuilder.Web.PublishUtil - Unknown error occured
SWsoft.SiteBuilder.BO.Facade.PublishException: Publish failed: unknown exception ---> System.Web.Services.Protocols.SoapException: There was an exception running the extensions specified in the config file. ---> Cannot find signature in message.
at SWsoft.SiteBuilder.Modules.Storage.Proxies.ServiceUtil.InvokeService[T](ObjectMethodInvoker fun)
at SWsoft.SiteBuilder.Modules.Storage.Proxies.DataFacadeProxy.ForceLocalUpgrade()
at SWsoft.SiteBuilder.BO.Facade.Publish.DynamicSitePublisher.PerformModulesMajorUpgrade(PublishSession publishSession)
at SWsoft.SiteBuilder.BO.Facade.Publish.DynamicSitePublisher.OnPublish(PublishSession publishSession, CheckResult cr)
at SWsoft.SiteBuilder.BO.Facade.Publish.SitePublisher.Publish(PublishSession publishSession)
at SWsoft.SiteBuilder.BO.Facade.Publish.PublishSiteCommand.<Run>b__0()
at SWsoft.SiteBuilder.BO.Facade.PublishHelper.CheckPublishExceptions(CheckPublishExceptionsMethod a_method)
at SWsoft.SiteBuilder.BO.Facade.Publish.PublishSiteCommand.Run()
--- End of inner exception stack trace ---


Please let me know what I can do to fix this.

 

[Nayabk]

Hello,
We are still waiting for an answer on this. Please let us know if we need to provide you any additional information. Thanks.

 

[abobykin]

Problem background:
Sitebuilder communicates with published sites via soap to manage Sitebuilder modules. Each soap message should be signed with Sitebuilder private key to ensure security; site refuse unsigned messages and messages with incorrect signature that may come from malicious users.

Exception details indicates that Sitebuilder server sends unsigned messages, that is caused by incorrect application configuration.
Check following configuration sections in Sitebuilder web.config
1. <SoapSecurityExcludes>
It’s possible that published site url matches to one of the exclude url patterns defined in ths section.
2. webServices/soapExtensionTypes
This section should be defined as following in two places:
<location path="Wizard">
…
<system.web>
…
<webServices>
<soapExtensionTypes>
<clear/>
<add group="High" priority="1" type="SWsoft.SiteBuilder.Modules.Storage.Connector.WebServices.ServiceSecurity.SecuritySoapExtension, SiteBuilder.Modules.Storage.Connector"/>
</soapExtensionTypes>
</webServices>
</system.web>
</location>
<location path="Admin">
…
<system.web>
…
<webServices>
<soapExtensionTypes>
<clear/>
<add group="High" priority="1" type="SWsoft.SiteBuilder.Modules.Storage.Connector.WebServices.ServiceSecurity.SecuritySoapExtension, SiteBuilder.Modules.Storage.Connector"/>
</soapExtensionTypes>
</webServices>
</system.web>
</location>
In case these declarations are missed or incorrect, Sitebuilder may send unsigned messages.