Hi @gordoneliel

So, looking at the code to refresh my memory, it seems that by default the primary key is the JTI, which is unique to every token so I don’t know how you could possibly be getting a conflict. Additionally, you can provide an alternative “purpose” for the token (defaults to "user") by passing the purpose option to token_for_user/3.

What I would probably do is customise your AuthController/AuthPlug success callback and have it ignore the auto-generated token and generate a new token with the claims you want.

I tried doing that, and going the full custom routes as well, but unfortunately the code for creating a token looks into the resource to check whether to store the token or not. If I leave it on, it works, but creates a duplicate token for one login request. If I turn off store_all_tokens? then nothing gets stored in the db.

  defp maybe_store_token(token, resource, user, purpose, opts) do
    if Info.authentication_tokens_store_all_tokens?(resource) do
      with {:ok, token_resource} <- Info.authentication_tokens_token_resource(resource) do
        TokenResource.Actions.store_token(
          token_resource,
          %{
            "token" => token,
            "purpose" => to_string(purpose)
          },
          Keyword.put(opts, :context, %{
            ash_authentication: %{
              user: user
            }
          })
        )
      end
    else
      :ok
    end
  end

Just to clarify, I’m not getting a conflict, what happens is that two tokens get created every time a user signs in

Ahhhh! I see. I thought you were running into a database constraint.

I think we could add a behaviour or callback to token generation that lets you modify the claims.