WCF错误 - 从另一方收到了不安全或不正确安全的故障。请参阅内部FaultException以获取故障代码和详细信息

时间:2010-11-10 15:29:02

标签: wcf custom-binding

我在我的WCF服务的web.config中有以下给定的设置,这一直工作到今天并突然开始给出错误“从另一方收到了一个不安全或错误安全的错误。请参阅内部FaultException以获取故障代码和细节。“我已经验证了我的服务器和客户端的时间是一样的。 有什么想法吗?

<bindings>
  <customBinding>
    <binding name="stsBinding">
      <security authenticationMode="UserNameOverTransport" requireDerivedKeys="false"
          keyEntropyMode="ServerEntropy" requireSecurityContextCancellation="false"
          requireSignatureConfirmation="false">
      </security>
      <httpsTransport maxReceivedMessageSize="66665536"/>
    </binding>
  </customBinding>

  <wsFederationHttpBinding>
    <binding name="serviceFederation">

      <readerQuotas maxStringContentLength="2147483647"
               maxDepth="2147483647"
               maxBytesPerRead="2147483647"
               maxArrayLength="2147483647"/>

      <security mode="TransportWithMessageCredential">
        <!-- Ping token type MUST be SAML 1.1, do not change -->
        <message issuedTokenType="http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV1.1"
            negotiateServiceCredential="false">
          <!-- TODO: You must put the proper issuer URN of the Ping STS; normally this would be the Ping base URL -->
          <issuer address="https://my-sso-server.com"
              binding="customBinding" bindingConfiguration="stsBinding" />
        </message>
      </security>
    </binding>

1 个答案:

答案 0 :(得分:0)

要检查的事项:

  • 是否有任何已安装的Windows补丁,有时这会加强安全性并阻止工作。
  • 是否有密码已过期,通常是事情停止工作的原因。