RobertoSchneiders
I used the mix phx.gen.auth to generate the basic authentication system for my LiveView app. I’m following this security model documentation and one thing I can’t get right at the moment is the disconnect all instances of a live user.
When a user logs out in one browser tab, everything works fine in that tab and sure enough, the other tabs/live view sessions are immediately disconnected, however, on those additional tabs the loading top bar and the “We can’t find the internet. Attempting to reconnect” message is shown. It stays on the screen for about 10s before the redirect is made and the “You must log in to access this page” error is displayed.
I was expecting the redirect to happen immediately and I wasn’t expecting any “attempting to reconnect” messages to show up in this situation.
Is this expected behavior?
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Enabling companies to succeed by building software people love.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #ai
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Practical resources that improve the lives of professional developers.
Develop your skills with books, videos, and courses.
Enabling companies to succeed by building software people love.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
First Post!- Show Best Posts
- Show All Posts (oldest first)
- Show All Posts (newest first)
BradS2S
The section Disconnecting all instances of a live user is going to be helpful.
Phoenix LiveView uses a heartbeat to monitor the websocket connection so when the websocket disconnects, it gives you an error.
So what you do is broadcast to all subscribed live users that they are disconnected.
Most Liked
adw632
But that is what he is doing because he used phx.gen.auth:
It seems the websocket connection handling in liveview javascript is a bit flakey, even on mobile browsers almost always show that annoying “can’t find the internet”, especially when you switch tabs and come back or open and close the device.
Why the need to display this jarring housekeeping message is beyond me, it tarnishes all liveview sites IMO.
RobertoSchneiders
I found a better solution.
Instead of broadcasting the “Disconnect” event I’m subscribing and broadcasting to a reload event that forces a full page reload instead of disconnecting the socket. I left more details in this post