Git-Credential-Manager-Core | platform Git credential storage with authentication | Azure library

by microsoft C# Version: v2.0.475 License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | Git-Credential-Manager-Core Summary

Git-Credential-Manager-Core is a C# library typically used in Cloud, Azure applications. Git-Credential-Manager-Core has no bugs, it has no vulnerabilities and it has medium support. However Git-Credential-Manager-Core has a Non-SPDX License. You can download it from GitHub.

Git Credential Manager Core (GCM Core) is a secure Git credential helper built on .NET that runs on Windows and macOS. Linux support is in an early preview. Compared to Git's built-in credential helpers (Windows: wincred, macOS: osxkeychain, Linux: gnome-keyring) which provides single-factor authentication support working on any HTTP-enabled Git repository, GCM Core provides multi-factor authentication support for Azure DevOps, Azure DevOps Server (formerly Team Foundation Server), GitHub, and Bitbucket. Git Credential Manager Core (GCM Core) replaces the .NET Framework-based Git Credential Manager for Windows (GCM), and the Java-based Git Credential Manager for Mac and Linux (Java GCM), providing a consistent authentication experience across all platforms.

Support

Quality

Security

License

Reuse

Support

Git-Credential-Manager-Core has a medium active ecosystem.

It has 926 star(s) with 181 fork(s). There are 35 watchers for this library.

It had no major release in the last 12 months.

There are 51 open issues and 110 have been closed. On average issues are closed in 45 days. There are 7 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of Git-Credential-Manager-Core is v2.0.475

Quality

Git-Credential-Manager-Core has 0 bugs and 0 code smells.

Security

Git-Credential-Manager-Core has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

Git-Credential-Manager-Core code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

Git-Credential-Manager-Core has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

Git-Credential-Manager-Core releases are available to install and integrate.

Installation instructions are not available. Examples and code snippets are available.

Git-Credential-Manager-Core saves you 36 person hours of effort in developing the same functionality from scratch.

It has 96 lines of code, 0 functions and 286 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of Git-Credential-Manager-Core

Get all kandi verified functions for this library.

Git-Credential-Manager-Core Key Features

No Key Features are available at this moment for Git-Credential-Manager-Core.

Git-Credential-Manager-Core Examples and Code Snippets

No Code Snippets are available at this moment for Git-Credential-Manager-Core.

Community Discussions

Trending Discussions on Git-Credential-Manager-Core

How to store multiple PATs/passwords for use by git?

QUESTION

How to store multiple PATs/passwords for use by git?

Asked 2021-May-05 at 17:24

One password is no problem

I wanted to store my credentials "safely" for use by git so I did as instructed here. This way I don't have to input password/PAT every single time, I perform any git operation.

Install libsecret using sudo apt-get install libsecret-1-0 libsecret-1-dev
Build the "credential manager" using sudo make --directory=/usr/share/doc/git/contrib/credential/libsecret
and then configure my local git folder using git config --global credential.helper \ /usr/share/doc/git/contrib/credential/libsecret/git-credential-libsecret

Works superb.

How to do the above with many passwords?

What I don't get is how to do the same for many passwords associated with different accounts/repositories. I was suggested to use gcm core.

I tried installing gcm core as instructed here.

Download .deb package
sudo dpkg -i git-credential-manager-core configure
configure the "credential store" git config credential.credentialStore secretservice (as I use libsecret).
I removed the Credential helper pointing to /usr/share/doc/git/contrib/credential/libsecret/git-credential-libsecret from the local git config file.

It still doesn't work. When I try to push a repo, I get a garbled message with how to use git config followed by request to fill in credentials (shown here). I don't understand what I am doing! namely credential store, credential manager, secret-service and gcm core.

I looked here and here and I still don't get it.

...

ANSWER

Answered 2021-May-05 at 17:24

Any credential helper should follow the same process.

But if you have multiple account/password for the same domain (say github.com for instance), then you need to change your remote URL

Source https://stackoverflow.com/questions/67405245

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install Git-Credential-Manager-Core

You can download it from GitHub.

Support

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com. When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA. This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Find more information at: