Ash Auth For Inertia Setup & Ash Auth vs Ash Phoenix Auth
Hi everyone! So I have been playing with the
a) Am I losing anything if I don't use Ash Auth yet if I already has my auth configured from the phx.gen.auth since I can just pass the right scope for the actors when using Ash? I am migrating my models to Ash resources now but I need to understand how the ash auth works in tandem with the ash resources as a whole.
b) For the auth vs phoenix auth, I assume phoenix auth is just the UI/liveview + routes scope on top of the ash auth? I can still build my own routes with Inertia rendering and use the auth module to trigger the auth internally right?
Thank you so much for your time in reading this :ash:
mix phx.gen.autha) Am I losing anything if I don't use Ash Auth yet if I already has my auth configured from the phx.gen.auth since I can just pass the right scope for the actors when using Ash? I am migrating my models to Ash resources now but I need to understand how the ash auth works in tandem with the ash resources as a whole.
b) For the auth vs phoenix auth, I assume phoenix auth is just the UI/liveview + routes scope on top of the ash auth? I can still build my own routes with Inertia rendering and use the auth module to trigger the auth internally right?
Thank you so much for your time in reading this :ash:
Solution
you can just use your generated auth, Ash doesn't really care to much about what you pass in as an actor, your policies just need to know how to work with it. I've used ash with our own custom auth before ash_authentication was a thing, worked without a hitch.
The Elixir backend framework for unparalleled productivity. Declarative tools that let you stop wasting time. Use with Phoenix LiveView or build APIs in minutes for your front-end of choice.
2,193Members
Resources
Similar Threads
Was this page helpful?
