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

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

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

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more