Source Bing Ads: support oauth

[sherifnada]

Tell us about the problem you're trying to solve

With the release of Airbyte Cloud, we need to start supporting Oauth for this connector, since it's the recommended way of authenticating users into a SaaS application.

If this connector doesn't support oauth already (i.e: doesn't accept a client_id and client_secret) then we need to update its spec to accept those parameters. There are two ways to do this:

If the connector already supports some auth mechanism like api_key, I suggest that this be a oneof nested inside a top-level field called "authentication":

{ authentication: { type: object oneOf: [ // api key, // oauth ] } }

If the connector only supports webflow oauth, then no changes are needed to the properties format and we will only need to add annotations.

See the connector spec reference in the docs for reference on how a oneof can be implemented.

This should be done in a backwards compatible manner i.e: users currently supplying authentication info in the config's top-level should not be impacted by this change.

Acceptance Criteria

1. The connector supports oauth webflow authentication with client_id/client_secret in a backwards compatible manner
2. Oauth properties are annotated properly. See this PR for an example

• Source BingAds: support oauth (java part) #7442

[cheyura]

@sherifnada Public App with appropriate branding created, authorization flow checked. LastPass - Bing Ads OAUth Developer App

[antixar]

BingAds docs
Necessary scopes values: offline_access user.read

Example of consent url: https://login.microsoftonline.com/common/oauth2/v2.0/authorize?
client_id=
&response_type=code
&redirect_uri=
&response_mode=query
&scope=https://ads.microsoft.com/offline_access%20user.read

Example of token url: https://login.microsoftonline.com/common/oauth2/v2.0/token
-ContentType application/x-www-form-urlencoded
-Method POST
-Body "client_id=$clientId&scope=https://ads.microsoft.com/offline_access%20user.read&code=_code_&grant_type=authorization_code&redirect_uri=_url_"

where accounts, customer_id, developer_token, user_id, reports_start_date, hourly_reports, daily_reports, weekly_reports, monthly_reports should be forwarded from UI part

The BingAds oAuth2 implementation returns refresh_token

[misteryeo]

@annalvova05 What is this blocked on?

[bazarnov]

@misteryeo
No blockers at this moment, will work on it. Previously we were blocked by passing the additional OAuth parameters to java flow, which is no longer a blocker.

[misteryeo]

@bazarnov can we make sure to update the status? It's currently listed as Blocked :)

cc: @oustynova

[bazarnov]

@misteryeo
What status should I update?
The oAuth is implemented and tested using public client, within this PR - #12937

[misteryeo]

@bazarnov