Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

keyVaultCodesignCertificateName - error #1082

Closed
pzentner opened this issue May 20, 2024 · 3 comments
Closed

keyVaultCodesignCertificateName - error #1082

pzentner opened this issue May 20, 2024 · 3 comments
Labels
Need more info Please add more info about how to repro the problem

Comments

@pzentner
Copy link
Contributor

pzentner commented May 20, 2024

When switching the settings from using

codeSignCertificateUrlSecretName
codeSignCertificatePasswordSecretName

to using

keyVaultCodesignCertificateName

I am now getting the following error

Installing signing tool version 0.9.1-beta.24123.2 in C:\Users\cfbsadmin\AppData\Local\Temp\SigningTool-305010202
  The tool package could not be restored.
  Tool 'sign' failed to install. This failure may have been caused by:
  
  * You are attempting to install a preview release and did not use the --version option to specify the version.
  * A package by this name was found, but it was not a .NET tool.
  * The required NuGet feed cannot be accessed, perhaps because of an Internet connection problem.
  * You mistyped the name of the tool.
  

Would this have to do with wrong permissions to the KeyVault or is this another issue? Any insights would be appreciated.

@aholstrup1
Copy link
Contributor

Are you using self-hosted runners? I haven't be able to repro this on a GitHub runner or locally 🤔

If you're using a self-hosted runner, perhaps you need to add nuget.org as a nuget source
dotnet nuget add source https://api.nuget.org/v3/index.json --name nuget.org

@freddydk freddydk added the Need more info Please add more info about how to repro the problem label May 22, 2024
@pzentner
Copy link
Contributor Author

This might have been it. While we have a few self hosted runners, one didn't have the nuget source setup. And the run that was failing was running on that self hosted runner. We don't have anything right now to test it with, but I'll test again with the next build.

Thanks

@pzentner
Copy link
Contributor Author

I can confirm that it works after adding the nuget source. Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Need more info Please add more info about how to repro the problem
Projects
None yet
Development

No branches or pull requests

3 participants