Apparently somebody has written some blog posts about the libraries, and he liked Phauxth the most: Blog
SZJX
danschultzer
Pow Core Team
So I’ve been working on a solution myself since nothing really worked that well for my team. Coherence is the closest to a full feature authentication solution, but it has been built like a Rails monolith app which handles poorly in our elixir environment.
I took the approach to make a library that’s both modular and as plug n’ play as possible. It took much longer to build than I anticipated, but I think it has a strong foundation that will make it easy to work with and expand upon.
I would love to get some feedback to prepare for the 1.0.0 release. We got one app running in production with Pow (switched from Coherence). I’ll probably do the full release next month when we’ve deployed a second app with Pow to production.
https://forum.elixirforum.com/t/pow-robust-modular-extendable-user-authentication-and-management-system/15807
https://github.com/danschultzer/pow
There’s also PowAssent for multi-provider auth (OAuth, OAuth2, etc).
11
jpinnix
@danschultzer What are the advantages of Pow over Guardian? For example, I noticed there is the ability to utilize Guardian for the session plug (https://github.com/danschultzer/pow#authorization-plug), but why not just use Guardian instead of Pow in that case?
0
danschultzer
Pow Core Team
They don’t compare as Pow provides the whole user registration framework (ecto schema, phoenix controller/templates), while Guardian is an authentication library. Pow has built-in session based authentication, that can be replaced with Guardian or you own custom authentication.
So if you use Pow, then almost all the steps in the get started tutorial in Guardian is taken care of by Pow: guardian/guides/tutorial/start-tutorial.md at 9addcdfc523828cf7eb21ee6bc78c91e9156e1c4 · ueberauth/guardian · GitHub
Pow also has password reset, email confirmation, “remember me” and multi-provider extensions. Pow is built to make it faster, easier and more secure for developers to add user registration to their app, while keeping it easy to customize (e.g. using Guardian JWT for authentication).
4
jpinnix
Thanks for the clarification!
Also, after thinking about this the last few days, I’ve decided to go with the default Pbkdf2 hashing 
for the project I’m working on right now. I had asked you about Argon2 for a potential project that would require it. Glad to see you dropped in those instructions on the README.
2
Owens
@danschultzer I see you created phoenix_oauth2_provider, kudos.
Curious what the difference is with this and the popular OAuth2?
I’d like to use something that easily connects with pow.
Owens
Thanks Dan.
What I want to do is build a mobile app that can access data from my API/backend. Not interested in Twitter/Facebook/Google login.
danschultzer
Pow Core Team
In that case, then yeah, you can use PhoenixOauth2Provider for that. There is no extra configuration necessary to get it to work with Pow since the provider library works independently.
Owens
Thanks. I’m still confused the difference between OAuth2 and PhoenixOauth2Provider though, what to use one for vs the other. This is relatively new territory for me.