-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[source-linkedin-ads] LinkedIn Ads connector missing Refresh Token field with OAuth2.0 Authentication #52691
Comments
This is a documentation problem ;-( If you want to use Linkedin Ads with OAuth 2, you have to sign up for your own developer app with linkedin, fill out Client ID and Client Secret, and tap the authentication button. That's because on Airbyte OSS, we can't provide our own client_id and secret app tokens. Previously, we did NOT allow you to do the OAuth2 flow, and we said that you should just provision your auth_token and refresh_token with whatever tools you want, and give us the tokens. Now we want client_id and client_secret instead. cc @bnchrch, @Hesperide, @ian-at-airbyte. If we see issues like this more often (this is 2nd time I see a user confused with new OAuth flow), we could:
|
@natikgadzhi I've been inventorying connectors that might be affected by this. This was one of them. See: https://github.com/airbytehq/airbyte-internal-issues/issues/11477. |
It’s likely that you need to check what redirect url your app has on
developer portal. It might be picky re: hosts and ports.
|
When trying to setup the Bing Ads connection, I get the same error. 2025-02-04 15:02:34,696 [io-executor-thread-6] INFO i.a.o.OAuthImplementationFactory(createNonDeclarativeOAuthImplementation):182 - Using MicrosoftBingAdsOAuthFlow for airbyte/source-bing-ads |
Connector Name
source-linkedin-ads
Connector Version
5.1.3
What step the error happened?
Configuring a new connector
Relevant information
Testing locally and running Airbyte using abctl tool I'm trying to set up a LinkedIn Ads source connector using OAuth2.0 Authentication method, but the field for Refresh Token is missing. The documentation also states that Refresh Token is required as input. Only possible way to test connector locally is using Access Token, which works, but Refresh Tokens live longer so it would be my preferred way.
Relevant log output
Contribute
The text was updated successfully, but these errors were encountered: