Modules for GitHub org need to be enabled

[next crescent]

Hi all, when I try to enable modules for my org, I see the following:

Trial will end on the 2026-02-10. To get started enable module scanning in your preferred GitHub organizations

And it doesn't take me anywhere: am I missing something? 😅

[plain wyvern]

hey @next crescent what happens if you reload the screen? do you still see the same thing?

[next crescent]

Hard reloading the page worked!

[plain wyvern]

👍 thx. We're fixing this ASAP!

[next crescent]

Is there no way to configure a "linked" OAuth app with Google IDP's? Seems since I'm logged in with my company email, I get this GitHub error

[plain wyvern]

no it's not possible because Oauth apps only serve for authentication purposes. In order for cloud modules to work, Dagger needs a bit more permissions so it has read-only access to whatever Github repo you give it permissions to so it can manage your Dagger modules in the platform

[next crescent]

It is possible: what I'm asking is why Dagger's platform doesn't handle the separate Oauth flows (both to Goolge as the IDP and GitHub for read/acceess to the modules in repos) as a broker?

The Dagger platform would store both tokens linked to my org's identity.

Or, if your IDP provider supported it, you could use OAuth token exchanges or identity federation to handle getting a refresh token from a configured Oauth app in GitHub and storing it alongside the google auth session.

[plain wyvern]

right. I see what you're referring to now. We haven't implemented that flow yet. The only way you can current link your repo is by logging-in through Github's SSO.

I've noted your use-case and added it to the backlog.