<cryptography> settings element breaks in SP2 or SP3
- From: "ep" <reply@xxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 26 Apr 2005 13:29:46 -0500
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>
.
- Prev by Date: Re: Implementing WSE
- Next by Date: securitytokenmanagers be added programatically?
- Previous by thread: Trouble after applying SP3
- Next by thread: securitytokenmanagers be added programatically?
- Index(es):
Relevant Pages
|
