fix: Fix Azure DevOps authentication for personal Microsoft accounts #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The changes in `README.md` update the description: - of the `keyrings.artifacts` package to explicitly mention that it leverages the `azure-identity` library for authentication. - of the system-wide keyring installation adding a note, that pixi global install is not possible yet
- Context: For Azure DevOps organizations linked to a personal Microsoft account, `AzureCLiCredential` does not work. - Implemented a check to determine if an Azure DevOps organization is linked to a personal account. - The check involves making a plain request to the Azure DevOps organization PyPI simple URL. - If the request returns only basic auth authentication in the header or the returned tenant_id (`X-VSS-ResourceTenant`) is `00000000-0000-0000-0000-000000000000` in return header, it indicates a personal Microsoft account.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
For Azure DevOps organizations linked to a personal Microsoft account,
AzureCLiCredentialdoes not work.Changes
"X-VSS-ResourceTenant") is00000000-0000-0000-0000-000000000000in the return header, it indicates a personal Microsoft account.This fix ensures that the correct authentication method is used for Azure DevOps organizations linked to personal Microsoft accounts.