ROPC Flow not working #7558
Labels
bug-unconfirmed
A reported bug that needs to be investigated and confirmed
msal-node
Related to msal-node package
Needs: Attention 👋
Awaiting response from the MSAL.js team
public-client
Issues regarding PublicClientApplications
question
Customer is asking for a clarification, use case or information.
Core Library
MSAL.js (@azure/msal-node)
Core Library Version
3.1.0
Wrapper Library
Not Applicable
Wrapper Library Version
2.0.0
Public or Confidential Client?
Public
Description
here i describe that in c# the same flow correctly works for MSAL with the same username and password for the same tenant for federated credentials: pnp/cli-microsoft365#6582
this works but requires Microsoft.PowerApps.Administration.PowerShell module that is windows-specific.
if i use the pac cli that is cross platform, the login perfectly works and i can do whatever i want with the cli but it doesn't have the option to "enable" or "disable" cloud flow for a specific power platform environment.
and that is precisely why i stumbled upon the m365 cli.
but only with your cli, with the same username and password and using the same appId for the same tenant(specifying the tenant or not doesn't change the result):
fails to login and gives back
Error(s): 50126 - Timestamp: 2025-01-31 09:30:14Z - Description: AADSTS50126: Error validating credentials due to invalid username or password.
this is also the actual c# code i used for a different use case, and it still works fine:
Error Message
fails to login and gives back
Error(s): 50126 - Timestamp: 2025-01-31 09:30:14Z - Description: AADSTS50126: Error validating credentials due to invalid username or password.
MSAL Logs
fails to login and gives back
Error(s): 50126 - Timestamp: 2025-01-31 09:30:14Z - Description: AADSTS50126: Error validating credentials due to invalid username or password.
Network Trace (Preferrably Fiddler)
MSAL Configuration
Relevant Code Snippets
Reproduction Steps
execute the provided code for a federated adfs saml user of a valid organization for which you want a jwt from an azure tenant
Expected Behavior
i should be able to login and obtain a valid jwt as it happens for the c# library with the same setup and username/password.
Identity Provider
Entra ID (formerly Azure AD) / MSA
Browsers Affected (Select all that apply)
None (Server)
Regression
No response
The text was updated successfully, but these errors were encountered: