It is not 30 seconds but 30 minutes If I read correctly, and I guess you could change that value to something like 24hours, and refresh it when you start the game.
lud
buddhisthead
Ah, right you are - it’s 30 minutes; however that is still short and I don’t want to weaken the session token strategy. The one-time “remember me” cookie is the right tool for the job.
There is nothing public to share on the game server, but it’s not fancy - I’m just storing account information for now. In the future, it will help with cloud services and multi-player access to game data.
lud
Then yes I would accept and send cookies. But really there is no difference between a cookie and a token, both are headers here.
buddhisthead
lud
Sorry I do not have a running app at the moment to check but there is always the docs:
:persistent_session_cookie_key- session key name. This defaults to
“persistent_session”. If:otp_appis used it’ll automatically prepend
the key with the:otp_appvalue.
danschultzer
Pow Core Team
The API guide uses the PowPersistentSession.Store.PersistentSessionCache for renewal tokens which by default lasts 30 days. So all you have to do is to set up your client logic to renew the session with the renewal token when the session token no longer works (as is needed in any case, since the session token only lives for 30 minutes). You are able to renew the session for up to 30 days with the renewal token.
buddhisthead
dimitarvp
I’d like to have a test in my app that creates an unconfirmed user (I have successfully enabled the confirmation module and have manually checked that my setup is working) and then tries to sign in with that. Pow.Plug.assign_current_user and Pow.Operations.authenticate don’t reject it so I am wondering what does?
Code:
# in another file (the ex_machina factory):
def unconfirmed_user_factory do
%User{
email: Faker.Internet.email(),
password: password()
}
end
# in the test file:
@pow_config Application.fetch_env!(:my_app_name, :pow) # the app name is not a typo, just obfuscated after pasting it here.
@email1 "u1@whatever.org"
@pass1 "abcdefghi"
test "sign in with unconfirmed user fails", %{conn: conn} do
conn = Pow.Plug.put_config(conn, @pow_config)
params =
params_for(:unconfirmed_user, %{email: @email1, password: @pass1})
|> Map.merge(%{password_confirmation: @pass1})
{:ok, user} = Pow.Ecto.Context.create(params, [repo: Repo, user: User])
Pow.Operations.authenticate(%{"email" => @email1, "password" => @pass1}, @pow_config)
end
What’s even more puzzling is that the created user has unconfirmed_email equalling nil. email_confirmed_at is nil at least (and there is a value in the email_confirmation_token).
@danschultzer What am I doing wrong? I simply want to have one sanity test in place to catch me if I break the auth system in the future. How would you write a persistent – and non-persistent as well – test that creates an unconfirmed user, tries to sign in with it and properly receives an error?
dimitarvp
Oh well, after some docs and sources reading, the test correctly detects a problem when trying to sign in with an unconfirmed user. Pasting the code for posterity:
@pow_config Application.fetch_env!(:my_app_name, :pow)
@email1 "u1@whatever.org"
@pass1 "asdfghjk"
test "trying to sign in with an unconfirmed user fails", %{conn: conn} do
{:ok, _user} =
Pow.Operations.create(
%{email: @email1, password: @pass1, password_confirmation: @pass1},
@pow_config
)
params = %{"user" => %{"email" => @email1, "password" => @pass1}}
conn = Pow.Plug.put_config(conn, @pow_config)
conn = post(conn, Routes.pow_session_path(conn, :create, params))
err = get_flash(conn, "error")
refute is_nil(err)
end
Basically, don’t forget to put the Pow config in the Plug.Conn. And then search the Phoenix error flash for error(s).
Kurisu
Hey @danschultzer,
Please can you help again with this? I have a plug based on your suggestion that used to work fine until… now I’m having some dyalizer warning:
Function call/2 has no local return.ElixirLS Dialyzer
This is occuring on the line we have
config = Pow.Plug.fetch_config(conn)
After some search I found that Pow.Plug.fetch_config(conn) can return no_config_error() sometimes which result in a no_return() type.
Please, any suggestion on how to get rid of this warning?
Below my custom Plug:
defmodule MyApp.LoadClientProfilePlug do
@doc false
@spec init(any()) :: any()
def init(opts), do: opts
@doc false
def call(conn = %{assigns: %{current_user: user = %{role: "client"}}}, _opts) do
config = Pow.Plug.fetch_config(conn)
preloaded_user = Core.Repo.preload(user, :profile)
conn
|> Pow.Plug.assign_current_user(preloaded_user, config)
end
end