NuGet/Home

Add CLI option for `disableTLSCertificateValidation` property

Open

#14,061 opened on Jan 22, 2025

View on GitHub
 (1 comment) (2 reactions) (0 assignees)HTML (292 forks)batch import
Priority:3Type:Featurehelp wanted

Repository metrics

Stars
 (1,459 stars)
PR merge metrics
 (Avg merge 464d 23h) (1 merged PR in 30d)

Description

NuGet Product(s) Involved

NuGet.exe, dotnet.exe

The Elevator Pitch

Some time ago the property disableTLSCertificateValidation was added to nuget config sources (#12996, #13023, #13478). But this property is not represented by any CLI option so it needs to be added manually in the NuGet config file.

Similar to how allowInsecureConnections has a CLI option, I would suggest adding a CLI option to set the disableTLSCertificateValidation when using nuget sources add and dotnet nuget add source.

Additional Context and Details

No response

Contributor guide

Research direction
Study how the existing `allowInsecureConnections` CLI option is implemented for `nuget sources add` and `dotnet nuget add source`, then replicate the same pattern for `disableTLSCertificateValidation`.
Tech stack
csharp
Domain
cli
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitC#NuGet CLI concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60