Authentication token expired

Question

We're using API V13 of the Bing Ads API.

It was working fine and then without us touching our code, we started to get "AuthenticationTokenExpired" errors.

We checked an re-checked many times and our authentication token is created right before making a call, so it can't have expired in a few seconds. What's going on?

Below is the exception we're getting:

 [previous:Exception:private] => 
    [faultstring] => Invalid client data. Check the SOAP fault details for more information. TrackingId: 4621e7a3-5add-456f-800d-45aab387f34e.
    [faultcode] => s:Server
    [faultcodens] => 
    [faultactor] => 
    [detail] => stdClass Object
        (
            [AdApiFaultDetail] => stdClass Object
                (
                    [TrackingId] => 4621e7a3-5add-456f-800d-45aab387f34e
                    [Errors] => stdClass Object
                        (
                            [AdApiError] => stdClass Object
                                (
                                    [Code] => 109
                                    [Detail] => 
                                    [ErrorCode] => AuthenticationTokenExpired
                                    [Message] => Authentication token expired. Please renew it or obtain a new token.
                                )

                        )

                )

        )

Answer 1

We were able to resolve our issue by changing the requested scope to "openid offline_access https://ads.microsoft.com/msads.manage" in the OAuth authorization request that redirects the user to https://login.live.com/oauth20_authorize.srf.

Then when requesting the access token we added the scope "https://ads.microsoft.com/msads.manage" in the request. It does require the user to create a new OAuth authorization, but seems to have resolved it on our side.

Answer 2

I completely re-created the app registration and that seems to have fixed the problem.

For us we were not using the new msads.manage scope. But apart from that I changed nothing else in the re-creation process.

Answer 3

Same issue. Started on May 5th for me.

Answer 4

Same here, started 5th of May. Token is issued correctly (also refresh-tokens are issued as usual), but it instantly invalidates with the message 'AuthenticationTokenExpired'. Is this a known issue on Microsoft Ads end?

Answer 5

Same problem for me. It started happening late in the afternoon on Friday May 5th. Zero code changes on our end. Our Refresh Token is successfully being exchanged for an Access Token, but then any requests we make using the tokens are met with "AuthenticationTokenExpired".

For the Microsoft folks, here are a few of the most recent response tracking IDs. Please advise.

22a1e644-0898-480d-983f-5f912189f4b9

960a5543-d44f-427e-871e-4fc4e5d5026a

363724e4-b9ac-44da-a21a-008218b589ad