-
Notifications
You must be signed in to change notification settings - Fork 23
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
Use personal tokens for Github/Gitlab access #40
Comments
The gitlab backend is already using a token for authentication (it's not possible to auth with user+pass). I suppose the same could be implemented for the github backend. I don't understand what you mean by magit/ghub. Are you suggesting that the org-sync backend for github shouldn't handle authentication at all but rather rely on another library? I'm not familiar with the ghub library but at least magit is not a great fit since that works with git while org-sync is all about issues, which are via a HTTP JSON REST API and not via git. |
@plajjan think this is what @backerman is talking about. |
@divansantana right, ok, makes sense. |
Is this resolved? I'm trying to use this with 2FA. |
I was pleased to find that on Github you can use personal access tokens instead of password. So that worked even with 2FA. |
It would be nice if org-sync used personal tokens for Github and Gitlab access e.g. by using the magit/ghub library. In addition to following least-privilege, this change woudl take the secret out of the user's .emacs (because ghub stores the token in ~/.authinfo).
The text was updated successfully, but these errors were encountered: