From: M Hickford <mirth.hickford@gmail.com>
To: git@vger.kernel.org
Cc: peff@peff.net
Subject: git-credential-oauth
Date: Tue, 8 Nov 2022 11:12:03 +0000 [thread overview]
Message-ID: <CAGJzqs=+fCQzkDX53H8Mz-DjXicVVgRmmzPjkatSiOpYO7wGGA@mail.gmail.com> (raw)
Hi all. I'm excited to share git-credential-oauth, a Git credential
helper that securely authenticates to GitHub, GitLab, BitBucket and
other forges using OAuth.
https://github.com/hickford/git-credential-oauth
The target user currently uses personal access tokens with
git-credential-store or git-credential-cache. I suspect most readers
of this list use SSH keys to authenticate, but you're welcome to try
it out with HTTPS remotes.
> The first time you push, the helper will open a browser window to authenticate. Subsequent pushes within the cache timeout require no interaction.
This read-only credential-generating helper is designed to be used in
conjunction with existing storage helpers. It's neat how the
credential system supports multiple helpers. With the config below,
Git checks the cache for a stored credential before generating a fresh
credential.
> [credential]
> helper =
> helper = cache --timeout 7200 # two hours
> helper = oauth
Comments and suggestions welcome.
ps. Git Credential Manager already has this feature so why another
helper? git-credential-oauth is a simpler app that just does OAuth.
It's developed in Go so should be easy to package for Linux distros.
The install size is smaller. For a full comparison, see
https://github.com/hickford/git-credential-oauth#comparison-with-git-credential-manager
.
reply other threads:[~2022-11-08 11:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGJzqs=+fCQzkDX53H8Mz-DjXicVVgRmmzPjkatSiOpYO7wGGA@mail.gmail.com' \
--to=mirth.hickford@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).