Hi @kc_2466 , Thanks for the report; we'll get this fixed in the next maintenance release (this week) via PG-3064 Thanks, Steve

Hi @kc_2466 , Understood, that was the same reason given before. Our products' AD/LDAP integration works different than JIRA/TeamCity (live lookup vs sync) so it's just not that simple. We're not willing to add complexity to work-around "dumb" organizational policies -- what you described is the whole point of AD/LDAP (centrally administered access). It's possible to delegate group administration in AD, but if they don't want to do that... I guess they are okay with you just creating less-secure built-in users until they get around to completing their tickets ;) Thanks, Alana

Hi @kc_2466 , nice catch! We'll get it fixed via PG-3060 in the next maintenance release!

@kc_2466 thanks for the suggestions, we'll also get this in a future maintenance release via PG-3067 ... should be trivial!

Hi @kc_2466 , Those should not be displayed to non-feed admins; we'll clear that up with PG-3050 in the next maintenance release. In the meantime, I suppose you could just click the "X" for them ;) -- Dean

Hi @kc_2466 , We'll get this fixed via PG-3050 as well; the button should be shown to non-admins -- Dean

Hi @kc_2466 , Thanks! We'll add this via PG-3066 in an upcoming maintenance release, hopefully later this week if it's as trivial as it seems :) Thanks, Steve

Hi @kc_2466 , We'll Add support for LC_TIME environment variable & user setting via PG-3054 in an upcoming maintenance release -- p[robably not this week's, but in the next or following. Thanks, Alana

Nice idea! That was pretty trivial to add in there, and will be in the next maintenance release via PG-3038: [image: 1751500114153-0862e122-a88d-49ef-ad76-204f40afaec5-image.png]

That's the intended/expected behavior of repackage. The use case is CI/CD workflows, so you would do something like: Create w.x.y-ci.z Repackage to w.x.y-rc.z Repackage to w.x.y Retention policies would then clear out old -ci and -rc packages. I believe that display bug has been fixed in ProGet 2025; I remember seeing it listed as a bug discovered during testing. But in any case, it's in the package history as you can see.

Yes - they are "self-connectors". We've now bought an externally signed certificate, as it seemed like the simpler option (the in house cert option was causing other issues too). However that hasn't resolved the issue with the self-connectors. However, I've just edited those connectors manually to use http rather than https, and that has resolved the issue. But It's not really an ideal solution. So it looks like from inside the docker container it's still not "trusting" the externally signed certificate.

Hi @kc_2466 , The message "Feed-scoped Privileges are not available in ProGet Free Edition. You can still add them, but they will apply to all feeds." should be displayed when you add a privilege, but it's probably easy to miss. I'm not sure if we show it after that. As for Personal API Keys, you can create them as an admin, but non-admin users can't create their own. It's a different page. Cheers, Steve

@kc_2466 thanks for the heads up, we'll target reviewing/fixing this for the following maintenance release (i.e. 2024.27 / Feb 21) via PG-2893

Hi @kc_2466, Thanks for submitting this to us. It looks like there is an issue with packages with 3 or less characters that may fail to download. I created ticket, PG-2886, which will release this Friday (February 3rd, 2025), that will contain the fix for this. I also want to note that version 2.8.0 of syn does not exist on crates.io, so I verified using syn 2.0.8. Thanks, Rich

Hi @kc_2466, Looks like download uses an API we haven't implemented. Didn't expect that it would use a different mechanism from install! I don't think we'll get a fix for this in tomorrow's release, but I'll schedule it for the following on Feb. 7 (should be v2024.26). Thanks!

I've now found a cleaner way of adding this entry to the host file... If using docker run, add the argument: --add-host=<host_server_name>=127.0.0.1 if using a docker compose file, add an entry: extra_hosts: - "<host_server_name>: 127.0.0.1"