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

[Bug] Managed Identity: In the Machine Learning source, the client id is sent incorrectly in the network request #920

Open
Robbie-Microsoft opened this issue Mar 10, 2025 · 0 comments
Assignees
Labels
Bug Something isn't working, needs an investigation and a fix P3

Comments

@Robbie-Microsoft
Copy link

Robbie-Microsoft commented Mar 10, 2025

Library version used

latest

Java version

latest

Scenario

ManagedIdentityClient - managed identity

Is this a new or an existing app?

None

Issue description and reproduction steps

The Machine Learning source is based off of App Service 2017 (MSALs do not support this App Service 2017 version, only 2019). In the 2017 API, the client id should be passed to the network request as "clientid" instead of "client_id".

This bug was identified recently after Azure-SDK-for-JS removed their App Service 2017 implementation in favor of MSALJS's (msal-node) Machine Learning implementation. An Azure-SDK-for-JS customer is seeing network errors due to the incorrect way client id is being passed to the network request.

Relevant code snippets

Expected behavior

No response

Identity provider

Other

Regression

No response

Solution and workarounds

No response

@Robbie-Microsoft Robbie-Microsoft added needs attention Automatically used when an issue is created through an issue template untriaged Automatically used when an issue is created through an issue template labels Mar 10, 2025
@Avery-Dunn Avery-Dunn added Bug Something isn't working, needs an investigation and a fix P2 Normal priority items, should be done after P1 and removed needs attention Automatically used when an issue is created through an issue template untriaged Automatically used when an issue is created through an issue template labels Mar 11, 2025
@bgavrilMS bgavrilMS added P3 and removed P2 Normal priority items, should be done after P1 labels Mar 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working, needs an investigation and a fix P3
Projects
None yet
Development

No branches or pull requests

3 participants