Fixing issue using bearer token on vsts.

MethodsAndPractices · Jul 10, 2018 · 74d588f · 74d588f
1 parent f7fd6e3
commit 74d588f
Show file tree

Hide file tree

Showing 4 changed files with 15 additions and 4 deletions.
diff --git a/.docs/Add-VSTeamAccount.md b/.docs/Add-VSTeamAccount.md
@@ -73,7 +73,7 @@ Note: You must run PowerShell as an Adminstrator to store at the Machine level.
 ### -------------------------- EXAMPLE 7 --------------------------
 
 ```PowerShell
-PS C:\> Add-VSTeamAccount -Account mydemos -Token $(System.AccessToken) -BearerToken
+PS C:\> Add-VSTeamAccount -Account mydemos -Token $(System.AccessToken) -UseBearerToken
 ```
 
 Will add the account and use the OAuth Token provided by VSTS when you check the *Allow scripts to access OAuth token* checkbox on the phase. Using this method removes the need to create a Personal Access Token. Note -Token is just an alais for -PersonalAccessToken.  
@@ -146,7 +146,7 @@ Type: SwitchParameter
 Parameter Sets: Windows
 ```
 
-### -BearerToken
+### -UseBearerToken
 
 Switches the authorzation from Basic to Bearer.  You still use the PAT for PersonalAccessToken parameters to store the token.
 

diff --git a/.docs/Add-VSTeamProfile.md b/.docs/Add-VSTeamProfile.md
@@ -92,7 +92,7 @@ Type: SwitchParameter
 Parameter Sets: Windows
 ```
 
-### -BearerToken
+### -UseBearerToken
 
 Switches the authorzation from Basic to Bearer.  You still use the PAT for PersonalAccessToken parameters to store the token.
 

diff --git a/README.md b/README.md
@@ -12,6 +12,16 @@ The cases of every file is very important. This module is to be used on Windows,
 
 ## Release Notes
 
+### 3.0.1
+
+Huge review of the docs and added support for bearer auth.
+
+Bearer auth will allow you to use the OAuth token created by VSTS during your build and release and not have to create a PAT. Just check the 'Allow scripts to access OAuth token' option on your phase. Then you can add an account by using the -UseBearerToken switch and passing in the $(System.AccessToken) variable.
+
+```PowerShell
+Add-VSTeamAccount -Account mydemos -Token $(System.AccessToken) -UseBearerToken
+```
+
 ### 3.0.0
 
 There is a breaking change with calls to Add-VSTeamKubernetesEndpoint. The acceptUntrustedCerts and generatePfx parameters have been changed from boolean to switch. So any calls that contained:

diff --git a/src/team.psm1 b/src/team.psm1
@@ -67,7 +67,7 @@ function _clearEnvironmentVariables {
       [System.Environment]::SetEnvironmentVariable("TEAM_PROJECT", $null, $Level)
    }
 
-   _setEnvironmentVariables -Level $Level -Pat '' -Acct '' -BearerToken ''
+   _setEnvironmentVariables -Level $Level -Pat '' -Acct '' -UseBearerToken ''
 }
 
 function Get-VSTeamInfo {
@@ -241,6 +241,7 @@ function Add-VSTeamAccount {
 
          if ($UseBearerToken.IsPresent) {
             $token = $_pat
+            $encodedPat = ''
          }
          else {
             $token = ''