I was able to find it in the docs, for future reference to anyone else looking: Update cached user credentials — Pow v1.0.39
dcrck
why
mohandass-pat
I can able to setup invitation create user flow in API. But I’m struggling to create Invitation accept flow. How to do that. Any examples on accept invitation flow would be great.
danschultzer
Pow Core Team
It depends how your API works, but the plug module should have all the methods you need to set it up yourself: PowInvitation.Plug — Pow v1.0.39
I don’t have any example of invitation in API, but feel free to create an issue at GitHub - pow-auth/pow: Robust, modular, and extendable user authentication system · GitHub to discuss solutions, and write out examples.
dcrck
Hi @danschultzer,
I have Ecto in a separate application from Phoenix. Is there a way to bring in the schema for Pow and its extensions without having to install all the dependencies (Phoenix, etc.), or should I just define the Pow-related schema and changesets manually in my User module?
danschultzer
Pow Core Team
No, but it’s actually the oldest PR I’ve been working on. Would love for all dependencies to be optional. When I looked at it back then it didn’t work though. Is this an entirely different app, or is it an umbrella project? I don’t believe it’s an issue in an umbrella project since dependencies are shared.
dcrck
danschultzer
Pow Core Team
I can’t think of any way of doing it short of copying all necessary modules. You can try out the optional-deps branch: {:pow, github: "danschultzer/pow", ref: "optional-deps"}. Obviously it’s highly experimental. What it does is that at compile time it excludes groups of modules based on which dependency is available. I’m curious if it works for you.
Edit: Feel free to continue the discussion in Add optional dependency load by danschultzer · Pull Request #2 · pow-auth/pow · GitHub if it works.
rrosztoczy
Hello, I am utilizing Pow in an umbrella app. I have two custom user schemas and a custom context module all in the same application. It seems like at the moment this means that I need to have two separate custom context modules, rather than one, because the using macro opts for Pow.Ecto.Context specifies only a single user module. I was curious if there was a way to configure the user module that the context references more dynamically based on which application hits the application hits the context module?
danschultzer
Pow Core Team
I was curious if there was a way to configure the user module that the context references more dynamically based on which application hits the application hits the context module?
It’s possible if you are able to tell what struct to use based on the params, but you’ll have to override all the methods. Also in this case you should just use the @behaviour instead of the macro.
Feel free to open an issue on github to share your setup, there may be alternatives depending on your exact use case.