microsoft / microsoft/artifacts-keyring
Move from PATs to Microsoft Entra tokens?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 45
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
Currently, the use of artifacts-keyring uses creates personal access tokens (PATs) on use. The documentation for authenticating to Azure Devops with personal access tokens has the following "Important" warning text:
We recommend the more secure Microsoft Entra tokens over higher-risk personal access tokens. Learn more about our efforts to reduce PAT usage. Review our authentication guidance to choose the right authentication mechanism for your needs.
Is there a plan to move away from managing PATs to leveraging Microsoft Entra tokens?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the current artifacts-keyring flow that creates Azure DevOps personal access tokens, then read the linked Microsoft Entra authentication guidance. Determine whether Entra token support can replace PAT management; done would require an agreed migration plan or implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, python
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100