You don’t have to use Ecto.
You can create your own users context that uses :mnesia rather the Ecto.
But you properly want to use Ecto for the changeset to leverages all the builtin functions and changeset in Pow.
Schultzer
danschultzer
Pow Core Team
Pow was built to use Ecto, but as @Schultzer mentions, you are not bound to Ecto, or using the migrations. Depending what you are looking for you could just create a custom Repo module, but you could also ignore the whole Ecto part of Pow and set up a custom users context. Pow is very flexible here.
Feel free to open an issue on Github if you would like to see some examples of customizations. I would want to see how you currently persist structs in Mnesia to give a more detailed answer.
What @outlog suggests is likely the easiest integration though.
Thanks!
Exadra37
So my current take is to use Mnesia for the persistence layer while still leveraging the Ecto changesets magic, that also requires an ecto schema to be available, thus by your words I should be looking into building a custom repo in order to keep leveraging the Pow Ecto functionality for changesets and schemas?
My current work is in a very earlier phase, thus it doesn’t have any user functionality added into, because I am planning to build it just after I have implemented Authentication and Authorization via some cools library like Pow or similar.
But I can share how I persist the other struct if you want?
danschultzer
Pow Core Team
Yeah, I think that would be the easiest, and you would be able to leverage it with your default Phoenix Ecto setup too.
Looking at ecto3_mnesia, I think it would carry you most of the way though. You don’t need to set up migrations, you just have to ensure that the tables are there. I really like Memento though, would be great with an Ecto adapter built on top of it 
Sure! Feel free to open an issue on Github. I prefer there as it’s easier to track and help others in similar situation.
lud
Hi,
What would be the best strategy for a single page application ? I am looking at the API guide but it feels like reimplementing the whole thing (I know it is not), meaning a lot of code to maintain. Is it the best way for SPAs, especially if we want to build a native android app after the web app is stable ?
In the web app, we would then have to manage the access token and renew it every 30 minutes. And to automatically sign in the day after, we would have stored the renew token, for example, in localstorage which seems a bad practice to me.
So I wonder if there is a better way of doing things, letting pow handle validation, session and auto-login through cookies. We would just have to manage cookies on a native app (or implement the whole API thing) but the web app would be more “standard”.
Thank you
Edit: Maybe that would be add custom controllers who defdelegate everything to the base Pow controller except for respond_create and other “respond” functions. Then I could just return JSON from those functions. Side question: do I need a custom AuthErrorHandler with custom controllers ? In my case yes, to return JSON, but generally speaking ?
danschultzer
Pow Core Team
Yeah, you should still use cookies in this case (keep using Pow.Plug.Session), but set it up with custom controllers. There’s an issue on Github where I’ve put an example for SPA integration: How to get the config for do_delete, do_create? · Issue #353 · pow-auth/pow · GitHub
So kinda the same as the API guide except you don’t need a custom authorization plug, and can keep on using Pow.Plug.Session.
lud
Ok that’s great, and it seems easy. I’ll do the same with registration form. Thank you very much.
Exadra37
Before I start opening issues in Github I need to first decide what one of your repos I will use, because you have so many that I am confused 
I just want to support login with Github, Gitlab , Google and Twitter, and I don’t want to have the traditional user registration where I need to have the registration forms and have to store their passwords, but I want all of the rest that an Authentication and Authorization system have to offer.
So what one should I use?:
- GitHub - pow-auth/pow_assent: Multi-provider authentication for your Pow enabled app · GitHub
- GitHub - pow-auth/assent: Multi-provider framework in Elixir · GitHub
- GitHub - danschultzer/phoenix_oauth2_provider: Get an OAuth 2 provider running in your phoenix with controllers, views and models in just two minutes · GitHub
- or another you may have and I have missed
danschultzer
Pow Core Team
PowAssent would be the right choice, it does everything for you out of the box.
There’s an API guide here, though with SPA it would make most sense just to use the default controller flow as you anyway need to redirect the user: How to use PowAssent in an API — PowAssent v0.4.6
Exadra37
Sorry I should have mentioned that I am still using a Phoenix web application and no API.