We've narrowed down the issue. It seems that the service user that ProGet is running with cannot see all the members of the LDAP groups. This can be fixed by changing the user to one that can see all members of the LDAP groups through this process: https://inedo.com/support/kb/1077/configuring-your-inedo-product-to-run-as-a-windows-domain-account

It was my reverse proxy (apache). I had to set AllowEncodedSlashes to On. Problem solved.

I see, that's an interesting idea. It seems like some sort of auto-generated documentation of sorts? I don't know if ProGet is the place for that data, but we don't have a feature to store such doumentation at this time. So, maybe you could auto-post it a documentation wiki of sorts and use the "Project URL" property to link to it?

ProGet does not have a "pin version" feature, though it has been requested in the past. Instead, you may just want to create an "archived" feed, and promote packages you want to "pin" to that.

Sure, here they are: ProGet License Agreement Security and Access Controls

I'm afraid we don't have an ETA at this time; we're currently focusing on Debian and PyPi feeds for the moment, and hope to move towards Composer later.

Hi @ReginaldD, did you manage to bulk-delete packages from your server using inedo API? Cheers,

Hello; just to let you know, the Inedo ProGet Plugin for Jenkins has been updated, and may work better. Have you had an progress onthis otherwise?

Well maybe it could be useful to at least integrate into the configuration of the application. This would be a good option if you'd choose that you don't want it to be found in online search results.

You'll want to push a "combined" symbols package to http://🚫/nuget/feed-name - the symbols endpoint is for downloading extracted symbols only. Check out the guide we have at Symbol and Source Server docs for more info

To resolve this issue, I disabled Anonymous Authentication for the ProGet website in IIS (leaving just Windows Authentication enabled) and restarted all services. I tried this previously to no avail but for some reason it is working fine now.

This is available in a standard installation of the latest version under Manage Feed: I'll check out the source code now. Thanks.

Hello Tobias, PG-1270 will make local packages appear before remote packages in the list, as well as making connector packages appear in the same order that they would appear in the connector.

Thank you so much for your answer and the confirmation for a futur support of Black Duck. I will contact you once we are ready to work with you (ProGet solution is in planification and installation phasis here). Thanks.

Thanks Dean. The image is available now.

You shouldn't be receiving a "401" error from the public npmjs registry. If you are, my guess is that you have some sort of proxy or firewall selectively blocking outgoing access to certain queries to the registry. Once you resolve that, then p[roblem #2 will also be resolved.

yes, after subscribing to one of our vulnerability providers like Sona OSSIndex or Whitesource (more coming later).

Not really I'm afraid... "Pulling with dependencies" would require implementing every dependency resolution algorithm of every version of every client, including the non-deterministic dependency resolution used by the npm client, and then somehow letting you select the algorithm version and the additional contet required by the algorithm (such as .net framework target versinon).