Hi @claes-hermansson_6271, Great! Our recommend three-feed workflow (unapproved, approved, internal) is similar, and keeps the third-party packages in the first two feeds. This way, you can scan for vulnerabilities much more easily. As I understand it though, to get full coverage the pgscan tool needs to be installed on every build server, and the pgscan publish... command needs to be implemented in every build? This is correct. Dependency resolution is complex and often nondeterministic, so it can only really happen at build-time. Hopefully you can templatize pretty easily :) Cheers, Steve

As a followup, it's worth mentioning that this occurs specifically when directory providers are switched. The "Active Directory (New)" user directory requires the user@domain.tld format, so switching from the previous "LDAP & Active Directory" user directory (which supported netBIOSdomain\user) no longer can impersonate.

Hmm , it's hard to say. It's just a random crash with no indiciation of a specific error... You should switch to IIS, perhaps then you can get better insight into what might be causing it... or the error might go away altogether.