-
Notifications
You must be signed in to change notification settings - Fork 887
Restrict GitHub OAuth based on GitHub teams? #2848
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
Comments
I'm envisioning an environment variable:
This would be set to a comma-separated list of organization and team slugs:
In this example, it'd be assumed that the organization array was already permitting |
Yes I think that would be perfect! |
kylecarbs
added a commit
that referenced
this issue
Jul 8, 2022
kylecarbs
added a commit
that referenced
this issue
Jul 9, 2022
kylecarbs
added a commit
that referenced
this issue
Jul 12, 2022
This wasn't looping prior, so organizations with >100 teams couldn't login. Contributes to #2848.
kylecarbs
added a commit
that referenced
this issue
Jul 12, 2022
This wasn't looping prior, so organizations with >100 teams couldn't login. Contributes to #2848.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Can Coder's GitHub OAuth user authentication be extended to not only check if the user is a member of particular GitHub organization(s) but also whether they are a member of particular GitHub team(s)?
This would provide us with more granular control over who can access/use Coder at our company to support a more gradual roll-out to our developers and thus enable us to provide better, more focused onboarding support.
We can easily create and manage new GitHub teams within our existing GitHub organization but are not allowed to create additional GitHub organizations.
The text was updated successfully, but these errors were encountered: