Skip to Content (Press Enter)
UserImage.jpg
Julian Valero Sanchez
3Views
0Comments
[MSAL Reactive] Silent sign-in behaviour change in the latest version (1.1.0)
Question
Reactive
Forge
OutSystems 11
msal-reactive
Reactive icon
MSAL Reactive (O11)
Forge asset by Walter Robins
Application Type
Reactive

Hello,

After updating to the latest version (1.1.0) of the component we noticed that the client action SignInSilent was taking a long time to return. 

The client action SignInSilent now calls the ssoSilent, whereas the previous version of the component used acquireTokenSilent. The hidden iframe contains the following AADSTS errors:

- If third-party cookies aren't enabled: AADSTS50059.

- After enabling third-party cookies: AADSTS50011. The redirect URI specified in this error is the URL of the screen where the component is running.

Eventually ssoSilent times out and returns an error, which we handle by falling back to the interactive sign-in flow.

We are unsure of the reason behind the change in the silent sign-in action. As this change breaks the behaviour of our apps, we cannot use the new version of the component as it is. Do you have any suggestions on how to proceed?

Thank you.

0
0
10 Oct 2025
Copy Link
Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.