0
<configuration>
  <system.serviceModel>
    <bindings>
      <ws2007HttpBinding>
        <binding name="UnifyDataService" maxReceivedMessageSize="1048576">
          <readerQuotas maxStringContentLength="32768" maxArrayLength="1048576" />
          <security>
            <transport>
              <extendedProtectionPolicy policyEnforcement="Never" />
            </transport>
          </security>
        </binding>
      </ws2007HttpBinding>
    </bindings>
    <services>
      <service behaviorConfiguration="AdoProxySite.AdoProxyBehavior"
        name="Unify.TD.Runtime.Wcf.Server.AdoProxy">
        <endpoint address="" binding="ws2007HttpBinding" bindingConfiguration="UnifyDataService"
          name="UnifyDataService" contract="Unify.TD.Runtime.Wcf.Server.IAdoProxy" />
        <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" />
      </service>
    </services>
    <behaviors>
      <serviceBehaviors>
        <behavior name="AdoProxySite.AdoProxyBehavior">
          <serviceMetadata httpGetEnabled="true"/>
          <serviceDebug includeExceptionDetailInFaults="true"/>
        </behavior>
      </serviceBehaviors>
    </behaviors>
  </system.serviceModel>
  <system.web>
    <compilation debug="true"/>
  </system.web>
</configuration>

My WCF "Web.config" shown above, I should change "" to "". How to change it?

Gramero
  • 1,835
  • 3
  • 24
  • 26
  • Provide details about your client and how / where it calls your service. Your service uses Message security with Windows client credentials so your client must be on the same network / domain as service. Your enpoint should also expose your service's identity. – Ladislav Mrnka Mar 06 '11 at 09:36
  • My client is on the same network. I test on 2 clients, one can connect to WS, but another one cannot. – Gramero Mar 06 '11 at 14:52
  • What is different about the 2 clients: e.g. are they same OS? both using domain accounts? same domain? same place in network topology (e.g. no VPN tunnel involved)? – Chris Dickson Mar 08 '11 at 15:52
  • The action that resolved for me was change the application pool Identity from "ApplicationPoolIdentity" to "NetworkService". – Rogerson Nazário Feb 20 '18 at 19:17

1 Answers1

0

This could help you: WCF error: The caller was not authenticated by the service

Community
  • 1
  • 1
Phil C
  • 3,687
  • 4
  • 29
  • 51