Right, in that case the default PowAssent setup will be all you need.
danschultzer
Pow Core Team
Exadra37
I have installed PowAssent but it forces me to use the traditional User Authentication flow that I said I don’t want to use:
Can it be disabled?
danschultzer
Pow Core Team
Yeah, just remove the Pow registration routes. Then customize the sign in page to only have the social provider links.
Exadra37
Thanks but that doesn’t change the behavior, neither the Pow Assent to disable registration.
Don’t waste more your time with me here… If I decide to go with Pow Assent I will open an issue in Github.
Thanks for your time and being so helpful and quick to reply.
buddhisthead
Hi Dan,
I’ve been using POW since 1.0.18 and it’s been great. I just updated to 1.0.20 so that I can use the persistent sessions. It’s clear for web pages, but I’m using an API for most things and would like to add the 30-day persistent session window to my API routes as well. I started going through the code and got lost. Any hints on how to add this to my session routes would be appreciated. Thanks!
BTW, I read the thread on the new push for mix generated auth; and I’m sticking with POW for my forseeable future - it’s robust and has lots of great features and production integration. Thank you for your work on this.
lud
API routes called from javascript in the browser share the same session cookie as regular HTML routes so you have nothing special to do.
buddhisthead
Thanks, lud. I’m not using Javascript from a browser; it’s being called from a client inside a game using an http client. Do I just need to know the name of the cookie and save it’s value, then return that key/value in the header of a get/post to an API endpoint?
lud
In that case I guess you shoud follow this guide that allows to maintain a token based session. It seems to support persistent sessions too.
Edit: by the way i’m very interested in Elixir gaming. Do you have anything public to show about your game ?
buddhisthead
I’ve followed that guide and it doesn’t discuss long-term persistent tokens (30-day); it appears to address renewable tokens, which require constant refreshing (30-seconds) and won’t be helpful for the case where clients aren’t running for periods of days. For most games requiring authentication, it’s desirable to allow offline access, but have things updated when the connection is available. For this, we use a silent account refresh on game startup, using an authentication token from a previous session. A 30-day “must log back in” is acceptable, as long as we can update the account info on each game startup. That’s needed for things like trial expiration, account blocking, feature updates, user nickname changes, etc.
This game is written in Unity, not elixir. I am just implementing the server side in Elixir/phoenix/pow.
