Posts made by philipp.jenni_7195

I wait for the next official release. i have a workaround with disable the permission

I have tested your latest release. Now i can't upload any file. You can reproduce it with the same steps, but now the upload of 7.60.0 will fail.

On Docker output i see follow output:

Running Execution Dispatcher...
Running Execution Dispatcher...
Checking for executions to dispatch...
Checking for executions to dispatch...
Execution Dispatcher completed.
Execution Dispatcher completed.
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 PUT http://localhost:81/upack/Test/upload application/zip 2338404
A 403 error occurred in Test: The Feeds_OverwritePackage task is required to perform this action.
A 403 error occurred in Test: The Feeds_OverwritePackage task is required to perform this action.
An error occurred processing a PUT request to http://localhost:81/upack/Test/upload: The Feeds_OverwritePackage task is required to perform this action.
An error occurred processing a PUT request to http://localhost:81/upack/Test/upload: The Feeds_OverwritePackage task is required to perform this action.
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 PUT http://localhost:81/upack/Test/upload application/zip 2338404 - 403 67 - 34.9552ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 POST http://localhost:81/0x44/ProGet.WebApplication/Inedo.ProGet.WebApplication.Controls.Layout.NotificationBar/GetNotifications - 0
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 POST http://localhost:81/0x44/ProGet.WebApplication/Inedo.ProGet.WebApplication.Controls.Layout.NotificationBar/GetNotifications - 0 - 200 30 - 2.3018ms
Running Feed Replication...
Running Feed Replication...
Feed Replication completed.
Feed Replication completed.
Running Execution Dispatcher...
Running Execution Dispatcher...
Checking for executions to dispatch...
Checking for executions to dispatch...
Execution Dispatcher completed.
Execution Dispatcher completed.

Here the steps how you can reproduce:

• Create a docker-compose file:

  services:
    proget:
  	container_name: proget_proget
  	deploy:
  	  replicas: 1
  	environment:
  	  SQL_CONNECTION_STRING: "Data Source=sql-server-db; Initial Catalog=ProGet; User ID=sa; Password=my-p8ss53rd"
  	expose:
  	- 81
  	image: proget.inedo.com/productimages/inedo/proget:latest
  	labels:
  	  generated: by 8gwifi.org
  	ports:
  	- '81:80'
    sql-server-db:
  	container_name: sql-server-db
  	image: mcr.microsoft.com/mssql/server:2019-latest
  	ports:
  	  - "1433:1433"
  	environment:
  	  SA_PASSWORD: "my-p8ss53rd"
  	  ACCEPT_EULA: "Y"
  version: '3'
  ```
  

• Run "docker-compose up"
• Connect to the SQL Server with SA and create a db "ProGet"
• Run "docker-compose down"
• Run "docker-compose up
• Connect with browser to "http://localhost:81
• Login with "admin/admin"
• Enter a "Free" Lizence Key
• Create a Universal Package feed "Test"
• Create an API Key with Type "Feed" and Permission "View/Download" anad "Add/Repackage" for all Feeds
• Download upack.exe from https://github.com/Inedo/upack/releases
• Execute upack.exe push database-schema-7.60.0.upack http://localhost:81/upack/Test/ --user=api:<Your generated API>
• Execute upack.exe push database-schema-7.61.0.upack http://localhost:81/upack/Test/ --user=api:<Your generated API>

On the second upack command you should receive the error.

I was just able to reproduce the error with this procedure on Windows 10 and Docker Desktop.

Yes. That is correct. I can it reproduce with any package.

Hi Rich,

I can reproduce this on 2 different systems with the same case over and over again.

1. create new feed
2. create API key for this feed
3. push package with the smaller version. This works.
4. create package with the bigger version. This gives an error

Both systems are based on a Docker container (Linux) with MSSQL.

Is there any way to generate a detailed log that I can send to you?

I have sent you screenshot of my config and 2 upacks.

I have tried it with another installation and have exactly the same problem there. No matter with which upack I tested.

With the following case the problem should be reproduced.

Proget: 2022.18 (Docker version)
UPack: 3.0.1

• Create an API key which only has the permission "View/Download" and "Add/Package" on the application feed. The feed type is "Feed
• Create UPack with new version
• Push the package with the following command upack.exe push mypackage-3.0.0.upack http://myserver/upack/jnetwork-applicaton/ --user=api:XAPIKEYXXXXXXXXXXXXXXXXXXXXXX
• Create UPack with new version
• Push the package with the following command upack.exe push mypackage-3.0.1.upack http://myserver/upack/jnetwork-applicaton/ --user=api:XAPIKEYXXXXXXXXXXXXXXXXXXXXXX

The first upload works, but the second upload with an new version to an exisiting package will fail. UPack then gives me the following error:

Unhandled exception. Inedo.UPack.Net.UniversalFeedException: 403 Forbidden: The Feeds_OverwritePackage task is required to perform this action.

In one place it worked for me, but then I found out that the API key was mapped to a user who was in the administrators group.

The server is not public, but i can send you a database backup and the docker config.

I have tried with V.3.1 of upack. Same result. Upack returns: Inedo.UPack.Net.UniversalFeedException: 403 Forbidden: The Feeds_OverwritePackage task is required to perform this action.

Version: upack 2.2.5.15

Command: upack puch c:\tmp\database-schema-7.60.0.upack https://nuget.exanic.local/upack/application --user=user:password

I doesn't use the API Key

I use Build-In Users. The User is an Group, and the Group has the Publish Package Permission for all Feeds

Hi,

I have tested the problem again and can reproduce it even with a new feed.

The upload via the UI works in any case. The upload via the UPack.exe works only as long as in the table [Feeds] in the field [FeedConfiguration_Xml] the property FeedUsage is set to value Mixed. If the value is PrivateOnly it does not work anymore. The value changes as soon as you save the type once in the feed configuration.

Hi Alana,

I have checked this and uploaded a new version where never exisits and it also not working.

In release 2022.15 i become an error 403 forbidden when i will push a new universalpackage to the proget server.
The user has the follow permssions:

• Feeds_AddPackage
• Feeds_DownloadPackage
• Feeds_PullPackage
• Feeds_ViewFeed

The Version is not existing in the feed!

when i add the permission "Feeds_OverwritePackage" to the user, it works fine.

It has the permission requirements changed or is it a bug?

I use the Docker Container.