Kabawo
Hi. I am new to Elixir and I’m trying to build a REST api as a hobby/ learning project. The recommendation I found in the forums for implementing auth is to go the phx.gen.auth route and amend as necessary to suit REST workflow (I suspect Phoenix.Token would be of help here). Because I generated the project with --no-html --no-assets flags it seems the phx.gen.auth is not available. Can I ask what is the recommended solution in such case? Would I have to add html (I wanted to keep the project lean)? Would I build the auth from scratch using Phoenix.Token (I imagine as a plug)? Or maybe this is too much to implement and properly set up for a beginner? I am not a commercial programmer and I’ve had limited exposure to auth implementations (Python Flask, Flask-RESTful and FastAPI) and following the guides and sample/ toy projects for these technologies adding auth seemed fairly trivial (with the complexity hidden within libraries), so I am quite surprised to hit a bit of a roadblock in Phoenix. Thanks in advance for any help
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Bringing learning, work and compliance together since 1987.
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.
Producing high quality Elixir screencasts since 2017.
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!"
Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
100phlecs
The sooner you get acquainted with Plug and its functions the better off you’ll be, as you’ll see how Phoenix builds on-top of it.
So yes, you would build the Auth from scratch with a Plug using Phoenix.Token.
Here are some guides that I think would be useful as reference.
If you don’t want to roll your own, then guardian may be what you’re interested in using, which can hide some of the implementation details like the previous languages you’ve worked with.
There are other auth libraries to use as well. I can’t vouch for any of them. I’ve not used Guardian before, but looking around the forum Guardian is the one I see come up.
Kabawo
Thanks for a quick response and the necessary resources.
I did come across guardian and some other propositions, but I think I’ve read Jose Valim saying that in this case the best library is no library (hence the auth generator). My only worry was that as a noob I may miss on some edge cases building it from scratch as a Plug. I guess I will give it a try and I’ll treat guardian as a fallback alternative.
Thanks for help