microsoft / microsoft/ado-codespaces-auth
Allow granular scopes based on extension preference
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 10
- Forks
- 8
- Avg merge
- 8h 55m
- Merged PRs (30d)
- 2
Description
Azure devops added support for granular scopes https://devblogs.microsoft.com/devops/new-azure-devops-scopes-now-available-for-microsoft-identity-oauth-delegated-flow-apps/. Previously we only had one default scope which allows access to all APIs.
Most developers using codespaces don't need tokens beyond vso.code_write (Git pull, push) & vso.packaging (Packaging - read). Getting full access tokens also risk developers making unintentional changes.
We can default to using the existing full scope, but allow developers to add the needed scopes in their devcontainer configuration using the VSCode settings customization option.
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 with the Azure DevOps scopes reference linked in the issue and the existing full-scope behavior. Then trace how VS Code settings customization is supplied through devcontainer configuration. Done means the full scope remains the default while configured granular scopes, including code and packaging permissions, are used for tokens.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript, vscode
- Domain
- authentication, developer-experience
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100