does it happen with any NuGet package you try to push with the SAML user?.Did not get the 403, however, the was still present in the local folder. Then added the delete permission for the same user and then retried deploying. I have attached the screenshot of the repository and the packages created. nuspec file entry, returning an invalid metadata
#347 winfo code#
22:07:53,534 (o.a.r.ArtifactoryResponseBase:125) - Sending HTTP error code 403: Not enough permissions to overwrite artifact 'nuget-local:' (user needs DELETE permission). 22:07:53,356 (o.j.r.n.NuGetWorkContext:68) - Indexing NuGet metadata for repo 'nuget-local' on path 'Dapper.1.60.9.nupkg' 22:07:53,316 (o.a.e.UploadServiceImpl:386) - Deploy to 'nuget-local:Dapper.1.60.9.nupkg' Content-Length: unspecified 22:07:52,122 (o.a.a.n.NuGetServiceImpl:282) - NuGet package nuget-local: does not have a NuGet ID. 22:07:52,094 (o.a.e.UploadServiceImpl:386) - Deploy to 'nuget-local:' Content-Length: unspecified Response status code does not indicate success: 403 (Forbidden). Pushing Dapper.1.60.9.nupkg to 'RESTRICTED_URL'. PS C:\downloads\prasanna-test\jQuery.3.4.1> nuget push. In the UI we can see the package deployed in the repository along with another package. Nuget push using a SAML user gives a 403 when using the SAML user. Nuget push using a SAML user pushes the package but gives a 403 in the client and in request.log
0 kommentar(er)
