dimensionalOS / dimensionalOS/dimos
Add Google SSO to staging site authentication
Open
Nobody has claimed this yet.
infra
web
- Dominant language
- Python
- Stars
- 4.5k
- Forks
- 808
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 233
Description
Summary
Replace the current hardcoded password authentication on the staging site with Google SSO.
Current State
- Staging site uses a simple hardcoded password for access
- No proper identity provider integration
Requirements
- Implement Google SSO (OAuth 2.0 / OpenID Connect) for staging site authentication
- Restrict access to Dimensional org Google accounts
- Remove the hardcoded password once SSO is in place
- Ensure existing staging workflows are not disrupted during migration
Acceptance Criteria
- Users can log in to the staging site via their Dimensional Google account
- Hardcoded password auth is removed
- Only authorized Google accounts can access the site
Synced from DIM-1619 by stash
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the staging site's current hardcoded password authentication and the configuration used to deploy it. Review how Google OAuth 2.0/OpenID Connect can restrict access to Dimensional accounts without disrupting staging workflows; done means authorized users can sign in with Google and the password path is removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100