Answered by:
'microsoft.identityModel' has invalid child element 'applicationService'

Question
-
Hi,
I am trying to setup a simple WCF service/client to integrate with Geneva Server. After I run FedUtil.exe, the Service Web.config is updated and a new metadata.xml file is generated. However; I am no longer abe to get to the Service after this update.
Looking at the Web.config file, I see:
"Warning 1 The element 'microsoft.identityModel' has invalid child element 'applicationService'. List of possible elements expected: 'audienceUris, serviceCertificate, securityTokenHandlers, windowsClaimsIdentity, maximumClockSkew, issuerTokenResolver, serviceTokenResolver, federatedAuthentication, claimsAuthenticationManager, issuerNameRegistry'. C:\VisualStudio\EchoPing\ECH-IIS\Web.config 39 6 ECH-IIS"
Tried to add microsoft.identityModel dll from the geneva framework dir to the project but that did not help. Any help is much appreciated.
Here is my Web.config:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<system.serviceModel>
<diagnostics>
<messageLogging logMalformedMessages="false" logMessagesAtServiceLevel="false" logMessagesAtTransportLevel="false" />
</diagnostics>
<behaviors>
<serviceBehaviors>
<behavior name="NewBehavior">
<serviceMetadata httpGetEnabled="true" />
</behavior>
</serviceBehaviors>
</behaviors>
<services>
<service behaviorConfiguration="NewBehavior" name="com.ibm.was.wssample.sei.EchoServicePortImpl">
<endpoint address="WSSampleSei/EchoService" binding="basicHttpBinding" bindingConfiguration="NewBinding0" contract="EchoServicePortType" />
<endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" />
</service>
</services>
<bindings>
<basicHttpBinding>
<binding name="NewBinding0" />
</basicHttpBinding>
</bindings>
</system.serviceModel>
<microsoft.identityModel>
<audienceUris>
<add value="https://localhost/echo/Echo.svc/" />
</audienceUris>
<issuerNameRegistry type="Microsoft.IdentityModel.Tokens.ConfigurationBasedIssuerNameRegistry">
<trustedIssuers>
<add thumbprint="52B4F78B8F5575B903EFDAAA2BC3055BD2C92FF4" name="CN=localhost" />
</trustedIssuers>
</issuerNameRegistry>
<federatedAuthentication enabled="true">
<wsFederation passiveRedirectEnabled="true" issuer="https://wsi9.wsinterop.ibm.us/FederationPassive/" realm="https://localhost/echo/Echo.svc/" />
</federatedAuthentication>
<!--The applicationService element is for metadata generation only. The application registration tool uses this section to publish application metadata. The application does not need to access this element.-->
<applicationService>
<claimTypeRequired>
<claimType type="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name" />
</claimTypeRequired>
</applicationService>
<serviceCertificate>
<certificateReference x509FindType="FindBySubjectDistinguishedName" findValue="CN=localhost" storeLocation="LocalMachine" storeName="My" />
</serviceCertificate>
</microsoft.identityModel>
</configuration>Monday, March 23, 2009 7:34 PM
Answers
-
FedUtil does not support configuring WCF services yet. It only supports configuring ASP.NET applications for passive federation.
- Proposed as answer by Helali Bhuiyan - MSFT Wednesday, March 25, 2009 9:18 PM
- Marked as answer by Marc GoodnerMicrosoft employee Monday, April 13, 2009 4:07 PM
Wednesday, March 25, 2009 9:17 PM
All replies
-
Hi!
Try to remove the element 'applicationService' from web.config.
I will investigate why it appeared and why it coused problem.- Proposed as answer by Svyatoslav Trukhanov - MSFTModerator Tuesday, March 24, 2009 6:31 AM
Tuesday, March 24, 2009 6:31 AMModerator -
FedUtil does not support configuring WCF services yet. It only supports configuring ASP.NET applications for passive federation.
- Proposed as answer by Helali Bhuiyan - MSFT Wednesday, March 25, 2009 9:18 PM
- Marked as answer by Marc GoodnerMicrosoft employee Monday, April 13, 2009 4:07 PM
Wednesday, March 25, 2009 9:17 PM