WCF 错误 - 从另一方收到不安全或安全错误的错误。错误代码和详细信息请参见内部FaultException

发布于 2024-10-02 01:32:43 字数 1485 浏览 2 评论 0原文

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

<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>

I have the below given setting in my web.config of my WCF service, this was working fine till today and suddenly started giving the error "An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail." I have verified the time in my server and client it's same.
Any thoughts?

<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>

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

东北女汉子 2024-10-09 01:32:43

需要检查的事项:

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

Things to check:

  • Is there any windows patch that has been installed, sometimes this tightens security and stops things working.
  • Is there a password that has expired, often the cause when things stop working.
~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文