This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(76.8, 83%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKS%3C/text%3E%3C/svg%3E)
azure ad b2c login page gives 400 bad request after keeping screen idle for the whole night. How can I resolve this issue?
Hi @Kalim Shariff , this is most likely just due to session/token expiry. Unless I'm misunderstanding. Are you logged in the entire night, and then it logs you out? Or is this just the log in page? Can you just refresh?
Thank u for u reply @James Hamil . I used Azure B2C with angular msal. My scenario is to get into the login page using azure b2c userflow and leave the page as it is for some time (may be over the night), so when you are trying to login after sometime. It is returning 400 badrequest. Can u please provide any solution?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(169.60000000000002, 77%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
Refreshing the page does cure the issue, but the user will not know to refresh, and considering this occurs in the azure user flow, it gets stuck. Is there a way to handle this gracefully in custom policies?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(262.40000000000003, 14.000000000000002%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJC%3C/text%3E%3C/svg%3E)
The only solution I see would be to wrap login request with try-catch and handle the error (e.g. auto-reload the page).
It happened to me (today) and my clients as well (few days ago).
I was logged in, put device to sleep. Next morning the page shown Session expired (our own code). I reloaded the page to get to login screen but the page is broken. I mean... we plan to handle this 400 response, but it should not happen.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(147.20000000000002, 4%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMT%3C/text%3E%3C/svg%3E)
I'm having this same problem with msal-react. Has anyone discovered a working solution for this?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(144, 21%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERC%3C/text%3E%3C/svg%3E)
I have the same error but happening in a different use case.
This happens also if just sitting on the login screen for a long time, on azure's oidc server. This is a UX problem for users who (rightly-so) log out when done, leave the tab open overnight, and the next day try to log in again. Any ideas how to solve? We're using custom policies.