Connector Improvement: Github Connector - Auth using Github App
AnsweredWe’re looking for a non-user-tied way to authenticate Fivetran with Github.
Right now both the OAuth and the PAT authentication methods are tied to a user. We’re wondering if the Github Connector can be improved to provide a Github App as an authentication method.
-
Hi Maegan - Thanks for submitting this request. We will be looking into this request as security for our connectors is always important.
-
This is crucial.
GitHub Apps are not limited to the 5000/requests/hour but instead have a rate limit that scales with the size of the organization. Not to mention, by authenticating with an app instead of a user, the connector won't break if the employee leaves the company.
-
Hi Maegan,
What is the main reason for utilizing non-user tied authentication? Is it purely to improve rate limits or are there other considerations?
Thanks,
Frank
-
Same here. Having auth tied to a specific user is a bit of a headache:
- if they change teams or leave the company then we need to set up auth through somebody else, which is just kicking the can
- we've seen issues where Fivetran --> GitHub API usage has negatively impacted said users by exceeding GitHub rate limits
- having a specific non-human GitHub Enterprise user for this connection is an extra cost for us that seems like it should be unnecessary
-
Seconding Sam Kessaram's 3 points; #2 just happened to me yesterday!
As a GitHub Administrator for my company, I set up the Fivetran GitHub Connector by OAuth'ing as my account. It used up all my personal rate limit and I was not able to use any other services that (Copilot, etc) that used the GitHub API.
Please sign in to leave a comment.
Comments
5 comments