Login Problem

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • gus
    Senior Member
    • Jan 2009
    • 134

    #1

    Login Problem

    The Login from my API-NG test app, whch has been working perfectly for months has suddenly started to fail (since about 10:00 today).

    The Java error message I'm getting is:
    javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.
    provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

    but I'm using the Interactive (desktop) method of logging in, so I shouldn't need to be mucking about with security certificates should I?

    is it me or the API ?
  • Dave1024
    Junior Member
    • Nov 2012
    • 1

    #2
    I have the same problem, working fine up to this morning, and now get:

    UNABLE_TO_VERIFY_LEAF_SIGNATURE

    I'm using javascript on Node. After a bit of googling I tried setting the ssl option rejectUnauthorized = false, the error then becomes FORBIDDEN (so maybe a red herring).

    Comment

    • isThatSo?
      Junior Member
      • Oct 2013
      • 1

      #3
      Temporary solution

      Same problem on my end.
      My temporary fix was copying the session token (ssoid value) from the betfair cookie manually into the application.
      Everything else works fine.

      Comment

      • GNSPS
        Junior Member
        • Oct 2013
        • 4

        #4
        Mine has stopped working too!

        Maybe something related with certificate login automation?

        Are you guys also using the non-interactive login method?

        Comment

        • gus
          Senior Member
          • Jan 2009
          • 134

          #5
          Nope, I'm using the Interactive method.

          Comment

          • GNSPS
            Junior Member
            • Oct 2013
            • 4

            #6
            Ok, guess every one is affected then...

            Gus, have you seen any report from betfair about this?

            Do you think it's because of API-NG implementation on 1st november?

            I've tried searching around but nothing from betfair at all!

            Comment

            • gus
              Senior Member
              • Jan 2009
              • 134

              #7
              Originally posted by GNSPS View Post
              Ok, guess every one is affected then...

              Gus, have you seen any report from betfair about this?

              Do you think it's because of API-NG implementation on 1st november?

              I've tried searching around but nothing from betfair at all!
              No, haven't seen anything ... that's why I keep checking this thread!

              I did wonder if it might be something as simple as the Certificate having expired at the Betfair end, but really I'm in the dark and eagerly awaiting illumination!

              Comment

              • BetfairDeveloperProgram
                Administrator
                • Oct 2008
                • 679

                #8
                Hi All,

                I'll investigate this issue further and provide an update shortly.

                Thanks

                Neil

                Comment

                • BetfairDeveloperProgram
                  Administrator
                  • Oct 2008
                  • 679

                  #9
                  Hi All,

                  This problem should now be rectified, please can you test this and confirm?

                  A change that was made this morning would have caused this issue for some customers, and this has now been fixed.

                  Thanks

                  Neil

                  Comment

                  • gus
                    Senior Member
                    • Jan 2009
                    • 134

                    #10
                    Originally posted by Betfair Developers Program View Post
                    Hi All,

                    This problem should now be rectified, please can you test this and confirm?

                    A change that was made this morning would have caused this issue for some customers, and this has now been fixed.

                    Thanks

                    Neil
                    Yep, it's working now.

                    Thanks Neil.

                    Comment

                    • GNSPS
                      Junior Member
                      • Oct 2013
                      • 4

                      #11
                      It is working perfectly now, Neil.

                      Thank you so much!

                      Comment

                      Working...
                      X