-
Notifications
You must be signed in to change notification settings - Fork 9.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Authentication issue #18623
Comments
Thanks for your report! This looks similar to #18586 but I think you shouldn't run into this problem if, as you mention, repos E and F are hosted on different domain names (vs let's say Can you confirm |
I'm very sorry, that's true, the domain names are the same, but different companies (paths) as you mentioned : |
Yeah you're going to get burned here by exactly what was described in #18586 due to multiple pats for multiple organizations, Bummer! I went ahead and updated with a single comment that would get you workable for at least one of the orgs: #18586 (comment) |
👍🏽 #18586 |
I have same problem with 3.3.18 |
follow. i have authentication issue after update to 3.3.18 today |
Hello 👋 Please, try the latest beta (3.3.19-beta2) from https://desktop.github.com/beta which includes support for multiple git credentials on the same host based on different repository paths and let us know if it works. After updating, you might need to re-enter your credentials for your Azure DevOps repositories. For hosts other than
Thank you for your patience 🙏 |
Hi sergiou87, However, when i rollback to version 3.3.5, it works. i dont see the authentication issue anymore. |
Thanks for your report @chintingtan I'm looking at your logs and your issue seems slightly different:
Would you mind filing a new issue with your logs so we can help you there more effectively? Thank you 🙏 |
Ok sure. i will file a new issue. |
You can download 3.4.0 now from https://desktop.github.com (auto-updates are rolled out progressively and might take longer) Closing this now, thank you for your patience 🙏 |
3.4.0 fixed the issue, thank you very much :) |
The problem
The PAT token gets lost on this scenario :
(No submodules, nothing special on any of these repo's)
Repo A : Gitlab private (company) repo 1 (domain 1) (Ssh)
Repo B : Gitlab private (company) repo 2 (domain 1) (Ssh)
Repo C : Gitlab private (company) repo 3 (domain 1) (Ssh)
Repo D : Gitlab private (company) repo 4 (domain 1) (Ssh)
Repo E : Azure DevOps private (company) repo 1 (domain 2) (PAT)
Repo F : Azure DevOps private (company) repo 2 (domain 3) (PAT)
Release version
3.3.18
Operating system
Windows 11
Steps to reproduce the behavior
The PAT token gets lost on this scenario :
(No submodules, nothing special on any of these repo's)
Repo A : Gitlab private (company) repo 1 (domain 1) (Ssh)
Repo B : Gitlab private (company) repo 2 (domain 1) (Ssh)
Repo C : Gitlab private (company) repo 3 (domain 1) (Ssh)
Repo D : Gitlab private (company) repo 4 (domain 1) (Ssh)
Repo E : Azure DevOps private (company) repo 1 (domain 2) (PAT)
Repo F : Azure DevOps private (company) repo 2 (domain 3) (PAT)
Log files
No response
Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: