401 after idle app in browser with OAuth2 proxy
Opened this issue · 0 comments
anders-kiaer commented
How to reproduce
Steps to reproduce the behavior:
- Open a deployed app in browser. The app should be behind an OAuth2 proxy doing auth.
- Let it be idle for some time (might be order of ~1 h, not tested exactly).
- Do e.g. some button clicking that would trigger callbacks in the Dash app.
- Observe in browser console that requests get 401 response.
- The 401 is gone if Dash app page is reloaded in browser.
Expected behavior
Not having to reload for callbacks to work without 401.