Expectation of on-prem Bitbucket with authentication working? #1404
Description
I've been battling this off and on for a year or two at this point. I thought I had things solved, but I'm now concerned that either a recent VS update broke what I thought was working, or maybe it never was working at all. Shortest version I can manage: We have multiple internal NuGet packages hosted on an internal server. They're configured to link back to the repos using SourceLink configuration. The source control server is Bitbucket Data Center, and requires login to access the code. With just that much, I today found this comment, which makes me worry that I'm already barking up a dead tree: #788 (comment)
From the several related issues I've looked at, I'll add the following details:
- The Source Link URL does include the REST API format (https://bitbucket.domain/rest/api/1.0/projects/PROJ/repos/REPO/raw/src/FILE.cs?at=HASH)
- There is a "Source Link Authentication Failed" landing page which provides options to "Authenticate", "Decompile", "Browse", or "View"; pressing "Authenticate" does nothing whatsoever
- Request is failing with 401 Unauthorized
- Fiddler using HTTPS inspection shows that the VS requests are NOT being sent with any Authorization header whatsoever
- Git Credential Manager fallback is enabled
- I have confirmed on the command line that using git with the same https: server prefix works as expected using its saved credentials
I will also note that we do use Resharper, and it provides its own SourceLink integration for scenarios other than debug step into; notably you can control-click on an item, and navigate to its definition through the SourceLink information. That part is working fine, so it really seems like the problem is just that I can't get VS to use any authentication information in this scenario, whether directly or via GCM.
I had seen some older posts mentioning using Web Credentials in the Windows Credential Manager, but it seems that there isn't a way to store something there other than Internet Explorer, or perhaps earlier versions of Edge. Current Edge seems to prefer a Microsoft Wallet concept.
Anything I've missed?