Menu
▾
▴
#948 Alternatives for basic git authentication that can be cached with git credential manager
Hello,
On one of my Windows computers I use of OpenSSH is restricted, so I would like to fall back on https for git. As far as I can see, with https only basic authenticatie with username and password is available. However, I am using 2FA and I have learnt that have to add the 6 digit code to my password. But that is quit useless, since I cannot cache my credentials with the GIt Credential Manager and have to enter my password en code every time. I know of at least 2 other methods for https git authentication that can be cached:
- Git will prompt you to use a browser window. After login there with 2FA you can go back to git and your authorisation is cached for the next time you need git authorisation.
- You can generate a Personal Access Token (PAT) and use that as a password. A PAT does not require 2FA, so can be cached
The only thing I can find in my Sourceforge account is that I can generate OAuth1 or OAuth2 credentials for applications. Based on that I can generate a Bearer token. But that is different from a PAT: I cannot use it as a replacement for my password. I believe that these credentials can only be used with the SourceForge APIs and not with git.
So my question is whether there is any method to authenticate for SourceForge git in a way that it can be cached with the Git Credential Manager on Windows? If yes, can you explain me the methods?
If not, I would like to propose a feature request for authentication through a browser window or by providing a PAT.
Thanks for your efforts.
Henk van den Akker
Ticket moved from /p/forge/site-support/27668/
Can't be converted:
Hello,
Thank you for reaching out.
We don’t currently support either of those Git options, but they’re both good suggestions.
This ticket has now been moved to our feature requests so the team can review it for future upgrades.
Sincerely,
SourceForge Support