VSTS问题连接到GHE(HTTP 403) [英] VSTS issues connecting to GHE (HTTP 403)

查看:480
本文介绍了VSTS问题连接到GHE(HTTP 403)的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们没有改变VSTS(Visual Studio Team Services)中的任何内容,并且在试图从GHE(Github企业版)提取代码时,在我们的获取源构建步骤中突然出现HTTP 403错误。

We haven't changed anything in VSTS (Visual Studio Team Services) and are suddenly getting HTTP 403 errors in our "Get Sources" build step when trying to pull code from GHE (Github enterprise).


<2018-01-10T01:45:07.5198700Z远程:您的帐户已被暂停。请咨询您的安装管理员。
2018-01-10T01:45:07.5294550Z致命:无法访问'https:// ********:********@ghe-us.ourcompany.com/ ourteam / ourservice.git /':请求的URL返回错误:403
2018-01-10T01:45:07.8066190Z ## [error] Git获取失败,退出代码为128
2018-01- 10T01:45:07.8361190Z ## [section] Finishing:Get Sources`

2018-01-10T01:45:07.5198700Z remote: Your account is suspended. Please check with your installation administrator. 2018-01-10T01:45:07.5294550Z fatal: unable to access 'https://********:********@ghe-us.ourcompany.com/ourteam/ourservice.git/': The requested URL returned error: 403 2018-01-10T01:45:07.8066190Z ##[error]Git fetch failed with exit code: 128 2018-01-10T01:45:07.8361190Z ##[section]Finishing: Get Sources`

我们使用Github PAT(不带用户名)进行身份验证。有人试图创建一个新的PAT,并工作。

We're using a Github PAT (without username) to authenticate. Someone tried creating a new PAT and that worked.

为什么这个功能停止工作,为什么新的PAT会修复它?

Why has this stopped working and why did a new PAT fix it?

推荐答案

之前进行了一项更改,要求在GHE设备的前门允许帐户驻留在安全组内。他们已将该帐户添加到IDWeb中的组中,因此复制可能需要长达4小时才能完全传播。

There was a change done a little bit ago which requires accounts reside within a security group be allowed in the front door of the GHE appliance. They've added that account to the group within //IDWeb so replication may take up to 4 hours to fully propagate.

这可能是因为用户在技术上一个启用了电子邮件的服务帐户。

This is likely because the "user" was technically an email-enabled service account.

这篇关于VSTS问题连接到GHE(HTTP 403)的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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