MethodsAndPractices / vsteam

PowerShell module for accessing Azure DevOps Services and Azure DevOps Server (formerly VSTS or TFS)
https://methodsandpractices.github.io/vsteam-docs/
MIT License
447 stars 155 forks source link

Unable to use cmdlets when -UseWindowsAuthentication is used for Set-VSTeamAccount #403

Closed ChrisGibson1982 closed 3 years ago

ChrisGibson1982 commented 3 years ago

Steps to reproduce


Set-VSTeamAccount -Account $devOpsOrg -UseWindowsAuthentication
get-vsteam -ProjectName $myProjectName

Get-VSTeam: Cannot validate argument on parameter 'ProjectName'. The cmdlet cannot protect plain text secrets sent over unencrypted connections. To suppress this warning and send plain text secrets over unencrypted networks, reissue the command specifying the AllowUnencryptedAuthentication parameter

Expected behavior

Should return a list of projects

Actual behavior

Should return a list of projects, but almost every command comes up with the same error in PowerShell 7. Windows PowerShell just doesn't return anything

Environment data

OS

Server

> Get-VSTeamAPIVersion
Name                           Value
----                           -----
Packaging                      3.0-preview
Version                        TFS2017
ServiceEndpoints               3.0-preview
HierarchyQuery
Graph
Pipelines
TaskGroups                     3.0-preview
ExtensionsManagement           3.0-preview
Git                            3.0
VariableGroups
Core                           3.0
Release                        3.0-preview
DistributedTaskReleased
MemberEntitlementManagement
Tfvc                           3.0
Processes
Policy                         3.0
Build                          3.0
DistributedTask                3.0-preview
SebastianSchuetze commented 3 years ago

I see that you are using the module version TFS2017 for the API but you are saying you try to go against Azure DevOps Services. The parameter UseWindowsAuthentication is only working against on-premises installations of Azure DevOps or in this case TFS. It does not work with the SaaS solution.

So this is by design and not a bug. :-)

closing this issue.