Whitelist email domains during Google OAuth. #4042

New Issue

GiteaMirror · 2025-11-02T05:35:21-06:00

GiteaMirror commented

2025-11-02 05:35:21 -06:00

Originally created by @Ragnaruk on GitHub (Oct 1, 2019).

Gitea version (or commit ref): 1.9.3
Git version: 2.22.0
Operating system: Alpine Linux
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant
Log gist:

Description

Hello.

Is it possible to filter email domains of registering users if I'm using Google as an OAuth2 provider? I've tried setting EMAIL_DOMAIN_WHITELIST in config, but it doesn't seem to work.

Thanks.

Originally created by @Ragnaruk on GitHub (Oct 1, 2019).   - Gitea version (or commit ref): 1.9.3 - Git version: 2.22.0 - Operating system: Alpine Linux - Database (use `[x]`): - [ ] PostgreSQL - [X] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [X] Not relevant - Log gist: ## Description Hello. Is it possible to filter email domains of registering users if I'm using Google as an OAuth2 provider? I've tried setting `EMAIL_DOMAIN_WHITELIST` in config, but it doesn't seem to work. Thanks.

GiteaMirror added the issue/confirmed type/enhancement labels 2025-11-02 05:35:21 -06:00

GiteaMirror commented

2025-11-02 05:35:22 -06:00

@bagasme commented on GitHub (Oct 4, 2019):

@lunny What about kind/question label for this issue?

@bagasme commented on GitHub (Oct 4, 2019): @lunny What about kind/question label for this issue?

GiteaMirror commented

2025-11-02 05:35:22 -06:00

@stale[bot] commented on GitHub (Dec 4, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Dec 4, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 05:35:22 -06:00

@stale[bot] commented on GitHub (Dec 18, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Dec 18, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror commented

2025-11-02 05:35:23 -06:00

@stale[bot] commented on GitHub (Feb 16, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Feb 16, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

2025-11-02 05:35:23 -06:00

@Brayyy commented on GitHub (Apr 25, 2022):

Having the same issue. We're running with Google OAuth2 as our Authentication Source. We want to limit login/sign-up to our own Google company domains only, disallowing me to sign up using my personal [at]gmail.com account.

Our Grafana is currently configured to do this. Trying to log in via Google using unknown domains results in "Login Failed, required email domain not fulfilled".

The EMAIL_DOMAIN_WHITELIST option enforces that the new account being added meets the domain requirements, but it isn't enough to stop some rando from stopping by and setting up an account using their gmail account.

@Brayyy commented on GitHub (Apr 25, 2022): Having the same issue. We're running with Google OAuth2 as our Authentication Source. We want to limit login/sign-up to our own Google company domains only, disallowing me to sign up using my personal [at]gmail.com account. Our Grafana is currently configured to do this. Trying to log in via Google using unknown domains results in "Login Failed, required email domain not fulfilled". The `EMAIL_DOMAIN_WHITELIST` option enforces that the new account being added meets the domain requirements, but it isn't enough to stop some rando from stopping by and setting up an account using their gmail account.

GiteaMirror referenced this issue

2025-11-02 12:29:42 -06:00

[PR #4042] [MERGED] fix add a Ukrainian language #4036 #17213

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#4042