Microsoft/git-credential-manager-for-mac-and-linux

Source: Internet
Author: User


To correct errors on your Mac:


Fatal:java.lang.Error encountered. Details:
Unexpected error
Fatal:credential Helper '!/library/java/javavirtualmachines/jdk-10.0.2.jdk/contents/home/bin/java-ddebug=false- djava.net.usesystemproxies=true-jar/usr/local/cellar/git-credential-manager/2.0.3/libexec/ Git-credential-manager-2.0.3.jar ' told us to quit






The configuration on your Mac needs to be added as follows--add-modules Java.xml.bind



The complete command should be: git config--global--replace-all credential.helper '!java --add-modules java.xml.bind-ddebug=true- djava.net.usesystemproxies=true-jar/usr/local/cellar/git-credential-manager/2.0.3/libexec/ Git-credential-manager-2.0.3.jar '


I turned on debug mode. If there are other errors. Please leave a message.




Installation Instructions


This document explains how to obtain the GIT credential Manager for Mac and Linux (gcm4ml) and what to configure Git The GCM4ML as its credential helper.


System Requirements


Great care is taken to avoid using any features of Java, would impact compatibility with Java 6. If you find a compatibility issue, please report it and provide as many details on your platform as necessary to Reprod UCE the problem.


    1. Mac OS X version 10.9.5 and up OR a recent gnu/linux distribution.
    2. Java 6 and up.
    3. Git version 1.9 and up.
How to Install


On Mac OS X, installing via Homebrew is highly recommended. On Linux, it's recommended to use Linuxbrew or a rpm-based package manager if you can.



If You can also download Git-credential-manager-2.0.3.jar somewhere safe and St with any of the managers Able, such as~/git-credential-manager/, and then follow the instructions for automatic or manual configuration.


Installing on MAC using Homebrew or on Linux using Linuxbrew (recommended)
    1. Update the Homebrew/linuxbrew formulae to make sure the latest versions:

      brew update
    2. Install the GCM4ML formula:

      brew install git-credential-manager
    3. RuninstallThe gcm4ml in mode, which would check its requirements and then update the "global" Git configuration file (The O NE in your home folder):

      git-credential-manager install
Installing on Linux using RPM (recommended)
    1. Download git-credential-manager-2.0.3-1.noarch.rpm and Copy the file somewhere locally.

    2. Download the pgp key used to sign the RPM.

    3. Import the signing key into RPM ' database:

       sudo RPM--import rpm-gpg-key.txt
    4. Verify the gcm4ml rpm:

       RPM--checksig--verbose git-credential-manager-2.0.3-1.noarch.rpm

      ... should see a line (among those there) that's equal to the following:

       V4 rsa/sha256 Signatur E, key ID ba34dbc2:ok
    5. Install the RPM:

       sudo RPM--install git-credential-manager -2.0.3-1.noarch.rpm
    6. Run the gcm4ml in install mode, which would check Its requirements and then update the ' Global ' Git configuration file (the one in your home folder):

       git-cred Ential-manager Install
Installing on MAC or Linux without a package Manager


Download Git-credential-manager-2.0.3.jar somewhere safe and stable, such as~/git-credential-manager/


Automatic Configuration (recommended)
    1. RuninstallThe gcm4ml in mode, which would check its requirements and then update the "global" Git configuration file (The O NE in your home folder):

      java -jar /home/example/git-credential-manager/git-credential-manager-2.0.3.jar install
Manual Configuration
    1. Configure thecredential.helpersetting to launch Java and the absolute path to the JAR (make sure you surround the whole value with ' Single quotes '):

      git config --global credential.helper ‘!java -Ddebug=false -Djava.net.useSystemProxies=true -jar /home/example/git-credential-manager/git-credential-manager-2.0.3.jar‘
How to enable alternate credential storage


On Linux, the GCM4ML stores credentials in the GNOME Keyring. If GNOME Keyring is unavailable for your Linux distribution, or you are running the gcm4ml via a secure Shell (SSH) Sessio N, a Git setting can be used to opt into storing credentials unencrypted in a file under your home directory where Presuma Bly only and root has read access.



To enable fallback storage of credentials in the this file, run this Git configuration command:



git config --global credential.canFallBackToInsecureStore true



With this setting, the gcm4ml would fallback to storing your credentials in this file:



~/.VSTeamServicesAuthPlugin/insecureStore.xml


How to enable (or disable) debug mode


Debug mode would turn on tracing and assertions, producing a lot of output tostderr. Only turn the temporarily, when trying to isolate a defect.


Automatic Configuration (recommended)
    1. Run the gcm4ml in mode with the propertyinstalldebugset totrue(or tofalsedisable):

      java -Ddebug=true -jar /home/example/git-credential-manager/git-credential-manager-2.0.3.jar install
Manual Configuration
    1. Retrieve the value of thecredential.helperconfiguration:

      git config --global --get credential.helper git-credential-manager

      ... it should look like this:

      !java -Ddebug=false -Djava.net.useSystemProxies=true -jar /home/example/git-credential-manager/git-credential-manager-2.0.3.jar
    2. Set a new value for thecredential.helperconfiguration (essentially repeating the manual configuration installation step, be ing careful with quoting and spaces), changing the value of thedebug"totrue" (or tofalsedisable).

How to configure the proxy server


If your network does not allow a direct connection to remote hosts, you can configure the GCM4ML to perform requests throu GH a Web proxy.


Automatic Configuration (recommended)


If you is running Gnome 2.x or greater, you can configure the proxy settings using the GUI and the gcm4ml would use those Settings thanks to a JVM feature that's activated by setting the system property to (this is now dojava.net.useSystemProxiestrueAutomati Cally when running the gcm4ml ininstallmode).


Manual Configuration


If it ' s not possible to use the automatic Proxy server configuration, you must set the appropriate networking properties. Aside from SOCKS proxy servers, which can has their credentials specified through specific properties, authenticated ProX Y servers is currently not supported.


  1. Retrieve the value of the credential.helper configuration:

     git config-- Global--get credential.helper git-credential-manager

    ... it should look like this:

     !java -ddebug=false-djava.net.usesystemproxies=true-jar/home/example/git-credential-manager/ Git-credential-manager-2.0.3.jar
  2. Set a new value for thecredential.helperconfiguration (essentially repeating the manual configuration installation step, be ing careful with quoting and spaces), adding the appropriate properties. For example, if you have a proxy server so can do HTTP and HTTPS, running on the host192.168.0.117, listening on port8123, th En you would run the following (notice there's a pair of properties for HTTP and one for HTTPS).

    git config --global credential.helper ‘!java -Ddebug=false -Dhttp.proxyHost=192.168.0.117 -Dhttp.proxyPort=8123 -Dhttps.proxyHost=192.168.0.117 -Dhttps.proxyPort=8123 -jar /home/example/git-credential-manager/git-credential-manager-2.0.3.jar‘
How to remove or uninstall


We are sad to see you go! Give us some feedback on how we could do better next time.


Uninstall from Mac using Homebrew or Linux using Linuxbrew
    1. RununinstallThe gcm4ml in mode, which'll update the "global" Git configuration file (the one in your home folder):

      git-credential-manager uninstall
    2. Uninstall the Git-credential-manager package with Homebrew/linuxbrew:

      brew uninstall git-credential-manager
    3. Archive theinsecureStore.xmlfile from thegit-credential-managersub-folder under your HOME folder.

Uninstall from Linux using RPM
    1. RununinstallThe gcm4ml in mode, which'll update the "global" Git configuration file (the one in your home folder):

      git-credential-manager uninstall
    2. Uninstall the Git-credential-manager package with RPM:

      sudo rpm --erase git-credential-manager-2.0.3-1.noarch
    3. Archive theinsecureStore.xmlfile from thegit-credential-managersub-folder under your HOME folder.

Automatic configuration removal (recommended)
    1. Retrieve the value of thecredential.helperconfiguration:

      git config --global --get credential.helper git-credential-manager
    2. RununinstallThe gcm4ml in mode, which'll update the "global" Git configuration file (the one in your home folder):

      java -jar /home/example/git-credential-manager/git-credential-manager-2.0.3.jar uninstall
    3. The value retrieved in Step 1 contained the path to the JAR. You can go to delete that JAR.

    4. Archive theinsecureStore.xmlfile from thegit-credential-managersub-folder under your HOME folder.

Manual Configuration Removal
    1. Retrieve the value of thecredential.helperconfiguration:

      git config --global --get credential.helper git-credential-manager
    2. Delete the value of thecredential.helperconfiguration:

      git config --global --unset credential.helper git-credential-manager
    3. The value retrieved in Step 1 contained the path to the JAR. You can go to delete that JAR.

    4. Archive theinsecureStore.xmlfile from thegit-credential-managersub-folder under your HOME folder.





Microsoft/git-credential-manager-for-mac-and-linux


Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.