authgear / authgear/authgear-server
Whitelist for domain name with Google Login
- Dominant language
- Go
- Stars
- 2k
- Forks
- 125
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 32
Description
## Problem
For supporting Google Workspace login
## Appetite
> How much time do we want to spend and how does that constrain the solution? (Usually 2 weeks or 6 weeks)
## Solution
Need some research to see is it better to:
1. White list domain name of login email
2. Or is there specific Google Workspace Login apart from General Google Login?
## Success definition
Allow users to easily add support for Google Workspace Login
## Rabbit holes
> Details about the solution worth calling out to avoid problems
## No-goes
> Functionality or use cases we intentionally aren’t covering to fit the appetite
Contributor guide
Research direction
No files, tests, or entry points are named. Start by researching whether Google Workspace requires a distinct Google login flow or whether restricting login email domains is sufficient, then inspect the existing Google Login integration. Done means selecting an approach that lets users add Google Workspace login.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100