Can Nango help us (inlang) support fine(r)-grained github auth?

[samuelstroschein]

Hi there,

We have a discussion on finer-grained GitHub oauth, see opral/monorepo#582 (comment). I am wondering whether Nango suits our use case. Would be great if you can chip into the discussion (I haven't found a contact form).

[rguldener]

HI @samuelstroschein, how do you implement Github Auth today?

With Nango you can use Github's OAuth 2.0 flow, which gives you access to these scopes: https://docs.github.com/en/apps/oauth-apps/building-oauth-apps/scopes-for-oauth-apps
As far as I am aware, this also lets users select which orgs & repos they want to give your app access to. Like you mentioned, it is up to you and your app though to check where you have been granted access and do the appropriate API calls afterwards.

Feel free to join our Slack community if you want to chat about this in more detail: https://nango.dev/slack

[samuelstroschein]

HI @samuelstroschein, how do you implement Github Auth today?

Manually, in https://github.com/inlang/inlang/tree/main/source-code/website/src/services/auth.

Like you mentioned, it is up to you and your app though to check where you have been granted access and do the appropriate API calls afterwards.

This is the key detail. I thought Nango might handle the logic for us.

Can Nango run as express middleware? I don't want to use a hosted version as contributors will have a harder time contributing, more accounts are required, etc.

[rguldener]

No, Nango cannot run as an express middleware because it has state to keep track of (access tokens, refresh tokens, client id & secret etc.).

Sorry, sounds like it might not be a good fit for your use case unfortunately.