phoenix-liveview-auth

Add authentication to Phoenix LiveView by applying on_mount callbacks through live_session groups in your router, centralizing access control and redirecting unauthenticated users from protected sections like dashboards and admin areas.

The mount_current_scope pattern extracts the user scope from the session during the on_mount callback, allowing your LiveView modules to securely access the authenticated user data without scattering auth checks across individual components.

Resolve import conflicts during LiveView authentication by using a dedicated resolver and accessing template variables safely through assigns bracket syntax, preventing naming collisions between your auth modules and existing application code.

Yes, you can use live_session groups in the Phoenix router to apply on_mount authentication handlers to entire sections of your application, securing multiple LiveView routes like forms and dashboards with a single centralized configuration.

You need on_mount for LiveView session security because it intercepts connections at the router level, ensuring consistent access control and user scope extraction before any module mounts, reducing scattered and vulnerable auth checks.

Yes, this on_mount authentication approach works for admin areas built with Phoenix LiveView by applying session-based access control and redirects through live_session groups, ensuring only authenticated users access protected administrative sections.