Does ProGet support creating and managing local groups for users authenticated via LDAP i.e. LDAP-authenticated users, but groups defined and managed locally in the system?
Is it possible to disable import or syncing of LDAP groups when integrating with an LDAP directory?
When trying to resolve a Maven package using Gradle through a Maven feed that’s configured with a third-party registry, e.g. public Maven or internal Maven via a connector, the server responds with a 500 Internal Server Error with message: Value cannot be null. (Parameter 's')
Additional context:
How can we resolve or work around this issue?
System information:
Web UI Version: 2025.5 (Build 16)
Database Schema Version: 25.0.5.16
SQL Server Version: PostgreSQL 17.5 (Debian 17.5-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
db_owner: True
Database Name: proget
Database Collation: C (UTF8)
Database Recovery Model: Default (1)
Database Read Committed Snapshot: True
Database Auto Update Stats: True
Hi @stevedennis, thanks for the reply. According to the documentation, the URL needed to create self-connector can be found on the "Feed Overview" page - however, I'm not sure how to navigate to that page from the UI, and I am also unable to find anything similar to the URL mentioned. Would you be able to point me in the right direction? Thanks.
Does ProGet support creating and managing local groups for users authenticated via LDAP i.e. LDAP-authenticated users, but groups defined and managed locally in the system?
Is it possible to disable import or syncing of LDAP groups when integrating with an LDAP directory?
In Nexus, multiple repositories of the same type can be grouped virtually and exposed through a single endpoint, allowing clients to resolve packages across multiple sources seamlessly.
Does ProGet support grouping multiple feeds into a single endpoint? If not, is there a recommended workaround to achieve similar behavior?
From the UI it seems like the Maven feed only support standard file types such as .jar, .war, and .ear. However for our use case, we need to publish and resolve artifacts that use custom file extensions, such as .zip, .module, etc., while still maintaining the Maven2 layout.
Is there a way to configure the Maven feed to accept and serve artifacts with non-standard extensions?
When trying to resolve a Maven package using Gradle through a Maven feed that’s configured with a third-party registry, e.g. public Maven or internal Maven via a connector, the server responds with a 500 Internal Server Error with message: Value cannot be null. (Parameter 's')
Additional context:
How can we resolve or work around this issue?
System information:
Web UI Version: 2025.5 (Build 16)
Database Schema Version: 25.0.5.16
SQL Server Version: PostgreSQL 17.5 (Debian 17.5-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
db_owner: True
Database Name: proget
Database Collation: C (UTF8)
Database Recovery Model: Default (1)
Database Read Committed Snapshot: True
Database Auto Update Stats: True