Announcement

Collapse
No announcement yet.

TLS 1.0 - No Longer Supported from 1st December - All Betfair API Endpoints

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • TLS 1.0 - No Longer Supported from 1st December - All Betfair API Endpoints

    Please be aware that from 1st December requests to all Betfair Exchange endpoints will no longer support the TLS 1.0 security protocol

    Following the previous update relating to TLS support for Login we’ve identified a small number of customers still using TLS 1.0 to make API requests and these have been contacted individually.

    From 1st December only TLS 1.2 and above will be supported.

    Betfair Developer Program
    Last edited by BetfairDeveloperProgram; 20-11-2020, 11:43 AM. Reason: Added "From 1st December only TLS 1.2 and above will be supported."

  • #2
    Hi,

    I am running Windows Server 2012 R2 with SQL Server 2012 dB which is storing BF JSON updates for my website and ant to be sure that I have the right settings for 1st Dec.

    In Internet Options I notice TLS 1.2 is ticked (as well as TLS 1.1 etc). Is this sufficient for your requirements? Or do I need to update the registry as shown in the link below?

    https://docs.microsoft.com/en-us/mem...tls-1-2-client

    I had a look in the registry and there was no TLS entry (1.2 or 1.1) as outlined in the link. Please advise.

    Thank you,

    Simon

    Comment


    • #3
      Hi Simon,

      Thanks for contacting support directly regardiing this. Copying my response here for the benefit of others

      ""If you are logging in to Betfair from the same server successfully you should already have TLS 1.2 enabled.

      If in doubt (I cannot access the link you've provided) you can install the following update:

      https://support.microsoft.com/en-gb/...rotocols-in-wi"

      In addition, we would have contacted you directly if we'd identified any TLS 1.0 requests coming from your server IP.

      Kind Regards

      Neil

      Comment


      • #4
        Hi . i am running windows 10 , It was working fine yesterday .Today i have managed to get the ssoid but then i get the "Could not create ssl/tls secure channel.
        The same is happening on my desktop and laptop on two different programs within visual studio 2013. the security is set for TLS 1.2 and 1.3 So i am at a loss..
        Was the switch made last night?
        Think the problem might be with VISUAL STUDIO, needs updating
        Last edited by tippete; 02-12-2020, 08:59 PM.

        Comment


        • #5
          Hi tippete.

          Please see https://docs.microsoft.com/en-us/dot...rogramming/tls for potential solutions.

          Kind Regards

          Neil

          Comment


          • #6
            Here is a solution I found. To my method of sending json requests to the betfair server using the following VB code.

            Dim xhr : xhr = CreateObject("MSXML2.serverXMLHTTP")

            With xhr
            .Open("POST", Url & "/", False)
            .setRequestHeader("X-Application", AppKey)
            .setRequestHeader("Content-Type", "application/json")
            .setRequestHeader("Accept", "application/json")
            End With

            If Session <> "" Then
            xhr.setRequestHeader("X-Authentication", Session)
            End If

            .....etc
            As per Excel sample code

            I used the download found in web page https://support.microsoft.com/en-gb/...rotocols-in-wi

            ran the program and then without having to change anything my code started working again.

            In short.

            Go to Web Page
            https://support.microsoft.com/en-gb/...rotocols-in-wi


            Find the blue highlighted Download and then run it.

            Comment


            • #7
              dont think its applicable to windows 10.

              Comment


              • #8
                Doing the following worked for me in my Visual Studio 2017 project.
                Project -> ProjectName Properties -> Application -> change Target Framework to .NET Framework 4.6.2

                Comment


                • #9
                  Gracias Risi, voy a probar

                  Comment

                  Working...
                  X