Issue with Event Handling in Solara Integration with Auth0 on Inactivity
Hi everyone, I am currently testing Solara with Auth0 authentication and things have been going smoothly for the most part. However, I've noticed an intermittent issue where, if the application window is left open for an extended period, the event handling seems to stop functioning as if the connection has been severed. I may be wrong in assuming this issue is related to Auth0, but from a user's perspective, it appears as though everything is still operational when it is not. I would prefer the Auth0 session being explicity closed. Perhaps I'm dealing with two different topics here...
Anyway, I am wondering if there's a way to "automatically" close the Auth0 connection after a certain period of inactivity, which I would like to define specifically, say 30 minutes, and then prompt the user to re-enter their credentials. Is this possible? Any guidance or suggestions on how to implement this would be greatly appreciated. Thank you!
5 Replies
Any way to detect user inactivity or server timeout or similar things from Solara side? if there is some event or reactive element I could attach to then I suppose I could redirect to the Auth0 logout url, right?
Where is the server running? If it behind a proxy? I doubt it has anything to do with auth0, can you check if the same happens if you don’t use it?
Good point, I'm using a Cloudflare tunnel, could it be related to this?
I could leave a local server instance + local Auth0 authenticated browser open (no cloudflare) to see if I can reproduce the problem.
My guess is that the open websocket gets closed with Cloudflare, but solara should recover from that. Please let us know if you reproduce it locally!
https://community.cloudflare.com/t/cloudflare-websocket-timeout/5865 seems like they have a timeout, could that be it?
Makes sense, thank you!, I will tell you if I can reproduce it.