@stevedennis This is perfect. I greatly appreciate this, Steve.
davidroberts63
@davidroberts63
Best posts made by davidroberts63
Latest posts made by davidroberts63
-
RE: ProGet product version api
-
ProGet product version api
Is there an api call that would return the current version of ProGet I'm running? And is there an api call against indeo.com that would return the available versions and their release date?
I'm looking to build a self-updating dashboard of our pipeline tools. To help us stay on track with what version is in live use and staging, versus the lastest available and how old each are.
-
RE: Assets folder upload being denied
Haha, I missed it by one minor verison. :-D
Sounds good. Thanks for the quick response. Means I get to test my scripted upgrade process. :-D
Have a good one.
-
Assets folder upload being denied
We have an assets folder with an LDAP group assigned 'NuGet Uploaders' permissions. The users can create directories but get the following exception message immediately when clicking 'Add Assets':
Inedo.ProGet.WebApplication.SecuredTaskDeniedException: [USERNAME-HERE] is not permitted to perform the Feeds_AddPackage task for the current scope.
I've also tried granting the users all permissions except administrator as well as assigning the individual them-self as opposed to a group. But neither approach seem to allow the user to upload a file. I, as the proget administrator, can successfully upload a file to the asset directory. I've checked the tasks given the various permissions I've tried. 'Add Packages' is part of the permissions involved.
Are there any recomendations on how to get the user the ability to upload a file to the asset directory?
Product: ProGet
Version: 4.8.2 -
RE: Windows Authentication but not on Feeds
Somewhat similar to the post you've read already, but I've provided an answer to this kind of problem before:
https://inedo.com/support/questions/7990
Basically it's setting up two IIS sites, one with Windows auth the other with Basic Auth (or anonymous if you want). One instance of ProGet, but two ways to get to it.
We've been successfully using ProGet with both Windows Auth (for .NET nugets) and Basic Auth (for npm and docker) for about a year now, with the configuration described in the post I referenced.
David
-
RE: Proget feed access for anonymous not working
Jon I've run into the same issue before dealing with the npm feeds. I ended up hosting the proget site twice in IIS under different hostnames.
In IIS we have two websites:
- Windows Auth enabled
- Forms Auth disabled
- Anonymous Auth disabled
formsauth-proget.mycompany.com
- Anonymous Auth enabled
Both sites use the same physical path of your proget installation. The host name in the binding must be different though. That is so IIS knows which way to go, the website with Windows auth or the site with the anonymous auth.
We've been using this for several months with no problems. I hope it helps in your situation.
Please note, I do not work for ProGet, I'm a fellow customer offering assistance.
-
RE: Trying to switch to Active Directory fails
Gordon,
Have you made any changes to the web.config in the Proget website? Also, can you go through some of the IIS settings as well? Version of IIS, authentication modes that are enabled. Also, take a look at the providers for 'Windows Authentication' and what does that list look like?
I did a little digging and found a somewhat similar situation on a completely different product (SiteFinity). In that forum discussion there is talk about changes in the web.config causing the issue. Thus why I'm asking about what your proget installation web.config looks like.
Please note, I do not work for ProGet, I'm a fellow customer offering assistance.
-
RE: ProGet Support of NuGet V3 Feed
I'm not sure if you can use the V3 url in a ProGet connector. I believe I've tried and it wouldn't' work. I defer to ProGet employee's to confirm that.
However, that won't affect your developers using VS 2017. They can connect to ProGet with the url that you provided earlier and they will see the same results. I have about 80 developers across VS 2013, VS 2015 and VS 2017 all using the same ProGet url, and all are working fine with the nuget.org connector in ProGet.
Please note, I do not work for ProGet. I'm a fellow customer offering assistance.
-
RE: Uploading packages from jenkins to ProGet
As an alternative choice you can use Powershell for this. Add a 'Windows Powershell' step (be sure to install that Jenkins plugin first):
DIR -Recurse -File -Filter "*.nupkg" | @{
& nuget.exe push $_.FullName -Source https://urltoyourproget/nuget/feedname
}You will also need to ensure you have the nuget.exe command line executable available to the Jenkins node running.
Please note, I do not work for ProGet, I'm a fellow customer offering assistance.