LibGit2Sharp.LibGit2SharpException: failed to parse supported auth schemes: The operation identifier is not valid

Open
#2,048 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp, git, github
Domain
authentication

Research direction

Start with the shown Commands.Pull call and its FetchOptions/CredentialsHandler configuration in LibGit2Sharp 0.26.2, then reproduce the authentication failure on Windows 10 against GitHub. Compare the supported authentication schemes involved and verify that a pull using the reported credentials completes without the parsing error.

Written by the indexing model from the issue text.

Description

// code start
LibGit2Sharp.PullOptions options = new LibGit2Sharp.PullOptions();
options.FetchOptions = new FetchOptions();
options.FetchOptions.CredentialsProvider = new CredentialsHandler(
(url, usernameFromUrl, types) =>
new UsernamePasswordCredentials()
{
Username = _gitCredsUser,
Password = _gitCredsPassword
});

        // User information to create a merge commit
        var signature = new LibGit2Sharp.Signature(
            new Identity(_gitUsername, _gitEmail), DateTimeOffset.Now);

        // Pull
        Commands.Pull(repo, signature, options);

// end code

I am using LibGit2Sharp dll of 0.26.0.0, from last few days I am getting "failed to parse supported auth scheme" error while doing git pull. My git repository is on GITHUB. I am sure there might security related changes done on github side. that's why this error come.

Reproduction steps
Expected behavior

git pull should work without error.

Actual behavior
Version of LibGit2Sharp (release number or SHA1)

0.26.2

Operating system(s) tested; .NET runtime tested

windows 10

Dominant language
C#
Stars
3.5k
Forks
925
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from libgit2/libgit2sharp

All issues in libgit2/libgit2sharp

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.