gushonorato

Hey everyone!

I’m excited to share a new library with you all: Magic Auth! It’s an authentication library for Phoenix projects that aims to make your life as a developer easier by offering an authentication solution with minimal setup effort.

Why I Built Magic Auth

While phx.gen.auth is amazing, it can require a significant amount of time to implement all the necessary flows, such as password resets, recovery screens, and UI customization. Magic Auth is designed to simplify authentication, requiring virtually the same minimal effort as implementing a BASIC HTTP authentication flow, but with much more power!

What Magic Auth Brings to the Table

Here’s a quick rundown of the key features:

• Ship Faster : No time wasted configuring password resets and recovery flows—just implement and ship your product.

• Passwordless Authentication : Secure login process through one-time passwords sent via email. One-time passwords are better than magic links because users can receive the code on one device (e.g., phone email) and enter it on another (e.g., desktop browser).

• Enhanced Security : Protect your application from brute force attacks with built-in rate limiting and account lockout mechanisms.

• Customizable Interface : Use the beautiful default UI components out of the box, or customize them fully to match your design perfectly.

• Effortless Configuration and Comprehensive Documentation : Quick and simple integration with your Phoenix project, with detailed guides and references to assist you through every step of the integration process.

• Schema Agnostic : Implement authentication without requiring a user schema—ideal for everything from MVPs to complex applications.

Why This Matters

I’m deeply passionate about making the Elixir/Phoenix ecosystem the go-to choice for building MVPs and startups. I truly believe Elixir and Phoenix have unmatched potential for speed, scalability, and developer happiness.

Authentication can often be a roadblock, especially when you’re moving fast to validate ideas or launch a product. Magic Auth removes that friction so you can spend less time on boilerplate and more time building something awesome.

Check out Magic Auth on GitHub: GitHub - gushonorato/magic_auth: An Elixir authentication library designed for effortless setup. · GitHub. Give it a try, and let me know your thoughts! Your feedback can help shape Magic Auth into an even better tool for the community.

Let’s make the Elixir/Phoenix ecosystem the best place to build startups and MVPs.

Cheers,
Gustavo

P.S. Feel free to ask questions or share your thoughts. I’d love to hear how Magic Auth can help your projects!

https://github.com/gushonorato/magic_auth

12 comments

#library #magic_auth

44 2619 12

2026-09-24 22:23:21 UTC

Showing Posts 1 to 10

Show Best Posts
Show All (oldest first)
Show All (newest first)

nix2intel

Will this support totp in the future where i can setup a phone or passkey for auth? Looks amazing btw.

Post #2

gushonorato

Thank you for your feedback! I believe that with just a few modifications, I can add support for sending TOTP to a phone instead of email. Could you please open an issue on GitHub describing your use case?

Post #3

nix2intel

Did so, and seriously great work!

Post #4

3even

Very impressed with the quality of your code, comments and documentation. Thank you!

Post #5

Wojciech

Amazing! Magic auth is exactly what i imagined the perfect auth library to be.

Thanks for your great work!

Post #6

gushonorato

[Release] Version 0.1.1 – Important Security Fix

Hello everyone,

We’ve just released version 0.1.1, and we strongly recommend updating to this latest version as it includes a critical security fix.

[0.1.1] - 2025-01-29

Fixed

One-time passwords are not being deleted after verified, allowing them to be reused multiple times until they expire.

Please update as soon as possible and let us know if you have any feedback!

Thanks for your support!

Post #7

sreyansjain

Great work. Congratulations and Thank you.
Do you have any guide about using Magic Auth without liveview?
I wan’t to use Magic Auth with phoenix controllers and (dead) views. Please advise.

Post #8

gushonorato

Hey! Unfortunately, Magic Auth does require LiveView. However, adding support for “dead views only projects” isn’t too difficult. Could you please open an issue on GitHub so we can continue the discussion there? If possible, provide details about your use case in the issue.

Post #9

gushonorato

Release 0.2.0

Hey everyone! I’m excited to announce the release of Magic Auth v0.2.0, packed with several improvements and new features.

Enhancements

Multi-tenancy support via query prefixes and foreign keys.
Improved error messaging when mix magic_auth.install fails to inject code into the necessary files.
You can now return a tuple like {:allow, user_id} from the log_in_requested/1 callback. Magic Auth will store the user ID in %Session{user_id: user_id}, and fetch_magic_auth_session/2 will automatically load and assign the user to :current_user.
Default logging for success and error messages in the generated email-sending code.
New test helpers to streamline testing. Check out the Testing Guide for details.

This version includes breaking changes. Make sure to review the Changelog for migration instructions.

Post #10

mindreframer

I wanted to use Magic Auth for an app, that requires different Auth routers for different users. As it is right now, it was not possible to implement. The configuration is a global singleton.

To solve it I have used the ProcessTree package, which allows quasi-global configuration per request. Liveviews required some special treatment with on_mount callbacks. But it seems to be working quite OK right now in my local setup.

Here is the branch on the fork: