carlgleisner
Hey 
I’ve read through the posts on using AshAuthentication and multitenancy and couldn’t find an appropriate fit for this.
The title of this post may need massaging if this cannot be written off immediately.
Scenario
Using a clean (generated) slate, I’ve created a new resource Organization which uses the :attribute strategy whereas the User and Token resources have been adapted to use the :context strategy. This is further explained below and also published as a preproduction on GitHub.
Running the registration actions on User with the correct tenant set in AshAdmin, I get an error from Myapp.Accounts.Token.store_confirmation_changes saying:
Queries against the Myapp.Accounts.Token resource require a tenant to be specified
I get the same result from running the code in an iex session (please see the README of the reproduction).
The changes from the generated code are set out in this commit:
This is all set out in the README of reproduction repo, but I paste the pertinent sections of the resources below.
Asking humbly, is there something manifestly wrong with this setup?
Thankful for any input 
The resources
User and Token
multitenancy do
strategy :context
end
Organization
postgres do
table "organizations"
repo Myapp.Repo
manage_tenant do
template ["org_", :subdomain]
create? true
update? false
end
end
multitenancy do
strategy :attribute
attribute :subdomain
global? true
end
To juggle resources using different multitenancy strategies, the Ash.ToTenant protocol introspects the resources and returns either the org_subdomain form or the attrubute subdomain.
defimpl Ash.ToTenant do
def to_tenant(%{subdomain: subdomain}, resource) do
if Ash.Resource.Info.data_layer(resource) == AshPostgres.DataLayer &&
Ash.Resource.Info.multitenancy_strategy(resource) == :context do
"org_#{subdomain}"
else
subdomain
end
end
end
Perhaps it is worth noting that the :subdomain attribute on Organization is of the type :ci_string.
attribute :subdomain, :ci_string do
public? true
allow_nil? false
end
Where Next?
Trending in Questions
Other Trending Topics
Latest Ash Threads
Latest on Elixir Forum
Sponsor Spotlight
Supporting innovation across the BEAM ecosystem.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
zachdaniel
Hey! Could you try
mainof both ash_authentication and ash_authentication_phoenix?carlgleisner
Of course
But no mas unfortunately, same error with:
zachdaniel
Good to know thanks
can you share the full error output including the stack trace?
carlgleisner
zachdaniel
can you try
mainagain? Withmix deps.update ash_authenticationcarlgleisner
I just did but I’m sorry it is the same, see stack trace below.
Also committed and pushed it to the reproduction.
zachdaniel
No problem, will take a look in the morning thanks!
zachdaniel
Investigating now, just want to say thank you for such a detailed and useful reproduction
zachdaniel
I feel bad, I just didn’t push the fix up properly last night
Only had a few and didn’t realize that the push failed. Anyway, fixed in main, will be released next week 
carlgleisner
Many thanks Zach!
Happy Friday