WSE: <cryptography> settings element breaks in WSE SP2 or SP3

I have a WSE server app that uses the <cryptography> element in the
configuration (seen below). This worked perfectly in WSE sp1, but when I
upgraded to SP2 and then to SP3, I get the following soap fault from any WSE
web service call. I know there is not a problem with the config file, it
worked in sp1 and it is correct according to the sp3 documentation. What is
happening here?

System.Web.Services.Protocols.SoapHeaderException: Server unavailable,
please try later > System.Configuration.ConfigurationException: WSE032:
There was an error loading the microsoft.web.services2 configuration
section. > System.Configuration.ConfigurationException: WSE028: An
unrecognized configuration element was found: cryptography.

<microsoft.web.services2>
<security>
<cryptography>
<encryptionFormatters>
<add uri="urn:myEncryptionFormatter:algUri:1"
type="MyLibrary.MyEncryptionFormatter, MyLibrary, Version=1.0.2.0,
Culture=neutral, PublicKeyToken=xxxx"
/>
</encryptionFormatters>
</cryptography>
</security>
<diagnostics />
</microsoft.web.services2>

[1208 byte] By [epearson] at [2008-1-25]
# 1

Thanks for reporting this. Yes, this was a bug that was introduced in WSE 2.0 SP2 which is now being fixed. The next release of WSE 2.0 and in the CTP drops for WSE 3.0 will contain this fix.

Since this was an advanced feature you were the first to report this, so thank you.

Mark Fussell
WSE Program Manager

MarkFussell at 2007-8-21 > top of Msdn Tech,.NET Development,ASMX Web Services and XML Serialization...

.NET Development

Site Classified