bobfp

bobfp

Hi everyone,

I’m migrating a Magic Link authentication flow from Phoenix LiveView to a SolidJS SPA using Ash TypeScript, and I’m stuck on retrieving the authentication token.

Background

  • Using AshAuthentication’s built-in magic link resources (which worked perfectly out-of-the-box with LiveView)

  • Now building a JS SPA (SolidJS) that needs to interact with the same backend via the RPC client

  • The LiveView implementation handled the token automatically, but I want to manage it manually in the SPA

What I’m trying to do

Recreate the same Magic Link flow in my SPA:

  1. User requests a magic link via email

  2. User clicks the link and is authenticated

  3. The app receives and stores the authentication token for subsequent API calls

Current status

:white_check_mark: Successfully requesting the magic link using AshAuthentication’s request_magic_link action
:white_check_mark: Successfully calling the sign-in-with-magic-link action
:cross_mark: Cannot retrieve the authentication token after sign-in to store it client-side

The problem

From what I can tell, the token appears to be returned via metadata in the response, but the RPC client doesn’t seem to expose this metadata (or I’m not accessing it correctly).

Question

  1. How do I access response metadata (specifically the auth token) from AshAuthentication’s magic link sign-in action through the RPC client?

  2. Is there a different pattern I should be following when using AshAuthentication with a JS SPA instead of LiveView?

Any guidance on properly handling AshAuthentication tokens in a decoupled frontend would be greatly appreciated!

Showing Posts 1 to 2

zachdaniel

zachdaniel

Creator of Ash

Ah…right. I think the RPC client may need to be updated to support displaying metadata in its results. You’ll need to open an issue for this :smiley:

bobfp

bobfp OP

No worries, will do.
For anyone else that has a similar issue, I found a workaround by getting the token in a calculation:

defmodule FastricaServer.Accounts.User.Calculations.CurrentToken do
  @moduledoc """
  Calculation that retrieves the current authentication token for a user.

  This queries the Token resource to find the most recent valid token
  for the user, which is set during authentication via the sign_in_with_magic_link action.
  """
  use Ash.Resource.Calculation

  @impl true
  def calculate(records, _opts, _context) do
    # For each user record, generate a fresh JWT token
    Enum.map(records, fn user ->
      case AshAuthentication.Jwt.token_for_user(user, %{
        "purpose" => "user"
      }) do
        {:ok, jwt_token, _claims} -> jwt_token
        _ -> nil
      end
    end)
  end

  @impl true
  def load(_query, _opts, _context) do
    # No additional data needs to be loaded
    []
  end
end
— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
kpanic
Hi everyone, I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding. I sta...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
asweet-confluent
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
apz
I’m new to elixir and just tried to install the elixirLS extension for VScode(ium) and it is throwing some errors that I would like help ...
New

Other Trending Topics Top

JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews