none
Webseit crashed nach TLS1.0 Deaktivierung RRS feed

  • Question

  • Hallo,

    nachdem TLS1.0 deaktiviert wurde, ging unsere Webseite nciht mehr.

    Merkwürdig ist, dass ältere Seiten kein Problem haben. Diese verwenden allerding keinen Webservice. Der Aufruf des Webservice über den Browser geht aber trotzdem. Nur aus der einen WebApplikation heraus nicht.

    ZusatzInfo: Wir haben jetzt herausgefunden, dass es mit dem Aufruf eines WebRequests in Verbindung mit unserem Webservice zusammenhängt.

    Kann man WCF WebService mit Basiauthentication irgendwie auf TLS 1.2 einstellen? UNd wenn ja, wo?

    VG


    Gruß Hipp


    • Edited by Hipp1010 Friday, November 24, 2017 12:51 PM
    Friday, November 24, 2017 10:47 AM

Answers

  • Hi VG,

    This forum is English Language support, I would suggest you change your post to English.

    By using Translate Tool, it seems your issue is related with different TLS version between WCF Service and Client.

    Is your project framework version .NET 4.0 and earlier or .NET 4.6? For .NET 4.6, the default protocol will be TLS 1.2. I think you could upgrade your project to .NET 4.6.

    Or, you could explicitly set TLS like below:

    ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12; // .NET 4.5
    ServicePointManager.SecurityProtocol = (SecurityProtocolType)3072; // .NET 4.0

    You could refer link below for more information.

    # The client and server cannot communicate, because they do not possess a common algorithm

    https://stackoverflow.com/questions/26742054/the-client-and-server-cannot-communicate-because-they-do-not-possess-a-common-a

    Best Regards,

    Tao Zhou 


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    • Marked as answer by Hipp1010 Tuesday, November 28, 2017 8:32 AM
    Monday, November 27, 2017 2:34 AM