opensafely-core / opensafely-core/sysadmin
Trouble using standard Windows OAuth flow on L3 server
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 3
Description
When @AnnaB45 git clones an https git URL on her laptop, it works, using the standard Github web-based oauth (note tail-end of her git config there, in case useful):
When she does the same thing on the L3 server, from the /e/anna_r directory, she gets a GitHub login dialog, it then fails (not clear exactly how), falls back to an OpenSSH login dialog, and then fails (per this SO post).
Here's her git config on the L3 server:
As a workaround she is currently logging in with a PAT
Contributor guide
No contributing guide indexed for this repository
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 HTTPS clone from /e/anna_r on the L3 server and comparing the server and laptop Git configurations shown in the issue. Check the GitHub OAuth failure and subsequent OpenSSH fallback, using the linked Stack Overflow post as context. Done means the cause is identified and the standard GitHub web-based OAuth flow works on the server or the required workaround is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- authentication, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100