-
Notifications
You must be signed in to change notification settings - Fork 965
Description
Bug Details
Describe the bug
After successfully logging in and using the app for several hours or a day, the following errors occur when reaccessing the web app the next day without re-login:
Fetch API cannot load https://login.windows.net/{tenant}/oauth2/v2.0/authorize?response_type=id_token&redirect_uri=https%3A%2F%2Fmywebappname.azurewebsites.net%2F.auth%2Flogin%2Faad%2Fcallback&client_id={clientid}&scope=openid+profile+email&response_mode=form_post&nonce={id_2412031212}&state=redir%3D%252FgetFeatureFlags due to access control checks.
Failed to load resource: Origin https://{mywebappname}.azurewebsites.net is not allowed by Access-Control-Allow-Origin. Status code: 200
TypeError: globalThis.requestIdleCallback is not a function. (In 'globalThis.requestIdleCallback(this.processMutations, { timeout: 500 })', 'globalThis.requestIdleCallback' is undefined)
at bootstrap-autofill-overlay.js:4273
NOTE - If clear the browser cache and re-logged in it work again
Steps To Reproduce
-Log in to the web app and use it for a few hours.
-Leave the session idle overnight.
-Access the web app the next day without re-login.
What is the expected behavior?
Authentication flow should initiate seamlessly without the CORS policy error.
Actual Behavior:
The UI partially loads, and some authenticated content fails to load due to the described errors.
The CORS error appears, preventing seamless authentication.
Because of this above errors UI not load the Web + Chat and Web Options
Screenshots
If applicable, add screenshots to help explain your problem.
