# SAT solver error: (RuntimeError) No SAT solver available

**URL:** <https://forum.elixirforum.com/t/sat-solver-error-runtimeerror-no-sat-solver-available/69505>\
**Category:** Questions\
**Tags:** ash, ash\_authentication\
**Created:** [February 20, 2025, 1:15pm UTC](https://forum.elixirforum.com/t/sat-solver-error-runtimeerror-no-sat-solver-available/69505 "2025-02-20T13:15:58Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![zachdaniel](https://forum.elixirforum.com/user_avatar/forum.elixirforum.com/zachdaniel/32/31980_2.png) [@zachdaniel](https://forum.elixirforum.com/u/zachdaniel)\
**Post date:** [February 20, 2025, 4:22pm UTC](https://forum.elixirforum.com/t/sat-solver-error-runtimeerror-no-sat-solver-available/69505/4 "2025-02-20T16:22:14Z")

</div>

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.

---

_[View the full topic](https://forum.elixirforum.com/t/sat-solver-error-runtimeerror-no-sat-solver-available/69505)._