You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is Your Feature Request Related To A Problem? Please describe.
In the Chocolatey CLI codebase we have code that makes it possible to use a Certificate and Certificate password when authenticating with Chocolatey feed sources.
At the moment we do not have any tests for this functionality, and AFAIK no way to test whether this functionality works as intended.
Describe The Solution. Why is it needed?
We need to look into how to implement E2E tests when authenticating to Chocolatey feed sources that makes use of certificate authentication, both if they are configured as global sources or passed in during install/upgrade/list/info commands.
Additional Context.
It is possible that this functionality do not exist in later version of the NuGet codebase, meaning once we update the references used, we do not have this functionality anymore.
This also needs to be looked into, and if determined if we will not support the functionality in the future it will need to be deprecated instead of adding tests for this.
Related Issues
N/A.
The text was updated successfully, but these errors were encountered:
Is Your Feature Request Related To A Problem? Please describe.
In the Chocolatey CLI codebase we have code that makes it possible to use a Certificate and Certificate password when authenticating with Chocolatey feed sources.
At the moment we do not have any tests for this functionality, and AFAIK no way to test whether this functionality works as intended.
Describe The Solution. Why is it needed?
We need to look into how to implement E2E tests when authenticating to Chocolatey feed sources that makes use of certificate authentication, both if they are configured as global sources or passed in during install/upgrade/list/info commands.
Additional Context.
It is possible that this functionality do not exist in later version of the NuGet codebase, meaning once we update the references used, we do not have this functionality anymore.
This also needs to be looked into, and if determined if we will not support the functionality in the future it will need to be deprecated instead of adding tests for this.
Related Issues
N/A.
The text was updated successfully, but these errors were encountered: