Skip to main content

Using Personal Access Tokens(PAT) to clone Azure DevOps Git Repositories

When working with Azure DevOps repositories, Personal Access Tokens (PATs) offer an alternative to traditional authentication. Although I would not recommend them for general usage, there are some scenario's where a PAT is a secure option providing security through scoped permissions, expiration dates, and the ability to revoke access without changing your primary credentials.

I had a situation where I needed to clone a set of GIT repositories and run a scan on each repository. As the script would be running for a long time I thought it would be better to create and use a PAT instead of my own account.

Creating a Personal Access Token (PAT)

  1. Sign in to your Azure DevOps organization
  2. Click on your profile icon in the top right corner
  3. Select "Personal access tokens"
  4. Click "+ New Token"
  5. Configure your token:
    • Give it a meaningful name
    • Set an expiration date
    • Select the organization
    • Under "Scopes," select "Code" with "Read" permissions (or "Read & write" if you need to push changes)
  6. Click "Create"
Important: Copy the token immediately and store it securely. You won't be able to see it again.

Cloning an Azure DevOps Git repo using a PAT

Depending if you are using Azure Devops Services (cloud) or Azure DevOps Server (on-prem) the approach is a little bit different:

Method 1: Azure DevOps Services (Cloud)

For Azure DevOps Services (the cloud-hosted version), you can embed the PAT directly in the clone URL:

git clone https://<PAT>@<organization>.visualstudio.com/<organization>/_git/<repository>

Method 2: Azure DevOps Server (On-Premises)

For Azure DevOps Server installations, the authentication method differs. You need to use the Authorization header with Base64-encoded credentials:

git -c http.extraheader='Authorization: Basic [base64_encoded_credentials]' clone https://<server>:<port>/tfs/<collection>/_git/<repository>

You need to encode the string "username:PAT" in Base64 format.

On Linux/Mac:

echo -n "username:your_pat_token" | base64

On Windows (PowerShell):

[Convert]::ToBase64String([Text.Encoding]::ASCII.GetBytes("username:your_pat_token"))

To avoid typing the header for every command, you can configure it in your repository git config:

# Set the extra header configuration

git config http.extraheader "Authorization: Basic [base64_credentials]"

More information

Use Personal Access Tokens - Azure DevOps | Microsoft Learn

Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...
Read more