Best way to handle actors/roles
Hi everyone! 
We’re working on a multi-app Phoenix project and could use some advice on unifying authorization actors.
We have three apps —
1. A user authenticates with an
2. After login, they choose a role, which becomes their
3. That selected role is the actor.
api_web and console_web → using a custom
* console_web specifically → no DB users; here,
* desk_web → using
Because of this, our shared Ash actions now need to handle both
Is there a recommended way to unify this? Ideally, we’d like a single actor struct that represents both the authenticated
This is how we have the Phoenix assigns atm:
api_web - just standard
desk_web - @current_account (after sign in) and @current_user (after role selector)
console_web - also
We’re working on a multi-app Phoenix project and could use some advice on unifying authorization actors.
Setup
We have three apps —
api_webconsole_webdesk_webAuth Flow
1. A user authenticates with an
Auth.Account2. After login, they choose a role, which becomes their
Auth.User3. That selected role is the actor.
Current Situation
api_web and console_web → using a custom
Auth.ActorAuth.User* console_web specifically → no DB users; here,
Auth.Actortypeadminsupportuser* desk_web → using
ash_authenticationAuth.UserBecause of this, our shared Ash actions now need to handle both
Auth.UserAuth.ActorQuestion
Is there a recommended way to unify this? Ideally, we’d like a single actor struct that represents both the authenticated
AccountUserash_authenticationThis is how we have the Phoenix assigns atm:
api_web - just standard
Ash.PlugHelpers.set_actor(conn, actor)desk_web - @current_account (after sign in) and @current_user (after role selector)
console_web - also
Ash.PlugHelpers.set_actor(conn, actor)
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
Was this page helpful?
