Both the EU01 and US01 direct OAuth endpoints are broken on Gitpod/Ona's backend for user-level authentication
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Bug description
Both the EU01 and US01 direct OAuth endpoints are broken on Gitpod/Ona's backend for user-level authentication.
Steps to reproduce
Using Google's Gemini for the past 4 days have been trying to resolve this issue but we are going in circles.
Workspace affected
Both the EU01 and US01
Expected behavior
Actually authenticating.
Example repository
Not Applicable
Anything else?
I also sent an email to both addresses "support@gitpod.io + support@ona.com".
I am pinging the following individuals since they have the most recent amount of commits they can investigate 🔎.
@kylos101 @geropl @autofix-bot
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 reproducing the direct OAuth failures for user-level authentication in both the EU01 and US01 workspaces, using the screenshots and reported expected behavior as reference. Trace the backend entry points handling these OAuth endpoints; done means users can authenticate successfully in both environments. No files or tests are identified in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, authentication, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100