Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Identity] Handle MSAL string response scenario #40281

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

pvaneck
Copy link
Member

@pvaneck pvaneck commented Mar 29, 2025

Closes: #40240

Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR aims to improve error handling in the MSAL client when the response content is a string rather than a dictionary.

  • Added a new test to verify that MSAL string error responses are properly handled.
  • Updated the error storage logic in the MSAL client to account for non-dictionary content.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
sdk/identity/azure-identity/tests/test_msal_client.py Adds a test to validate string error response handling
sdk/identity/azure-identity/azure/identity/_internal/msal_client.py Adjusts error extraction logic to handle string responses

@pvaneck pvaneck force-pushed the identity-msal-error-string branch from ec10dbc to 78a4f47 Compare March 29, 2025 00:34
@azure-sdk
Copy link
Collaborator

API change check

API changes are not detected in this pull request.

@pvaneck pvaneck marked this pull request as ready for review April 1, 2025 21:18
@pvaneck pvaneck requested review from xiangyan99 and a team as code owners April 1, 2025 21:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Untriaged
Development

Successfully merging this pull request may close these issues.

[Identity] Errors handling non-dictionary content type in proxy scenarios
2 participants