SAT solver error: (RuntimeError) No SAT solver available

Ash Forum Ash Questions / Help
,
1

I’m having trouble integrating ash_authentication with the magic_link strategy. The igniter.install generator, which defaults to installing picosat_elixir, is causing a problem with the token module. I’m encountering the following error:

Elixir: an exception was raised:
    ** (RuntimeError) No SAT solver available, although one was loaded.

This typically means that you need to run `mix deps.compile ash --force`

I’ve already tried mix deps.compile and even installed simple_sat before running the command again, but the error persists. How can I resolve this?

2

You did the full recommended task? mix deps.compile ash --force? Barring that, you could rm -rf _build and then recompile.

1 Like
3

Yes, I did try recompiling dependencies. I also forgot to mention that I’d already attempted that. It seems the error was a false positive from ElixirLS. Thanks again, Zach!

I have another question, if you don’t mind. I’m trying to integrate Inertia.js with ash_authentication using the magic_link strategy, and I’m running into two issues:

  1. I removed the sign_in_route method from the router to use a custom Inertia view, Login.tsx. This is a simple React component that makes a POST request to "/auth/user/magic_link/request". However, when I submit the form, ash_authentication attempts to redirect to /sign-in. Is there a way to integrate with Ash without using Ash LiveView? Not sure if i saw a concrete example somewhere in the docs

  2. The User resource generator created a policy that appears to only allow Ash internals to trigger the magic link actions. Is it safe or recommended to remove this policy? If not, how can I interact with these actions myself?

Thanks for your help and quick responses. Apologies for the slightly off-topic questions.

4
  1. You should definitely be able to leverage AshAuthentication’s actions without using our live views. I’m not sure what specifically is going wrong there, but typically any redirecting like that happens in your auth_controller.ex so it should be something you can change as necessary.
  2. That policy doesn’t only allow AA to call those actions, it just creates a bypass that always allows it in addition to whatever you allow in your policies. So you should leave that policy and do one of the following:
    a. Set the context %{ash_authentication?: true} on your requests so that the bypass is hit
    b. you can create your own copy of that bypass and add it alongside the ash authentication one, using a different key
    c. create a special actor, called something like %Authenticator{}, and write a custom simple check (like the one builtin to AA) that allows that actor to do whatever actions it wants.
5

I’ll give more context about the first item, basically Inertia provides a render_inertia function to render react (in my case) components, and on the client side i should be able to dispatch to an action with this snippet:

  const { data, setData, post } = useForm({
    email: ''
  })

  function submit(e: FormEvent) {
    e.preventDefault()
    post('/auth/user/magic_link/request')
  }

There’s two problems with that approach:

  1. Apparently auth/user/magic_link/request expect a body like: %{"user" => %{"email" => email} and inertia sends only %{"email" => email}. Also, looks like somewhere in ash have a redirect to /sign-in when i dispach a post this way, but the route do not exists since i removed to use my own views.

  2. Which leaves me to the second approach that i tried to solve this, create an endpoint post /login and manually interact with magic link ash modules at phoenix controller side, but i still cannot get it.

I know that with live view i could use the AshPhoenix.Form to trigger the magic link request action, but i’m not sure how would i do this in dead views with inertia

6

@zachdaniel don’t worry, i got it, i was trying to trigger the plug from MagicLinkStrategy but i should just trigger the action instead as this part of MagicLink module docs suggests. Thanks anyway for trying to help me with this

  By default the magic link strategy will automatically generate the request and
  sign-in actions for you, however you're free to define them yourself.  If you
  do, then the action will be validated to ensure that all the needed
  configuration is present.

  If you wish to work with the actions directly from your code you can do so via
  the `AshAuthentication.Strategy` protocol.

  ### Examples

  Requesting that a magic link token is sent for a user:

      iex> strategy = Info.strategy!(Example.User, :magic_link)
      ...> user = build_user()
      ...> Strategy.action(strategy, :request, %{"username" => user.username})
      :ok
1 Like