Bing Ads Connector Refresh Token Issue

Slack Knowledge Base Q&A Connector Questions
, , , ,
1

Summary

The user is facing an issue with the refresh token in the Bing Ads connector, even after creating a new app and getting new tokens. The error message indicates that the grant is expired and the user needs to sign in again.


Question

Hi everyone,

My Bing Ads connector stopped working due to an issue with the refresh token.
I already created an entirely new app in Bing Ads and got new tokens but the issue still persists.

Does anyone know how to deal with this?
Thank you :pray:.

Failed to get OAuth access token by refresh token. The user could not be authenticated as the grant is expired. The user must sign in again.


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.

Join the conversation on Slack

["bing-ads-connector", "refresh-token", "oauth", "grant-expired"]
2 
2024-04-21 23:38:55 platform > Executing worker wrapper. Airbyte version: 0.57.2
2024-04-21 23:38:55 platform > Attempt 0 to save workflow id for cancellation
2024-04-21 23:38:55 platform > Using default value for environment variable SIDECAR_KUBE_CPU_LIMIT: '2.0'
2024-04-21 23:38:55 platform > 
2024-04-21 23:38:55 platform > ----- START CHECK -----
2024-04-21 23:38:55 platform > Using default value for environment variable SOCAT_KUBE_CPU_LIMIT: '2.0'
2024-04-21 23:38:55 platform > Using default value for environment variable SIDECAR_KUBE_CPU_REQUEST: '0.1'
2024-04-21 23:38:55 platform > 
2024-04-21 23:38:55 platform > Using default value for environment variable SOCAT_KUBE_CPU_REQUEST: '0.1'
2024-04-21 23:38:55 platform > Checking if airbyte/source-bing-ads:2.2.0 exists...
2024-04-21 23:38:56 platform > airbyte/source-bing-ads:2.2.0 was found locally.
2024-04-21 23:38:56 platform &gt; Creating docker container = source-bing-ads-check-48682-0-hniyt with resources io.airbyte.config.ResourceRequirements@d339dd[cpuRequest=,cpuLimit=,memoryRequest=,memoryLimit=,additionalProperties={}] and allowedHosts io.airbyte.config.AllowedHosts@7debc1c4[hosts=[<http://bingads.microsoft.com|bingads.microsoft.com>, <http://login.microsoftonline.com|login.microsoftonline.com>, <http://login.live.com|login.live.com>, <http://login.windows-ppe.net|login.windows-ppe.net>, <http://ads.microsoft.com|ads.microsoft.com>, <http://api.ads.microsoft.com|api.ads.microsoft.com>, <http://clientcenter.api.bingads.microsoft.com|clientcenter.api.bingads.microsoft.com>, *.<http://datadoghq.com|datadoghq.com>, *.<http://datadoghq.eu|datadoghq.eu>, *.<http://sentry.io],additionalProperties={}]|sentry.io],additionalProperties={}]>
2024-04-21 23:38:56 platform &gt; Preparing command: docker run --rm --init -i -w /data/48682/0 --log-driver none --name source-bing-ads-check-48682-0-hniyt --network host -v airbyte_workspace:/data -v oss_local_root:/local -e DEPLOYMENT_MODE=OSS -e WORKER_CONNECTOR_IMAGE=airbyte/source-bing-ads:2.2.0 -e AUTO_DETECT_SCHEMA=true -e LAUNCHDARKLY_KEY= -e SOCAT_KUBE_CPU_REQUEST=0.1 -e SOCAT_KUBE_CPU_LIMIT=2.0 -e FIELD_SELECTION_WORKSPACES= -e USE_STREAM_CAPABLE_STATE=true -e AIRBYTE_ROLE=dev -e WORKER_ENVIRONMENT=DOCKER -e APPLY_FIELD_SELECTION=false -e WORKER_JOB_ATTEMPT=0 -e OTEL_COLLECTOR_ENDPOINT=<http://host.docker.internal:4317> -e FEATURE_FLAG_CLIENT=config -e AIRBYTE_VERSION=0.57.2 -e WORKER_JOB_ID=48682 airbyte/source-bing-ads:2.2.0 check --config source_config.json
2024-04-21 23:38:56 platform &gt; Reading messages from protocol version 0.2.0
2024-04-21 23:39:03 platform &gt; Fetching access token ...
2024-04-21 23:39:03 platform &gt; Check failed
2024-04-21 23:39:04 platform &gt; Check connection job received output: io.airbyte.config.StandardCheckConnectionOutput@11d7f0fd[status=failed,message=AirbyteTracedException('Failed to get OAuth access token by refresh token. The user could not be authenticated as the grant is expired. The user must sign in again.'),additionalProperties={}]
2024-04-21 23:39:04 platform &gt; 
2024-04-21 23:39:04 platform &gt; ----- END CHECK -----
2024-04-21 23:39:04 platform &gt; 
2024-04-21 23:39:04 platform &gt; Retry State: RetryManager(completeFailureBackoffPolicy=BackoffPolicy(minInterval=PT10S, maxInterval=PT30M, base=3), partialFailureBackoffPolicy=null, successiveCompleteFailureLimit=5, totalCompleteFailureLimit=10, successivePartialFailureLimit=1000, totalPartialFailureLimit=10, successiveCompleteFailures=1, totalCompleteFailures=1, successivePartialFailures=0, totalPartialFailures=0)
 Backoff before next attempt: 10 seconds
2024-04-21 23:39:04 platform &gt; Failing job: 48682, reason: Connection Check Failed 795838e7-226f-48b9-9b7e-66c1db7d3fc0```
3

Hi, I have same issue.

4

Sorry, still broken for me.

5

Hi, I have the same issue,… have you ever figured out what was wrong?

6

Hi Guys, I just added secrect client and it’s successful now