You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please run the sample application, and login.
Go to the tasks page.
Wait for an hour, for the access token to expire.
Navigate to the tasks page.
You will be redirected to the
Expected behavior
Since I have a refresh token which is valid for 14 days, I was expecting AcquireTokenSilent to request a new access token without redirecting anywhere.
Actual behavior
A redirection to /fabrikamb2c.onmicrosoft.com/b2c_1_susi/oauth2/v2.0/authorize occurs (see detailed url above), to retrieve a totally new access token and refresh token.
Thank you very much for your time and effort,
Sergios.
The text was updated successfully, but these errors were encountered:
jmprieur
changed the title
[Bug] AcquireTokenSilent redirects to fabrikamb2c.onmicrosoft.com in sample web application
[Bug] AcquireTokenSilent redirects to fabrikamb2c.onmicrosoft.com in B2C web app / web API sample
Mar 10, 2021
Unfortunately moving to ASP.NET Core is not possible. Because we are integrating Azure B2C with an existing project which uses .NET Framework 4.8 and Web Forms.
Logs and Network traces
Which Version of MSAL are you using ?
MSAL 4.26.0
Platform
net451
What authentication flow has the issue?
Is this a new or existing app?
This is a sample web application part of Azure-Samples.
Repro
Please run the sample application, and login.
Go to the tasks page.
Wait for an hour, for the access token to expire.
Navigate to the tasks page.
You will be redirected to the
page.
Expected behavior
Since I have a refresh token which is valid for 14 days, I was expecting AcquireTokenSilent to request a new access token without redirecting anywhere.
Actual behavior
A redirection to /fabrikamb2c.onmicrosoft.com/b2c_1_susi/oauth2/v2.0/authorize occurs (see detailed url above), to retrieve a totally new access token and refresh token.
Possible Solution
Additional context/ Logs / Screenshots
I've also created an issue on the sample application.
Thank you very much for your time and effort,
Sergios.
The text was updated successfully, but these errors were encountered: