I understand that Github is moving to a two token factor authentication model. What does that mean for the existing Collaboration plugin?
I believe 2FA is for accessing the website and user account details. [1]
My understanding is that for using the API as a client, only user name and Personal Access Token is required. [2]
[1] https://docs.github.com/en/github/authenticating-to-github/accessing-github-using-two-factor-authentication
[2] https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token
Phil Beauvoir is absolutely right - I am using coArchi with 2FA enabled and the only difference is that I punch in an access token instead of the account password.
I can confirm that this works the same way with MS Azure DevOps Git - which we use with MFA.
Quote from: tsanov on April 03, 2021, 18:47:58 PM
Phil Beauvoir is absolutely right - I am using coArchi with 2FA enabled and the only difference is that I punch in an access token instead of the account password.
Hi
I've tried replicating what you are doing - creating a personal access token in GitHub and pasting it into the "Identity password" field. But I still get "not authorized".
It is probably something very basic I have misunderstood, but I'm in need of help here.
That field in preferences is for accessing the SSH file.
If you are using HTTPS, the PAT is used in the repository's password field when connecting. This can be set in the Properties tab when the repository is selected.
Thank you so much - it did in fact work!