PowerShellGet won't search my (artifactory) repository for modules

[godefroi]

Steps to reproduce

# get-psrepository                                                                                                      
Name                      InstallationPolicy   SourceLocation
----                      ------------------   --------------
PSGallery                 Untrusted            https://www.powershellgallery.com/api/v2
BlahBlahPSModules         Trusted              https://artifactory.blahblah.com/api/nuget/psmodules-local

# find-module -Credential $cr1 -verbose -Name 'notreallyanamethatwillbefound'                                           VERBOSE: Repository details, Name = 'PSGallery', Location = 'https://www.powershellgallery.com/api/v2'; IsTrusted = 'False'; IsRegistered = 'True'.
VERBOSE: Repository details, Name = 'PSGallery', Location = 'https://www.powershellgallery.com/api/v2'; IsTrusted = 'False'; IsRegistered = 'True'.
VERBOSE: Using the provider 'PowerShellGet' for searching packages.
VERBOSE: The -Repository parameter was not specified.  PowerShellGet will use all of the registered repositories.
VERBOSE: Getting the provider object for the PackageManagement Provider 'NuGet'.
VERBOSE: The specified Location is 'https://www.powershellgallery.com/api/v2' and PackageManagementProvider is 'NuGet'.
VERBOSE: Searching repository 'https://www.powershellgallery.com/api/v2/FindPackagesById()?id='notreallyanamethatwillbefound'' for ''.
VERBOSE: Total package yield:'0' for the specified package 'notreallyanamethatwillbefound'.
VERBOSE: Getting the provider object for the PackageManagement Provider 'NuGet'.
VERBOSE: The specified Location is 'https://artifactory.blahblah.com/api/nuget/psmodules-local' and PackageManagementProvider is 'NuGet'.
WARNING: Unable to resolve package source 'https://artifactory.blahblah.com/api/nuget/psmodules-local'.
VERBOSE: Total package yield:'0' for the specified package 'notreallyanamethatwillbefound'.
PackageManagement\Find-Package : No match was found for the specified search criteria and module name 'notreallyanamethatwillbefound'. Try Get-PSRepository to see all available registered module repositories.
At C:\Users\my.name\Documents\PowerShell\Modules\PowerShellGet\2.2.1\PSModule.psm1:8871 char:9
+         PackageManagement\Find-Package @PSBoundParameters | Microsoft ...
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : ObjectNotFound: (Microsoft.PowerShel\u2026Cmdlets.FindPackage:FindPackage) [Find-Package], Exception
+ FullyQualifiedErrorId : NoMatchFoundForCriteria,Microsoft.PowerShell.PackageManagement.Cmdlets.FindPackage

Expected behavior

My custom repository will be searched for the requested module. It is important to note that according to the Artifactory log, no requests are ever made to the server.

Actual behavior

My custom repository isn't searched for the requested module (because the package source couldn't be resolved, whatever that means).

Environment data

# $psversiontable                                                                                                       
Name                           Value
----                           -----
PSVersion                      6.2.2
PSEdition                      Core
GitCommitId                    6.2.2
OS                             Microsoft Windows 10.0.18362
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

#  Get-Module -ListAvailable PowerShellGet,PackageManagement                                                            

    Directory: C:\Users\my.name\Documents\PowerShell\Modules

ModuleType Version    Name                                PSEdition ExportedCommands
---------- -------    ----                                --------- ----------------
Script     1.4.4      PackageManagement                   Desk      {Find-Package, Get-Package, Get-PackageProvider, G…
Script     2.2.1      PowerShellGet                       Desk      {Find-Command, Find-DSCResource, Find-Module, Find…

    Directory: C:\program files\powershell\6\Modules

ModuleType Version    Name                                PSEdition ExportedCommands
---------- -------    ----                                --------- ----------------
Script     1.3.2      PackageManagement                   Desk      {Find-Package, Get-Package, Get-PackageProvider, G…
Script     2.1.3      PowerShellGet                       Desk      {Find-Command, Find-DSCResource, Find-Module, Find…

# Get-PackageProvider -ListAvailable                                                                                    
Name                     Version          DynamicOptions
----                     -------          --------------
NuGet                    3.0.0.1          Destination, ExcludeVersion, Scope, SkipDependencies, Headers, FilterOnTag, …
PowerShellGet            2.2.1.0          PackageManagementProvider, Type, Scope, AllowClobber, SkipPublisherCheck, In…
PowerShellGet            2.1.3.0

[DannyArr]

Is the user in $cr1 an internal Artifactory user or is Artifactory authenticating with SAML? I had this same problem when I attempted to supply credentials only to then realise we were using SAML authentication. When using an internally generated user, it worked fine.

[iesen]

I tried this and got the same error. (using crowd sso integration)

I also tried allowing anonymous access to the repository, successfully registered without specifiying credentials, but no request is made to artifactory server while searching for modules.

Error is same:
WARNING: Unable to resolve package source 'https://myrepo.com/artifactory/api/nuget/my-powershell'.

[RandomNoun7]

I'm experiencing the same error.

I'm on powershell 7 preview with PowerShellGet 2.2.3

I also have wireshark installed and I can confirm that when Find-Module returns a warning that it can't resolve the package source, it has never tried to connect to the server.

C:\
> find-module -Repository artifactory -verbose
VERBOSE: Repository details, Name = 'artifactory', Location = 'https://artifactory.test/artifactory/api/nuget/nuget-local'; IsTrusted = 'True'; IsRegistered = 'True'.
VERBOSE: Using the provider 'PowerShellGet' for searching packages.
VERBOSE: Using the specified source names : 'artifactory'.
VERBOSE: Getting the provider object for the PackageManagement Provider 'NuGet'.
VERBOSE: The specified Location is 'https://artifactory.test/artifactory/api/nuget/nuget-local' and PackageManagementProvider is 'NuGet'.
VERBOSE: Total package yield:'0' for the specified package ''.
WARNING: Unable to resolve package source 'https://artifactory.test/artifactory/api/nuget/nuget-local'.
VERBOSE: Total package yield:'0' for the specified package ''.
C:\
>

The nuget repo on this instance is configured for anonymous access, and I'v tried running Find-Module passing the -Credential parameter as well using a local Artifactory user and API key, but in all cases, the behavior is that same, which is that the Artifactory server is never actually contacted before the module declares the package source cannot be resolved.

[godefroi]

@DannyArr the credential in $cr1 is indeed a SAML-authenticated credential. I don't know why that matters, because no request is made to Artifactory. When NuGet tries to contact Artifactory and Artifactory requests authentication, that request is logged. In this case, there's nothing in the Artifactory log.

[PDQDakota]

I'm encountering this same issue for a local user, no OAuth or SAML is used on the Artifactory instance. I see the error Unable to resolve package source but I can access the URL with no issues using Invoke-WebRequest.

$PSVersionTable

Name                           Value
----                           -----
PSVersion                      7.0.0-rc.2
PSEdition                      Core
GitCommitId                    7.0.0-rc.2
OS                             Microsoft Windows 10.0.18363
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Get-Module -ListAvailable PowerShellGet,PackageManagement


    Directory: C:\program files\powershell\7-preview\Modules

ModuleType Version    PreRelease Name                                PSEdition ExportedCommands
---------- -------    ---------- ----                                --------- ----------------
Script     1.4.6                 PackageManagement                   Desk      {Find-Package, Get-Package, Get-Package…
Script     2.2.3                 PowerShellGet                       Desk      {Find-Command, Find-DSCResource, Find-M…

    Directory: C:\Program Files\WindowsPowerShell\Modules

ModuleType Version    PreRelease Name                                PSEdition ExportedCommands
---------- -------    ---------- ----                                --------- ----------------
Script     1.4.2                 PackageManagement                   Desk      {Find-Package, Get-Package, Get-Package…
Binary     1.0.0.1               PackageManagement                   Desk      {Find-Package, Get-Package, Get-Package…
Script     2.1.5                 PowerShellGet                       Desk      {Find-Command, Find-DSCResource, Find-M…
Script     1.0.0.1               PowerShellGet                       Desk      {Install-Module, Find-Module, Save-Modu…

Get-PackageProvider -ListAvailable

Name                     Version          DynamicOptions
----                     -------          --------------
NuGet                    3.0.0.1          Destination, ExcludeVersion, Scope, SkipDependencies, Headers, FilterOnTag, …
PowerShellGet            2.2.3.0          PackageManagementProvider, Type, Scope, AllowClobber, SkipPublisherCheck, In…
PowerShellGet            2.1.5.0
PowerShellGet            1.0.0.1

[alerickson]

@PDQDakota Can you try unregistering and then registering the repository, and then run -verbose -debug with the specific command you were running that generated the error?

[PDQDakota]

@alerickson I was able to find a work around from another issue in another project. You must register the package source with Register-PackageSource -SkipValidate prior to registering the PS repository for the process to work. After that I can work with the Artifactory repo without issue. Something about the validation process seems broken but I have no idea how to verify that.

[alerickson]

@PDQDakota thanks for the info! It definitely sounds like there's something broken with PackageManagement's validation process when registering sources. We're working on a new version of PowerShellGet, and will be sure to make interacting with the Artifactory repo a smooth experience. Are there any other package repositories you use or is it primarily Artifactory?

[PDQDakota]

@alerickson It's primarily Artifactory where I'm at. We're moving off a file share backed repo.

[pcgeek86]

I'm having the same problem with PowerShell 7 on Windows 10 with MyGet.org.

[alerickson]

@pcgeek86 are you able to use the workaround Register-PackageSource -SkipValidate

[pcgeek86]

@alerickson I tried that approach, and it isn't helping solve the problem. I still get the same result.