"remote authentication required but no callback set" in pull after upgrading from 0.28 to 0.29

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
azure, csharp, git
Domain
authentication, backend, operating-systems

Research direction

Start with the Pull call and the error path in Core/Ensure.cs at line 154, then compare the authentication behavior between versions 0.28 and 0.29. Review related issues #2065 and #2087 and reproduce against the internal Azure DevOps server on Windows with .NET 4.8. Done means the shown pull succeeds using Windows authentication without the missing-callback exception.

Written by the indexing model from the issue text.

Description

@bording we get the error "remote authentication required but no callback set" after upgrading from 0.28 to 0.29 when connecting to a company internal azure devops server.

This works great with the old version using windows authentication.

Reproduction steps
  • connect to a company internal azure devops server via windows authentication
      Signature signature = GetSignature();
      PullOptions pullOptions = new()
      {
        MergeOptions = new() { FileConflictStrategy = CheckoutFileConflictStrategy.Theirs }
      };
      MergeResult mergeResult = Commands.Pull(Repository, signature, pullOptions);
Expected behavior

Success

Actual behavior

LibGit2Sharp.LibGit2SharpException
HResult=0x80131500
Message=remote authentication required but no callback set
Source=LibGit2Sharp
StackTrace:
at LibGit2Sharp.Core.Ensure.HandleError(Int32 result) in /_/LibGit2Sharp/Core/Ensure.cs:line 154

Version of LibGit2Sharp (release number or SHA1)

0.29

Operating system(s) tested; .NET runtime tested

Windows 11, .NET 4.8

Seems to be related to #2065 and #2087

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.