microsoft / microsoft/artifacts-credprovider

Default to / prefer Entra ID Access Tokens over AzDO PAT

Open
#543 2 comments 8 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

backlog enhancement keep
Dominant language
C#
Stars
947
Forks
728
PR merge metrics
No merged PRs in 30d

Description

per https://devblogs.microsoft.com/devops/reducing-pat-usage-across-azure-devops/ AzDO PAT is falling out of favour and they are suggesting leveraging Entra ID access tokens. This would be preferred in my org as the entra id auth tech keeps getting more security features that our InfoSec and platform teams really appreciate.

FWIW i'd suspect it be best if this plugin then stored a refresh token similar to how it stores the PAT today....

fwiw it's unclear to me if setting NUGET_CREDENTIALPROVIDER_VSTS_TOKENTYPE to SelfDescribing uses entra id tokens...i'm pretty sure they do not given the 4 hour span note...and i vaguely remember AzDO offering it's own jwt based access token at one point. if i'm wrong and that's the switch then this request may be about changing that default in 2.x

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the linked Azure DevOps guidance and the provider's handling of NUGET_CREDENTIALPROVIDER_VSTS_TOKENTYPE, especially the existing PAT storage and authentication flow. Determine whether SelfDescribing already uses Entra ID tokens and identify the provider entry points involved. Done means the preferred token flow and refresh-token storage behavior are defined and implemented with coverage for the default and relevant token-type settings.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, csharp
Domain
authentication, devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.