What Causes Consistent Errors Due to Likely Backend Offline OAuth Token Refresh?

This topic was automatically generated from Slack. You can find the original thread here.

consistently getting these due to likely some backend offline oauth token refresh error.

every maybe 8-ish hours or so?

Oh that’s interesting, I don’t believe we’ve been seeing that across the board with GH. You’re getting it for GitHub over and over every 8 hours?

And you’re reconnecting it?

I’m reconnecting it, yes

account ID in my @edisonscientific org: apn_kVhk64y

I have a feeling it may have to do with your OAuth client — did you configure as an OAuth app or GitHub app?

It’s a GitHub app

there’s no option to differentiate between a GitHub App vs an OAuth App for the github client type

I’m basically trying to use my own GitHub App (more granular permissions than the classic OAuth App option on GitHub)

so I create my own OAuth Client info here on pipedream (oauth app ID: oa_w4ivb0 on Pipedream), use that redirect provided to me for you guys as I create the app on my GitHub org, and it connects just fine. but then some weird backend error happens (just happened again about an hour ago) that kills the connection

Yea I believe the auth APIs are different for OAuth vs App. I can look into it again later, I’m forgetting the nuances off hand, but it’s not surprising that our integration doesn’t gracefully support both.

would be really nice if it could have support for the newer/modern GitHub apps :slightly_smiling_face:

What is the motivation on your end? More granular scopes? Anything else? I don’t recall the nuances offhand.

GitHub apps offer much more extreme repo-selective permissions than the traditional OAuth scopes

it’s the same concept they have of transitioning away from the classic PATs to the Fine-Grained tokens

I’ve given up on using GitHub Apps with pipedream for now, will just rely on the Fine Grained tokens