GitHub Desktop for Linux fails authentication in cloning a repo requiring a PAT.

[gtrevi]

The problem

On Ubuntu 20.04, cloning a private repo on GitHub requiring PAT fails, whereas both bare git command line and GitHub Desktop for Windows can perfectly clone the repo just fine, with the same PAT credentials.
This issue is happening only when using GitHub Desktop for Linux

My PAT is generated with all permissions enabled.

Release version

Version 2.9.3-linux3 (x64)

Operating system

Ubuntu 20.04.4 LTS

Steps to reproduce the behavior

Just go for "Clone a repository from the internet..." on a Private repo, requiring PAT authentication.

Log files

2022-07-19.desktop.production.log

Screenshots

Additional context

No response

[Chifouuu]

I have the same problem

[shiftkey]

Just go for "Clone a repository from the internet..." on a Private repo, requiring PAT authentication.

@gtrevi @Chifouuu is this a repository belonging to an organization?

[Chifouuu]

yes

[shiftkey]

I believe this is #217 and organizations having OAuth application restrictions enabled. I'm not 100% sure why a PAT wouldn't work with this case but it's a known difference between this and the Windows build (with this one being unofficial).

I'd suggest trying to add the repository manually and seeing if the fetch/push/pull encounters the same issue.

[github-actions]

Thank you for your issue!
We haven’t gotten a response to our questions above. With only the information that is currently in the issue, we don’t have enough information to take action. We’re going to close this but don’t hesitate to reach out if you have or find the answers we need. If you answer our questions above, this issue will automatically reopen.

[gtrevi]

@shiftkey thanks for looking into this.
Cloning through the CLI, and then adding them as local repos works, but unfortunately, fetch/push/pull do encounter the same issue.

[ShinoharaHaruna]

Same problem here. Since I do not want to modify the git url using PAT, nor do I want to return to git command line, my temporary method is to cancel all restrictions in <Organization>|Settings|Third-party Access|OAuth application policy|Third-party application access policy.

[shiftkey]

Please follow along with #217 which is the root cause here.