BryanJBryce
Ash Authentication – Generated UI and multiple auth Resources
I realize this is pushing the boundaries of tested space for this library, but I’ve got two Auth resources (Admin and User, one is global the other schema-based both with their own token tables) and I’m trying to figure out how to use the generate UI with them, but have them be separated. The default when you do that is this fun UI:
I tried this:
scope "/admin", AppWeb do
pipe_through :browser
auth_routes AdminAuthController, App.Accounts.Admin,
path: "/admin/auth",
sign_in_path: "/admin/sign-in",
register_path: nil,
reset_path: "/admin/reset"
end
scope "/", AppWeb do
pipe_through :browser
# User authentication routes
auth_routes AuthController, App.Accounts.User,
path: "/auth",
sign_in_path: "/sign-in",
register_path: "/register",
reset_path: "/reset"
No dice:
== Compilation error in file lib/app_web/router.ex ==
** (ArgumentError) AshAuthentication.Phoenix.StrategyRouter has already been forwarded to. A module can only be forwarded a single time
(phoenix 1.7.18) lib/phoenix/router/scope.ex:87: Phoenix.Router.Scope.register_forwards/3
(phoenix 1.7.18) lib/phoenix/router/scope.ex:58: Phoenix.Router.Scope.route/8
lib/app_web/router.ex:74: (module)
Trending in Questions
Other Trending Topics
Latest Ash Threads
Latest on Elixir Forum
Sponsor Spotlight
We build reliable cloud platforms for business-critical systems.
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
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #performance
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.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
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 5 of 5 Posts
zachdaniel
Looking into it there are certain kinds of workarounds that could be done:
https://github.com/graphql-elixir/plug_graphql/issues/7
but honestly nothing I can think of that is something that you could apply yourself in this situation. I would first really like to understand why you can’t forward to the same plug multiple times from different routes??
BryanJBryce
Right?!
jimsynz
that is so goddamn weird.
zachdaniel
I’ve pushed something up to main that you can try.
First define a plug that wraps
AshAuthentication.Phoenix.StrategyRouterlike so:then in your second call to
auth_routesaddstrategy_router_plug: MyPlugThatShouldNotBeNecessaryThis seems like a very strange limitation, but this should get you around it. If you wouldn’t mind, a PR with docs for this or an issue reminding us to add some docs around it would be great.
BryanJBryce
I’ll get that done