Azure Devops 发布到自己的提要突然导致 403 被禁止 [英] Azure Devops publishing to own feed suddenly results in 403 forbidden

查看:33
本文介绍了Azure Devops 发布到自己的提要突然导致 403 被禁止的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我已经在一个项目中使用 Azure DevOps 有一段时间了,但突然发布到我自己的组织/集合源导致 403.

我创建了一个提要,我可以在 nuget push 构建步骤中选择它,但它不起作用.我创建了一个新提要来发布 NuGet 包,这再次完美运行.在我看来,令牌已过期,但我从未创建过令牌或使用它进行身份验证.我也不想将 NuGet 提要更改为新提要,因为我也想使用旧包.

这是构建管道:

这是堆栈跟踪:

<块引用>

活动代码页:65001 SYSTEMVSSCONNECTION 存在真SYSTEMVSSCONNECTION 存在 true SYSTEMVSSCONNECTION 存在 true

[警告]无法创建出处会话:{statusCode":500,result":{$id":1",innerException":null,message":";用户

'a831bb9f-aef5-4b63-91cd-4027b16710cf' 缺乏完成权限这个动作.你需要有'ReadPackages'.","typeName":"Microsoft.VisualStudio.Services.Feed.WebApi.FeedNeedsPermissionsException,Microsoft.VisualStudio.Services.Feed.WebApi","typeKey":"FeedNeedsPermissionsException","errorCode":0,"eventId":3000}}将 NuGet.config 保存到临时配置文件.将 NuGet.config 保存到临时配置文件.[命令]C:Program Filesdotnetdotnet.exe"nuget push d:a1aMicrowave.0.13.3.2019072215-beta.nupkg --source

Feed 权限中有一个新的用户界面:

I have been using Azure DevOps for a project for quite some time, but suddenly publishing to my own organisation/collection feed results in a 403.

I created a feed and I can select it on the nuget push build step, but it does not work. I created a new feed to publish the NuGet packages to and this works perfectly again. It seems to me like a token expired, but I never created one or used it to authenticate. I also do not want to change my NuGet feed to the new one, as I want to use older packages as well.

This is the buildpipeline:

And this is the stack trace:

Active code page: 65001 SYSTEMVSSCONNECTION exists true SYSTEMVSSCONNECTION exists true SYSTEMVSSCONNECTION exists true

[warning]Could not create provenance session: {"statusCode":500,"result":{"$id":"1","innerException":null,"message":"User

'a831bb9f-aef5-4b63-91cd-4027b16710cf' lacks permission to complete this action. You need to have 'ReadPackages'.","typeName":"Microsoft.VisualStudio.Services.Feed.WebApi.FeedNeedsPermissionsException, Microsoft.VisualStudio.Services.Feed.WebApi","typeKey":"FeedNeedsPermissionsException","errorCode":0,"eventId":3000}} Saving NuGet.config to a temporary config file. Saving NuGet.config to a temporary config file. [command]"C:Program Filesdotnetdotnet.exe" nuget push d:a1aMicrowave.0.13.3.2019072215-beta.nupkg --source https://simonheiss87.pkgs.visualstudio.com/_packaging/5f0802e1-99c5-450f-b02d-6d5f1c946cff/nuget/v3/index.json --api-key VSTS error: Unable to load the service index for source https://simonheiss87.pkgs.visualstudio.com/_packaging/5f0802e1-99c5-450f-b02d-6d5f1c946cff/nuget/v3/index.json. error: Response status code does not indicate success: 403 (Forbidden - User 'a831bb9f-aef5-4b63-91cd-4027b16710cf' lacks permission to complete this action. You need to have 'ReadPackages'. (DevOps Activity ID: 2D81C262-96A3-457B-B792-0B73514AAB5E)).

[error]Error: The process 'C:Program Filesdotnetdotnet.exe' failed with exit code 1

[error]Packages failed to publish

[section]Finishing: dotnet push to own feed

Is there an option I am overlooking where I have to authenticate myself somehow? It is just so weird.

解决方案

"message":"User 'a831bb9f-aef5-4b63-91cd-4027b16710cf' lacks permission to complete this action. You need to have 'ReadPackages'.

According to this error message, the error you received caused by the user(a831bb9f-aef5-4b63-91cd-4027b16710cf) does not have the access permission to your feed.

And also, as I checked from backend, a831bb9f-aef5-4b63-91cd-4027b16710cf is the VSID of your Build Service account. So, please try with adding this user(Micxxxave Build Service (sixxxxss87)) into your target feed, and assign this user the role of Contributor or higher permissions on the feed.

In addition, here has the doc you can refer:

There is a new UI in the Feed Permissions:

这篇关于Azure Devops 发布到自己的提要突然导致 403 被禁止的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆