Download the new for windows ProFind1/31/2024 T11:52:19.3735506Z WARNING: Unable to find the architecture of the installed Google Chrome application T11:52:19.3715412Z WARNING: No registry key found based on 'Google Chrome' T11:52:19.3701258Z GoogleChrome package files install completed. T11:52:19.3097259Z By installing, you accept licenses for the packages. T11:52:19.2789067Z #& 'C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe' -NoLogo -NoProfile -NonInteractive T11:52:13.9848909Z PSSession created for Machines:'MYSERVER' T11:52:12.5329559Z Description : Execute PowerShell scripts on remote machines using PSSession and Invoke-Command for remoting T11:52:12.5329414Z Task : PowerShell on target machines Terminal/Emulator: Azure DevOps Pipelines / PowerShell.Chocolatey Licensed Extension version:. IIS: Windows Authentication enabled (anything else disabled within IIS's Authentication).ProGet: Windows Integrated Authentication enabled.SSL enabled with cert issued by internal CA.We're using ProGet in combination with Microsoft IIS: UserPassword: '$(PASSWORD) ' InlineScript: |Ĭhoco install $InstallPackage -f -u " $ (UserName ) " -p " $ (PASSWORD ) "ĬommunicationProtocol: 'Http ' What is Expected?ĭownload and installation of nupkg-files with dependencies on ProGet asset feeds, having windows authentication enabled, are working fine in ADO pipelines, too. task: PowerShellOnTargetMachines Install required packages The edited url64bit value in chocolateyInstall.ps1: The nupkg gets downloaded but the download of the installer from the asset feed fails with HTTP 401 - Unauthorized. We also use Azure DevOps pipelines to get our stuff automated and that's where it comes to issues though we're using windows integrated authentication, too: PowerShell-session everything is working fine with those packages:Ĭhocolatey first downloads the nupkg-file, then the installer itself from ProGets asset feeds. Using chocolatey within an authenticated user session resp. ProGet and IIS have windows integrated authentication enabled. The next step is to re-create the package by editing the download url of the installer in chocolateyInstall.ps1. Since we're not allowed to use external sources on client systems, we are downloading the installers from official sources then uploading it to ProGets assets feed. We are using packages with external dependencies like this one: I have verified this issue is not security related.I have verified this is not an issue for a specific package.I have verified no other issues exist related to my problem.I have verified this is the correct repository for opening this issue.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |