error: Received response 401 (Not Authorized)

[RagamRam]

Hi,
I’m getting the below error when trying to publish an extension. I’m using a valid newly created(today) PAT for this. Can you please check and let me know the issue? I’m getting the same error when I try to publish to on-premises TFS 2015 update3 local gallery from cmdline and also using this task.

2017-11-23T05:47:33.6546956Z Extracting archive: E:\Agent-Test_work\1\s\buildtool\ragamramachandran.build-task-0.0.10.vsix
2017-11-23T05:47:33.6546956Z --
2017-11-23T05:47:33.6546956Z Path = E:\Agent-Test_work\1\s\buildtool\ragamramachandran.build-task-0.0.10.vsix
2017-11-23T05:47:33.6546956Z Type = zip
2017-11-23T05:47:33.6546956Z Physical Size = 4953
2017-11-23T05:47:33.6546956Z
2017-11-23T05:47:33.6546956Z Everything is Ok
2017-11-23T05:47:33.6546956Z
2017-11-23T05:47:33.6546956Z Files: 6
2017-11-23T05:47:33.6546956Z Size: 6050
2017-11-23T05:47:33.6546956Z Compressed: 4953
2017-11-23T05:47:33.7794964Z [command]E:\Agents_Ext_work_tasks\PublishExtension_631511b4-50ab-47c8-b766-7ae2aa672733\1.1.44\node_modules\7zip-bin-win\x64\7za.exe a ragamramachandran.build-task-0.0.10.gen.vsix E:\Agents_Ext_work_temp\vsixeditor1171023-11684-1hhfljj.0cmn9daemi* -r -y -tzip -mx9
2017-11-23T05:47:33.8262967Z
2017-11-23T05:47:33.8262967Z 7-Zip (a) 17.01 beta (x64) : Copyright (c) 1999-2017 Igor Pavlov : 2017-08-28
2017-11-23T05:47:33.8262967Z
2017-11-23T05:47:33.8262967Z Scanning the drive:
2017-11-23T05:47:33.8262967Z 2 folders, 6 files, 5937 bytes (6 KiB)
2017-11-23T05:47:33.8262967Z
2017-11-23T05:47:33.8262967Z Creating archive: ragamramachandran.build-task-0.0.10.gen.vsix
2017-11-23T05:47:33.8262967Z
2017-11-23T05:47:33.8262967Z Add new data to archive: 2 folders, 6 files, 5937 bytes (6 KiB)
2017-11-23T05:47:33.8262967Z
2017-11-23T05:47:33.8262967Z
2017-11-23T05:47:33.8262967Z Files read from disk: 6
2017-11-23T05:47:33.8262967Z Archive size: 5376 bytes (6 KiB)
2017-11-23T05:47:33.8262967Z Everything is Ok
2017-11-23T05:47:39.0991305Z error: Received response 401 (Not Authorized). Check that your personal access token is correct and hasn't expired.
2017-11-23T05:47:39.1303307Z ##[error]tfx failed with error: Error: E:\Agents_Ext_work_tools\tfx.cmd failed with return code: 4294967295
2017-11-23T05:47:39.1303307Z ##[section]Finishing: Publish Extension
2017-11-23T05:47:39.1459308Z ##[section]Finishing: Release

Thanks,
Ragam

[jessehouwing]

If the command line isn't working, it would make sense the task won't work either, it invokes the command line in turn. TFS 2017 came with PAT support, 2015 as far as I can tell doesn't offer this option, so you need to use a NTLM proxy in order to publish directly to TFS or your tfs server must be configured to support basic authentication over SSL to allow you to pass in the username & password as plain text.

…

On Nov 23, 2017 07:11, "RagamRam" ***@***.***> wrote: Hi, I’m getting the below error when trying to publish an extension. I’m using a valid newly created(today) PAT for this. Can you please check and let me know the issue? I’m getting the same error when I try to publish to on-premises TFS 2015 update3 local gallery from cmdline and also using this task. 2017-11-23T05:47:33.6546956Z Extracting archive: E:\Agent-Test_work\1\s\ buildtool\ragamramachandran.build-task-0.0.10.vsix 2017-11-23T05:47:33.6546956Z -- 2017-11-23T05:47:33.6546956Z Path = E:\Agent-Test_work\1\s\ buildtool\ragamramachandran.build-task-0.0.10.vsix 2017-11-23T05:47:33.6546956Z Type = zip 2017-11-23T05:47:33.6546956Z Physical Size = 4953 2017-11-23T05:47:33.6546956Z 2017-11-23T05:47:33.6546956Z Everything is Ok 2017-11-23T05:47:33.6546956Z 2017-11-23T05:47:33.6546956Z Files: 6 2017-11-23T05:47:33.6546956Z Size: 6050 2017-11-23T05:47:33.6546956Z Compressed: 4953 2017-11-23T05:47:33.7794964Z [command]E:\Agents_Ext_work_ tasks\PublishExtension_631511b4-50ab-47c8-b766-7ae2aa672733\1.1.44\node_ modules\7zip-bin-win\x64\7za.exe a ragamramachandran.build-task-0.0.10.gen.vsix E:\Agents_Ext_work_temp\vsixeditor1171023-11684-1hhfljj.0cmn9daemi* -r -y -tzip -mx9 2017-11-23T05:47:33.8262967Z 2017-11-23T05:47:33.8262967Z 7-Zip (a) 17.01 beta (x64) : Copyright (c) 1999-2017 Igor Pavlov : 2017-08-28 2017-11-23T05:47:33.8262967Z 2017-11-23T05:47:33.8262967Z Scanning the drive: 2017-11-23T05:47:33.8262967Z 2 folders, 6 files, 5937 bytes (6 KiB) 2017-11-23T05:47:33.8262967Z 2017-11-23T05:47:33.8262967Z Creating archive: ragamramachandran.build-task-0.0.10.gen.vsix 2017-11-23T05:47:33.8262967Z 2017-11-23T05:47:33.8262967Z Add new data to archive: 2 folders, 6 files, 5937 bytes (6 KiB) 2017-11-23T05:47:33.8262967Z 2017-11-23T05:47:33.8262967Z 2017-11-23T05:47:33.8262967Z Files read from disk: 6 2017-11-23T05:47:33.8262967Z Archive size: 5376 bytes (6 KiB) 2017-11-23T05:47:33.8262967Z Everything is Ok 2017-11-23T05:47:39.0991305Z error: Received response 401 (Not Authorized). Check that your personal access token is correct and hasn't expired. 2017-11-23T05:47:39.1303307Z ##[error]tfx failed with error: Error: E:\Agents_Ext_work_tools\tfx.cmd failed with return code: 4294967295 2017-11-23T05:47:39.1303307Z ##[section]Finishing: Publish Extension 2017-11-23T05:47:39.1459308Z ##[section]Finishing: Release Thanks, Ragam — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#54>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AD-uSzSLErrXbLyvBVemrx5doKJk6uEsks5s5QyHgaJpZM4QoTpz> .

[RagamRam]

I’m able to upload the extension directly using TFS URL. But, yes, both the command-line and task fails. Using the basic authentication, I’m able to publish a customized build task to our TFS using command-line. Means our TFS is configured to support basic authentication over SSL and allows us to pass in the credential. Or do extensions and tasks publish work in a different way? I’m using basic-authentication, but the error shows PAT issue. [cid:image001.png@01D36478.4FBA5120] Thanks, Ragam From: Jesse Houwing [mailto:notifications@github.com] Sent: Thursday, November 23, 2017 4:18 PM To: Microsoft/vsts-extension-build-release-tasks <vsts-extension-build-release-tasks@noreply.github.com> Cc: Ramachandran, Ragam <Ragam.Ramachandran@allscripts.com>; Manual <manual@noreply.github.com> Subject: Re: [Microsoft/vsts-extension-build-release-tasks] error: Received response 401 (Not Authorized) (#54) If the command line isn't working, it would make sense the task won't work either, it invokes the command line in turn. TFS 2017 came with PAT support, 2015 as far as I can tell doesn't offer this option, so you need to use a NTLM proxy in order to publish directly to TFS or your tfs server must be configured to support basic authentication over SSL to allow you to pass in the username & password as plain text.

On Nov 23, 2017 07:11, "RagamRam" ***@***.******@***.***>> wrote: Hi, I’m getting the below error when trying to publish an extension. I’m using a valid newly created(today) PAT for this. Can you please check and let me know the issue? I’m getting the same error when I try to publish to on-premises TFS 2015 update3 local gallery from cmdline and also using this task. 2017-11-23T05:47:33.6546956Z Extracting archive: E:\Agent-Test_work\1\s\ buildtool\ragamramachandran.build-task-0.0.10.vsix 2017-11-23T05:47:33.6546956Z -- 2017-11-23T05:47:33.6546956Z Path = E:\Agent-Test_work\1\s\ buildtool\ragamramachandran.build-task-0.0.10.vsix 2017-11-23T05:47:33.6546956Z Type = zip 2017-11-23T05:47:33.6546956Z Physical Size = 4953 2017-11-23T05:47:33.6546956Z 2017-11-23T05:47:33.6546956Z Everything is Ok 2017-11-23T05:47:33.6546956Z 2017-11-23T05:47:33.6546956Z Files: 6 2017-11-23T05:47:33.6546956Z Size: 6050 2017-11-23T05:47:33.6546956Z Compressed: 4953 2017-11-23T05:47:33.7794964Z [command]E:\Agents_Ext_work_ tasks\PublishExtension_631511b4-50ab-47c8-b766-7ae2aa672733\1.1.44\node_ modules\7zip-bin-win\x64\7za.exe a ragamramachandran.build-task-0.0.10.gen.vsix E:\Agents_Ext_work_temp\vsixeditor1171023-11684-1hhfljj.0cmn9daemi* -r -y -tzip -mx9 2017-11-23T05:47:33.8262967Z 2017-11-23T05:47:33.8262967Z 7-Zip (a) 17.01 beta (x64) : Copyright (c) 1999-2017 Igor Pavlov : 2017-08-28 2017-11-23T05:47:33.8262967Z 2017-11-23T05:47:33.8262967Z Scanning the drive: 2017-11-23T05:47:33.8262967Z 2 folders, 6 files, 5937 bytes (6 KiB) 2017-11-23T05:47:33.8262967Z 2017-11-23T05:47:33.8262967Z Creating archive: ragamramachandran.build-task-0.0.10.gen.vsix 2017-11-23T05:47:33.8262967Z 2017-11-23T05:47:33.8262967Z Add new data to archive: 2 folders, 6 files, 5937 bytes (6 KiB) 2017-11-23T05:47:33.8262967Z 2017-11-23T05:47:33.8262967Z 2017-11-23T05:47:33.8262967Z Files read from disk: 6 2017-11-23T05:47:33.8262967Z Archive size: 5376 bytes (6 KiB) 2017-11-23T05:47:33.8262967Z Everything is Ok 2017-11-23T05:47:39.0991305Z error: Received response 401 (Not Authorized). Check that your personal access token is correct and hasn't expired. 2017-11-23T05:47:39.1303307Z ##[error]tfx failed with error: Error: E:\Agents_Ext_work_tools\tfx.cmd failed with return code: 4294967295 2017-11-23T05:47:39.1303307Z ##[section]Finishing: Publish Extension 2017-11-23T05:47:39.1459308Z ##[section]Finishing: Release Thanks, Ragam — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#54>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AD-uSzSLErrXbLyvBVemrx5doKJk6uEsks5s5QyHgaJpZM4QoTpz> .

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#54 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AgWaYmlcxeQ1mo1RNYyujLpML5eki0i6ks5s5U1MgaJpZM4QoTpz>.

[jessehouwing]

When using basic Auth you should not use the personal access token option. That was only added to 2017. You should use the user/pass option when setting up the service endpoint.

…

On Nov 23, 2017 12:00, "RagamRam" ***@***.***> wrote: I’m able to upload the extension directly using TFS URL. But, yes, both the command-line and task fails. Using the basic authentication, I’m able to publish a customized build task to our TFS using command-line. Means our TFS is configured to support basic authentication over SSL and allows us to pass in the credential. Or do extensions and tasks publish work in a different way? I’m using basic-authentication, but the error shows PAT issue. ***@***.*** Thanks, Ragam From: Jesse Houwing ***@***.*** Sent: Thursday, November 23, 2017 4:18 PM To: Microsoft/vsts-extension-build-release-tasks < ***@***.***> Cc: Ramachandran, Ragam ***@***.***>; Manual < ***@***.***> Subject: Re: [Microsoft/vsts-extension-build-release-tasks] error: Received response 401 (Not Authorized) (#54) If the command line isn't working, it would make sense the task won't work either, it invokes the command line in turn. TFS 2017 came with PAT support, 2015 as far as I can tell doesn't offer this option, so you need to use a NTLM proxy in order to publish directly to TFS or your tfs server must be configured to support basic authentication over SSL to allow you to pass in the username & password as plain text. On Nov 23, 2017 07:11, "RagamRam" ***@***.***<mailto: ***@***.***>> wrote: > Hi, > I’m getting the below error when trying to publish an extension. I’m using > a valid newly created(today) PAT for this. Can you please check and let me > know the issue? I’m getting the same error when I try to publish to > on-premises TFS 2015 update3 local gallery from cmdline and also using this > task. > > 2017-11-23T05:47:33.6546956Z Extracting archive: E:\Agent-Test_work\1\s\ > buildtool\ragamramachandran.build-task-0.0.10.vsix > 2017-11-23T05:47:33.6546956Z -- > 2017-11-23T05:47:33.6546956Z Path = E:\Agent-Test_work\1\s\ > buildtool\ragamramachandran.build-task-0.0.10.vsix > 2017-11-23T05:47:33.6546956Z Type = zip > 2017-11-23T05:47:33.6546956Z Physical Size = 4953 > 2017-11-23T05:47:33.6546956Z > 2017-11-23T05:47:33.6546956Z Everything is Ok > 2017-11-23T05:47:33.6546956Z > 2017-11-23T05:47:33.6546956Z Files: 6 > 2017-11-23T05:47:33.6546956Z Size: 6050 > 2017-11-23T05:47:33.6546956Z Compressed: 4953 > 2017-11-23T05:47:33.7794964Z [command]E:\Agents_Ext_work_ > tasks\PublishExtension_631511b4-50ab-47c8-b766-7ae2aa672733\1.1.44\node_ > modules\7zip-bin-win\x64\7za.exe a ragamramachandran.build-task-0.0.10.gen.vsix > E:\Agents_Ext_work_temp\vsixeditor1171023-11684-1hhfljj.0cmn9daemi* -r -y > -tzip -mx9 > 2017-11-23T05:47:33.8262967Z > 2017-11-23T05:47:33.8262967Z 7-Zip (a) 17.01 beta (x64) : Copyright (c) > 1999-2017 Igor Pavlov : 2017-08-28 > 2017-11-23T05:47:33.8262967Z > 2017-11-23T05:47:33.8262967Z Scanning the drive: > 2017-11-23T05:47:33.8262967Z 2 folders, 6 files, 5937 bytes (6 KiB) > 2017-11-23T05:47:33.8262967Z > 2017-11-23T05:47:33.8262967Z Creating archive: > ragamramachandran.build-task-0.0.10.gen.vsix > 2017-11-23T05:47:33.8262967Z > 2017-11-23T05:47:33.8262967Z Add new data to archive: 2 folders, 6 files, > 5937 bytes (6 KiB) > 2017-11-23T05:47:33.8262967Z > 2017-11-23T05:47:33.8262967Z > 2017-11-23T05:47:33.8262967Z Files read from disk: 6 > 2017-11-23T05:47:33.8262967Z Archive size: 5376 bytes (6 KiB) > 2017-11-23T05:47:33.8262967Z Everything is Ok > 2017-11-23T05:47:39.0991305Z error: Received response 401 (Not > Authorized). Check that your personal access token is correct and hasn't > expired. > 2017-11-23T05:47:39.1303307Z ##[error]tfx failed with error: Error: > E:\Agents_Ext_work_tools\tfx.cmd failed with return code: 4294967295 > 2017-11-23T05:47:39.1303307Z ##[section]Finishing: Publish Extension > 2017-11-23T05:47:39.1459308Z ##[section]Finishing: Release > > Thanks, > Ragam > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/Microsoft/vsts-extension-build-release- tasks/issues/54>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AD- uSzSLErrXbLyvBVemrx5doKJk6uEsks5s5QyHgaJpZM4QoTpz> > . > — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<https://github.com/ microsoft/azure-devops-extension-tasks#54# issuecomment-346585293>, or mute the thread<https://github.com/ notifications/unsubscribe-auth/AgWaYmlcxeQ1mo1RNYyujLpML5eki0 i6ks5s5U1MgaJpZM4QoTpz>. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#54 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AD-uS5GIWq6cs1AqRS63zYKNva84LR0Jks5s5VBpgaJpZM4QoTpz> .

[RagamRam]

Yes, I’m using user/pass option for setting up the service end point not the PAT. But while publishing the task I’m getting error related to PAT. [cid:image001.png@01D36551.5B0D21E0] C:\DeleteTasks>tfx extension publish --vsix C:\cVnextCustomTasks\ragamramachandran.build-task-0.0.10.vsix --auth-type basic TFS Cross Platform Command Line Interface v0.3.24 Copyright Microsoft Corporation

Username: XXXXXXXX Password:

Checking if this extension is already published It isn't, create a new extension. Received response 401 (Not Authorized). Check that your personal access token is correct and hasn't expired. Thanks, Ragam From: Jesse Houwing [mailto:notifications@github.com] Sent: Thursday, November 23, 2017 6:21 PM To: Microsoft/vsts-extension-build-release-tasks <vsts-extension-build-release-tasks@noreply.github.com> Cc: Ramachandran, Ragam <Ragam.Ramachandran@allscripts.com>; Manual <manual@noreply.github.com> Subject: Re: [Microsoft/vsts-extension-build-release-tasks] error: Received response 401 (Not Authorized) (#54) When using basic Auth you should not use the personal access token option. That was only added to 2017. You should use the user/pass option when setting up the service endpoint.

On Nov 23, 2017 12:00, "RagamRam" ***@***.******@***.***>> wrote: I’m able to upload the extension directly using TFS URL. But, yes, both the command-line and task fails. Using the basic authentication, I’m able to publish a customized build task to our TFS using command-line. Means our TFS is configured to support basic authentication over SSL and allows us to pass in the credential. Or do extensions and tasks publish work in a different way? I’m using basic-authentication, but the error shows PAT issue. ***@***.*** Thanks, Ragam From: Jesse Houwing ***@***.*** Sent: Thursday, November 23, 2017 4:18 PM To: Microsoft/vsts-extension-build-release-tasks < ***@***.******@***.***>> Cc: Ramachandran, Ragam ***@***.******@***.***>>; Manual < ***@***.******@***.***>> Subject: Re: [Microsoft/vsts-extension-build-release-tasks] error: Received response 401 (Not Authorized) (#54) If the command line isn't working, it would make sense the task won't work either, it invokes the command line in turn. TFS 2017 came with PAT support, 2015 as far as I can tell doesn't offer this option, so you need to use a NTLM proxy in order to publish directly to TFS or your tfs server must be configured to support basic authentication over SSL to allow you to pass in the username & password as plain text. On Nov 23, 2017 07:11, "RagamRam" ***@***.***<mailto:

<mailto:notifications@github.com%3cmailto:%0b>> notifications@github.com<mailto:notifications@github.com>>> wrote:

> Hi, > I’m getting the below error when trying to publish an extension. I’m using > a valid newly created(today) PAT for this. Can you please check and let me > know the issue? I’m getting the same error when I try to publish to > on-premises TFS 2015 update3 local gallery from cmdline and also using this > task. > > 2017-11-23T05:47:33.6546956Z Extracting archive: E:\Agent-Test_work\1\s\ > buildtool\ragamramachandran.build-task-0.0.10.vsix > 2017-11-23T05:47:33.6546956Z -- > 2017-11-23T05:47:33.6546956Z Path = E:\Agent-Test_work\1\s\ > buildtool\ragamramachandran.build-task-0.0.10.vsix > 2017-11-23T05:47:33.6546956Z Type = zip > 2017-11-23T05:47:33.6546956Z Physical Size = 4953 > 2017-11-23T05:47:33.6546956Z > 2017-11-23T05:47:33.6546956Z Everything is Ok > 2017-11-23T05:47:33.6546956Z > 2017-11-23T05:47:33.6546956Z Files: 6 > 2017-11-23T05:47:33.6546956Z Size: 6050 > 2017-11-23T05:47:33.6546956Z Compressed: 4953 > 2017-11-23T05:47:33.7794964Z [command]E:\Agents_Ext_work_ > tasks\PublishExtension_631511b4-50ab-47c8-b766-7ae2aa672733\1.1.44\node_ > modules\7zip-bin-win\x64\7za.exe a ragamramachandran.build-task-0.0.10.gen.vsix > E:\Agents_Ext_work_temp\vsixeditor1171023-11684-1hhfljj.0cmn9daemi* -r -y > -tzip -mx9 > 2017-11-23T05:47:33.8262967Z > 2017-11-23T05:47:33.8262967Z 7-Zip (a) 17.01 beta (x64) : Copyright (c) > 1999-2017 Igor Pavlov : 2017-08-28 > 2017-11-23T05:47:33.8262967Z > 2017-11-23T05:47:33.8262967Z Scanning the drive: > 2017-11-23T05:47:33.8262967Z 2 folders, 6 files, 5937 bytes (6 KiB) > 2017-11-23T05:47:33.8262967Z > 2017-11-23T05:47:33.8262967Z Creating archive: > ragamramachandran.build-task-0.0.10.gen.vsix > 2017-11-23T05:47:33.8262967Z > 2017-11-23T05:47:33.8262967Z Add new data to archive: 2 folders, 6 files, > 5937 bytes (6 KiB) > 2017-11-23T05:47:33.8262967Z > 2017-11-23T05:47:33.8262967Z > 2017-11-23T05:47:33.8262967Z Files read from disk: 6 > 2017-11-23T05:47:33.8262967Z Archive size: 5376 bytes (6 KiB) > 2017-11-23T05:47:33.8262967Z Everything is Ok > 2017-11-23T05:47:39.0991305Z error: Received response 401 (Not > Authorized). Check that your personal access token is correct and hasn't > expired. > 2017-11-23T05:47:39.1303307Z ##[error]tfx failed with error: Error: > E:\Agents_Ext_work_tools\tfx.cmd failed with return code: 4294967295 > 2017-11-23T05:47:39.1303307Z ##[section]Finishing: Publish Extension > 2017-11-23T05:47:39.1459308Z ##[section]Finishing: Release > > Thanks, > Ragam > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/Microsoft/vsts-extension-build-release-

<https://github.com/Microsoft/vsts-extension-build-release-%0b>> tasks/issues/54>,

> or mute the thread > <https://github.com/notifications/unsubscribe-auth/AD-

<https://github.com/notifications/unsubscribe-auth/AD-%0b>> uSzSLErrXbLyvBVemrx5doKJk6uEsks5s5QyHgaJpZM4QoTpz>

> . > — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<https://github.com/

<https://github.com/%0b>> microsoft/azure-devops-extension-tasks#54#

issuecomment-346585293>, or mute the thread<https://github.com/

<https://github.com/%0b>> notifications/unsubscribe-auth/AgWaYmlcxeQ1mo1RNYyujLpML5eki0

i6ks5s5U1MgaJpZM4QoTpz>. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#54 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AD-uS5GIWq6cs1AqRS63zYKNva84LR0Jks5s5VBpgaJpZM4QoTpz> .

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#54 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AgWaYub2m4Tb4BVupLfT-8GgssBQHugJks5s5WongaJpZM4QoTpz>.

[jessehouwing]

These issues are all related to tfx and not to the build tasks. I suspect the error message is generic for 401 and assumes usage of PAT, since the basic account support in 2015 was always sort of, but not very much supported.

Please report your issue here: https://github.com/Microsoft/tfs-cli

As I can't really do anything from this end, the CI tasks end up invoking tfx, if tfx isn't working these tasks won't work either.