GH2028: Adding credential support for inprocess nuget client

[TrymBeast]

Solution:

• Added NuGet.Credentials package
• Added call to DefaultCredentialServiceUtility.SetupDefaultCredentialService to configure the CredentialService

I don't know how to implement any test on this, but I've tested loading a recipe from an Azure DevOps Artifacts NuGet feed.

Fixes #2028

[microsoft-github-policy-service]

@TrymBeast please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

• (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

• (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

Contribution License Agreement

This Contribution License Agreement ( “Agreement” ) is agreed to by the party signing below ( “You” ),
and conveys certain license rights to the .NET Foundation ( “.NET Foundation” ) for Your contributions to
.NET Foundation open source projects. This Agreement is effective as of the latest signature date below.

1. Definitions.

“Code” means the computer software code, whether in human-readable or machine-executable form,
that is delivered by You to .NET Foundation under this Agreement.

“Project” means any of the projects owned or managed by .NET Foundation and offered under a license
approved by the Open Source Initiative (www.opensource.org).

“Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
Project, including but not limited to communication on electronic mailing lists, source code control
systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
discussing and improving that Project, but excluding communication that is conspicuously marked or
otherwise designated in writing by You as “Not a Submission.”

“Submission” means the Code and any other copyrightable material Submitted by You, including any
associated comments and documentation.

2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
Project. This Agreement covers any and all Submissions that You, now or in the future (except as
described in Section 4 below), Submit to any Project.

3. Originality of Work. You represent that each of Your Submissions is entirely Your
original work. Should You wish to Submit materials that are not Your original work,
You may Submit them separately to the Project if You (a) retain all copyright and
license information that was in the materials as you received them, (b) in the
description accompanying your Submission, include the phrase "Submission
containing materials of a third party:" followed by the names of the third party and any
licenses or other restrictions of which You are aware, and (c) follow any other
instructions in the Project's written guidelines concerning Submissions.

4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
Submission is made in the course of Your work for an employer or Your employer has intellectual
property rights in Your Submission by contract or applicable law, You must secure permission from Your
employer to make the Submission before signing this Agreement. In that case, the term “You” in this
Agreement will refer to You and the employer collectively. If You change employers in the future and
desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
and secure permission from the new employer before Submitting those Submissions.

5. Licenses.

a. Copyright License. You grant .NET Foundation, and those who receive the Submission directly
or indirectly from .NET Foundation, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable
license in the Submission to reproduce, prepare derivative works of, publicly display, publicly perform,
and distribute the Submission and such derivative works, and to sublicense any or all of the foregoing
rights to third parties.

b. Patent License. You grant .NET Foundation, and those who receive the Submission directly or
indirectly from .NET Foundation, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license
under Your patent claims that are necessarily infringed by the Submission or the combination of the
Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
import or otherwise dispose of the Submission alone or with the Project.

c. Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
granted by implication, exhaustion, estoppel or otherwise.

6. Representations and Warranties. You represent that You are legally entitled to grant the above
licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
have disclosed under Section 3 ). You represent that You have secured permission from Your employer to
make the Submission in cases where Your Submission is made in the course of Your work for Your
employer or Your employer has intellectual property rights in Your Submission by contract or applicable
law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
EXPRESSLY STATED IN SECTIONS 3, 4, AND 6 , THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.

7. Notice to .NET Foundation. You agree to notify .NET Foundation in writing of any facts or
circumstances of which You later become aware that would make Your representations in this
Agreement inaccurate in any respect.

8. Information about Submissions. You agree that contributions to Projects and information about
contributions may be maintained indefinitely and disclosed publicly, including Your name and other
information that You submit with Your Submission.

9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
defenses of lack of personal jurisdiction and forum non-conveniens.

10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
supersedes any and all prior agreements, understandings or communications, written or oral, between
the parties relating to the subject matter hereof. This Agreement may be assigned by .NET Foundation.

.NET Foundation dedicates this Contribution License Agreement to the public domain according to the Creative Commons CC0 1.

[gep13]

@TrymBeast in the absence of tests in the code for this, we will need to have a set of manual tests that can be ran to verify this functionality.

Can you please update the description of this PR to include all the test steps that you have done to validate this functionality. Please assume that someone reviewing this PR has no knowledge of how Azure DevOps works, and provide explicit steps on how to set things up, and how to verify functionality.

Does this change have any adverse affects on traditional authentication mechanisms, for example, standard username/password authentication within a nuget.config file?

[gep13]

@TrymBeast it would also be great to see some additional information being added to the commit message for this change. i.e. what is it doing under the hood, is there documentation around its usage that you can link to in the commit message? Are there any pieces of information that you found while investigating and implementing this, that would be good to capture for our "future" selves?

[gep13]

Oh, and since I forgot to mention this on my first comment here...

Thank you very much for your contribution to Cake! We really appreciate it!

[TrymBeast]

@gep13 Thanks for your comments, I will add information on how to test and I will link documentation on how this searches for the credential providers.
Setting the HttpHandlerResourceV3.CredentialService is how dotnet.exe, NuGet.exe, MSBuild and Visual Studio authenticates against protected package sources using external credential providers, the nuget global tool "NuGet.CommandLine.XPlat" uses exactly the DefaultCredentialServiceUtility.SetupDefaultCredentialService, so it shouldn't have any adverse effects on traditional authentication mechanisms.
Btw I also use the standard username/password on Azure Pipelines, so I better not break that.

Meanwhile, I've discovered that this is breaking the logger when using level diagnostic.
There seeems to be a log with a value like this:

[CredentialProvider.110533]Handling 'Request' 'Initialize'. Time elapsed in ms: 1 - Payload: {"ClientVersion":"6.12.1","Culture":"en-US","RequestTimeout":"00:00:30"}

Because of the curly braces it throws a FormatException: Input string was not in a correct format.

Should I implement a wrapper logger that fixes the format so in the Payload it uses the curly escape sequence? Or should I change the NuGetLogger to just print the curly braces and what's inside as is? I think the latter would be safest.

[devlead]

@TrymBeast, the correct fix would be to adjust NuGetLogger's calls to ICakeLog to pass data as the second argument with a given "{0}" format, then there's no need for escaping.

Something like

-        public void LogDebug(string data) => _log.Debug(data);
+        public void LogDebug(string data) => _log.Debug("{0}", data);

-        public void LogVerbose(string data) => _log.Debug(data);
+        public void LogVerbose(string data) => _log.Debug("{0}", data);

-        public void LogInformation(string data) => _log.Debug(data);
+        public void LogInformation(string data) => _log.Debug("{0}", data);

-        public void LogMinimal(string data) => _log.Information(data);
+        public void LogMinimal(string data) => _log.Information("{0}", data);

-        public void LogWarning(string data) => _log.Warning(data);
+        public void LogWarning(string data) => _log.Warning("{0}", data);

-        public void LogError(string data) => _log.Error(data);
+        public void LogError(string data) => _log.Error("{0}", data);

-        public void LogInformationSummary(string data) => _log.Information(data);
+        public void LogInformationSummary(string data) => _log.Information("{0}", data);

-        public void LogErrorSummary(string data) => _log.Error(data);
+        public void LogErrorSummary(string data) => _log.Error("{0}", data);

+        public void Log(LogLevel level, string data) => _log.Write(GetVerbosity(level), GetLogLevel(level), data);
-        public void Log(LogLevel level, string data) => _log.Write(GetVerbosity(level), GetLogLevel(level), "{0}", data);