Custom state leads to error after upgrading to 3.14.0 #7122
Labels
bug
A problem that needs to be fixed for the feature to function as intended.
msal-angular
Related to @azure/msal-angular package
msal-browser
Related to msal-browser package
public-client
Issues regarding PublicClientApplications
Core Library
MSAL.js (@azure/msal-browser)
Core Library Version
3.14.0
Wrapper Library
MSAL Angular (@azure/msal-angular)
Wrapper Library Version
3.0.4
Public or Confidential Client?
Public
Description
We have an Angular application connected to Azure B2C. We have some instances where we pass a custom state parameter on our requests.
Since upgrading from msal-browser 3.1.0 to 3.14.0 (msal-angular 3.0.4 to 3.0.17) we are getting errors handling the redirect:
Error - Interaction type validation failed due to invalid_state: State was not the expected format
Error Message
[018faafb-8d9f-70a4-b219-89d5655425bf] : msal.js.browser@3.14.0 : Error - Interaction type validation failed due to invalid_state: State was not the expected format
MSAL Logs
msal-issue-1716561570583.log
Network Trace (Preferrably Fiddler)
MSAL Configuration
Relevant Code Snippets
Reproduction Steps
Log in
Execute the logoutRedirect with and EndSessionRequest with a custom value for state
Observe the error when handling the redirect back to the application
Expected Behavior
No error is shown and the state can be read from the query parameter
Identity Provider
Azure B2C Custom Policy
Browsers Affected (Select all that apply)
Chrome
Regression
@azure/msal-browser 3.1.0
Source
External (Customer)
The text was updated successfully, but these errors were encountered: