Azure Question posted in
The official documentation to get you started can be found here.

Unable to call Azure DevOps Rest Api through PAT token

I am trying to import json file saved in local directory (desktop) to Azure DevOps Library Variable Group using Azure DevOps Rest api.

This is the script.

$jsonbody = Get-Content -Path "C:variable1.json" | Out-String
# Define organization name and PAT
$organization = ""
$token = "{PAT}"
$token = [System.Convert]::ToBase64String([System.Text.Encoding]::ASCII.GetBytes(":$($token)"))
$url="https://dev.azure.com/$organization/_apis/distributedtask/variablegroups?api-version=7.1-preview.2"
$head = @{ Authorization =" Basic $token" }
Invoke-RestMethod -Uri $url -Method Post -Headers $head -Body $jsonbody -ContentType application/json

This is the error message that I receive.

Invoke-RestMethod : The remote server returned an error: (401)
Unauthorized. At line:6 char:1 + Invoke-RestMethod -Uri $url -Method
Post -Headers $head -Body $jsonbo … +

+ CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-RestMethod],
WebException + FullyQualifiedErrorId :
WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeRestMethodCommand

I tried different rest api but received the same error message.

    $jsonbody = Get-Content -Path "C:variable1.json" | Out-String
    # Define organization name and PAT
    $organization = ""
    $token = "{PAT}"
    $token = [System.Convert]::ToBase64String([System.Text.Encoding]::ASCII.GetBytes(":$($token)"))
    $url="https://dev.azure.com/$organization/_apis/projects?api-version=7.1-preview.4"
    $head = @{ Authorization =" Basic $token" }
Invoke-RestMethod -Uri $url -Method GET -Headers $head -ContentType application/json

PAT token has full access.

These are the documents that I followed.

I can use the same PAT token to publish packages to Azure DevOps artefact feed (Nuget and NPM).

Any help would be appreciated on why the PAT token is not working when using rest api.

Tags:

2

Answers


  1. 0

    Initially, I generated PAT token with Full Access in my DevOps Portal like this:

    enter image description here

    Now, I ran below PowerShell script to list projects by calling Azure DevOps Rest API through PAT token:

    $orgUrl = "https://dev.azure.com/org_name"
$pat = "xxxxxxxxxxxxxxxxxxxxxxx"
$queryString = "api-version=7.1-preview.4"

$token = [System.Convert]::ToBase64String([System.Text.Encoding]::ASCII.GetBytes(":$($pat)"))
$header = @{Authorization = "Basic $token"}

$projectsUrl = "$orgUrl/_apis/projects?$queryString"
$projects = Invoke-RestMethod -Uri $projectsUrl -Method Get -ContentType "application/json" -Headers $header
$projects.value | ConvertTo-Json

    Response:

    enter image description here

    Similarly, you can use below script to import Json file saved in local directory to Azure DevOps Library Variable Group using Azure DevOps Rest Api:

    $jsonbody = Get-Content -Path "C:variablesvar.json" | Out-String
$orgUrl = "https://dev.azure.com/org_name"
$pat = "xxxxxxxxxxxxxxxxx"
$queryString = "api-version=7.1-preview.2"

$token = [System.Convert]::ToBase64String([System.Text.Encoding]::ASCII.GetBytes(":$($pat)"))
$header = @{Authorization = "Basic $token"}

$Url = "$orgUrl/_apis/distributedtask/variablegroups?$queryString"
$result = Invoke-RestMethod -Uri $Url -Method Post -Body $jsonbody -ContentType "application/json" -Headers $header

$result.variableGroupProjectReferences

    Response:

    enter image description here

    To confirm that, I checked the same in Azure DevOps portal where variable group imported successfully like this:

    enter image description here

    If still the error persists, try creating new PAT token with Full Access and use above mentioned scripts to call DevOps REST API.

    Reference:
    How to call Azure Devops REST API from PowerShell (opentechguides.com)

    Login or Signup to reply.
  2. 0

    PAT token has full access.

    Could you double-check if your PAT has full access?
    You can use PAT-Get-REST API to get the value of scope.
    Also you can follow the document 1 you mentioned above to check the Scopes in Azure Devops page.

    Besides you can create a new PAT with custom defined scopes and then try to use the new PAT to invoke REST APIS.

    Authorize the scope of access associated with this token.

    example:

    // Read, write, & manage
vso.variablegroups_manage  
vso.profile
vso.project

    Hope it can help you.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search