bobbypriambodo
Hi, I’ve just released my first hex package today (yay!).
Phoenix.Token.Plug is a collection of plugs for Phoenix.Token-based authentication, useful for API calls. It’s a bit like Guardian, but designed to use Phoenix.Token instead of JWT. Currently it only supports verifying Authorization header and ensuring that a request is authenticated, which fits my use case, but there are more available and interesting capabilities yet to be discovered.
Usage instruction is on the GitHub readme. Do give feedbacks, issues, and PRs! 
Where Next?
Trending in Announcing
Other Trending Topics
Latest Phoenix 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
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixir-ls
- #ai
- #elixirconf-us
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
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.
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
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 9- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
OvermindDL1
Awesome! Just need a VerifyCookie to copy the VerifyHeader functionality and it is the basics of what is needed.
OvermindDL1
And a way to customize the assign key to something other than
:useras someone may already use:useror may want multiple lookups.EDIT: And a way to customize the callback function name too on EnsureAuthenticated. ^.^
chrismccord
Very nice! One recommendation I have is the community convention would be to not stomp the Phoenix namespace. So instead of Phoenix.Token.Plug, can you rename your project to
PhoenixToken? Then thePhoenixToken.Plugmodule could be called as normal.bobbypriambodo
@OvermindDL1, thanks for the suggestions! I’ll see what I can do
Oh, I must have missed the convention. My reference for naming it was this point on https://hex.pm/docs/publish:
Since I thought
Phoenix.Token.Pluggives the verifying functionality toPhoenix.Token, that was what I went with. I probably misunderstood that point. I’ll rename it ASAP, thanks for the recommendation!bobbypriambodo
I’ve just published
phoenix_token_plugv0.2.0, which renames the namespace toPhoenixTokenPlug. I figured I might as well merge the.Plugnamespace sincePhoenixTokenwouldn’t have any functionality on its own (and neither wouldPhoenixToken.Plug). I’ve also added the functionality suggestions to the repo’s issues and will tackle it when I have the time.Keep in mind that the API might still be unstable at this point
OvermindDL1
Eeh, you never know, could end up writing more non-plug helpers for it or so. ^.^
/me is a fan of more namespaces.
bobbypriambodo
At least I still have the
I guess we’ll see how it unfolds, naming things is hard.
PhoenixTokenPlugmodule for utility functions, or if it comes to it, possiblyPhoenixTokenPlug.Utils?bobbypriambodo
I have an idea in mind, but I want to make sure first: how do you see this happening? Is it common to put stateless authentication tokens in their cookies, seeing as
Plug.Sessionalready has a solution for putting session data in and storing the key in cookies? And do you think that means we needVerifySessiontoo (seeing as Guardian has one)? It would probably help if you provide some example use cases for itOvermindDL1
A
VerifySessionwould probably make more sense yep.