michaelwa
I am very new to the Ash Framework. I did buy the book and I have gone up through the chapter on testing. I am very excite about the prospects, and it is time to start playing with it.
However, I am not sure what to do with Ash Authentication. I have some very strict compliance rules and I do not see a way to modify the “User” resource. There are some articles on customizing Ash Authentication but they mostly revolve around the Phoenix layer not concerned with modifying the base business logic that I believe should be embedded in the “User” resource. Below is a mostly representative sequence diagram of the “login” workflow.
Is there a guide that covers this topic I have not uncovered yet? Or is there something simple in the base documentation I am not understanding for making these kinds of changes?
Where Next?
Trending in Questions
Other Trending Topics
Latest Ash Threads
Latest on Elixir Forum
Sponsor Spotlight
Error tracking, logs, APM, uptime and cron monitoring in one dev-friendly platform. Find and fix problems before your users notice.
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
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #elixirconf-eu
- #metaprogramming
- #hex
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.
Practical resources that improve the lives of professional developers.
**Building the future of software with AI, trust, and human connection.**
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Marked As Solved- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
zachdaniel
I wouldn’t be too attached to AshAuthentication. AshAuthentication is a way for us to provide pre-built variations of authentication easily. There is nothing wrong with using “regular” actions/resources and powering the flow yourself. You can very likely make modifications to the actions that underpin AshAuthentication, (i.e you should see actions in your user resource like
sign_in_with_passwordandregister_with_passwordthat you are free to customize, thats why we generate them into your app), but at the end of the day if you’re worried about being able to rigidly prove that your app behaves to some specific requirement or specification, you may be better off not using AshAuthentication at all. Perhaps it just adds value while prototyping and later you replace it with your own tooling etc.Last Post!
zachdaniel
That is an eventual goal (well, generate liveviews most likely, potentially inert views after). With that said, it’s mot very complex to define your own. The actions etc are all usable from anywhere like any standard action.