Hi @jw , This doesn't seem like a a trivial change, due to the way those pages work, so I'll add it to the "wishlist" - we've got a lot of other ProGet 2025 roadmap stuff prioritized ahead for the time being :) Cheers, Alana

Hi @dan-brown_0128 , It doesn't look like there's been much interest in this so far (we haven't heard any othe rrequests for it), but I wanted to mention that Terraform repositories are planned and something we hope to accomplish in the coming months. Cheers, Alana

@sebastian said in Problem with PGV-22381O7 (tree-kill1.2.2 incorrectly flagged vulnerable): There should be a special treatment for withdrawn vulnerabilities within ProGet. Maybe not deleting them (because I'm pretty sure there will be cases where I will be looking at a package and think "I swear this one had a vulnerability, but now I can't find it?" ), but maybe auto-assess a special status to it. That's what we were worried about as well, having them dissapear. Perhaps we just delete ones without assessments, and if you set a withdrawn vulnerability unassessed, it gets deleted

@carl-westman_8110 very happy to hear it, thanks for the kind words :)

Hi @husterk_2844 , I'm afraid we're at a loss here; no one else has reported any kind of errors like this, and I can't imagine what would even cause such a problem. I suspect there is something off about your Docker Compose file? That seems to be the only thing different than the basic setup. I would just try to re-follow the basic instructions we posted: https://docs.inedo.com/docs/installation/linux/docker-guide That's what we use to test, and lots of users install and upgrade without a problem. Thanks, Steve

Hi @forbzie22_0253, The easiest solution is to change both the "ProGet Service" (INEDOPROGETSVC) service and the "World Wide Web Publishing Service" (W3svc) to Automatic (Delayed Start). This typically allows SQL Server to start before IIS and the ProGet Service start. Thanks, Dan

Hi @atripp thank you very much, downloading the latest version solved my issue. Best, Caterina

Hi @forbzie22_0253, There's no Windows event logged, but once the /heath page is reachable, then the application is ready. If you're using SQL Server and IIS on the same box, then both of those must first load before ProGet can start. Thanks, Steve

Great thanks for confirming Dean

Hi @v-makkenze_6348, I was able to identify the issue, PG-2778, and will have this fixed in the next maintenance release of ProGet. Thanks, Rich

Hi @steviecoaster , The Native API can be a little finicky, especially since you can invoke with JSON, forum-encoded values, querystring, and I think even XML. But it sounds like you're on the right track. Let me share the C# code that ProGet uses to set the password: using (var rfc2898 = new Rfc2898DeriveBytes(password ?? string.Empty, 10, 10000, HashAlgorithmName.SHA1)) { var bytes = rfc2898.GetBytes(20); DB.Users_SetPassword(userName, bytes, rfc2898.Salt); } ... it looks a little different than the code you're using, so hopefully that will help! -- Dean

Thanks @russell_8876! I've gone ahead and released pgutil 1.1.6 with a fix for this. Give it a try and let us know if it's still not working. -Greg

Hi @noam-linux-2022_8869 , Here is documentation on how to enable HTTPS in our products on Windows and Linux: https://docs.inedo.com/docs/installation/installing-on-iis/installation-windows-https-support https://docs.inedo.com/docs/installation/linux/https-support -- Dean

@dean-houston thanks for that info! I think that'll do nicely. I'll have to play around with it to be sure, but from what I can tell it looks straightforward to implement. Thank you!

@steviecoaster great, thanks for sharing! I added this to our documentation (https://github.com/Inedo/inedo-docs/pull/253), but apparently I don't have ability to merge PRs in that repo so it'll go live sometime later I'm sure

Hi @stevedennis Let's continue this thread here: EDO-10681

I did a "Pull to ProGet" and ran analyze again and now the warning is gone.

Thank you for the information Alana I appreciate the details!

Hi @j-d-koning_0111, Just wanted to check in if PG-2738 fixed your issue. We have also been working with another customer that has had similar issues. We determined this was related to setting to Map groups to SAML groups setting. If you have this enabled and do not have any groups claims sent, it was causing the error you saw above. This last issue, PG-2745, will be released in the next maintenance release. As a work around, make sure you have your SAML provider configured to send groups claims. Thanks, Rich