Hi all, A beginner here. I have the following plug code from an example Auth0 repo : def call(conn, _default) do with {:ok, token} when is_binary(token) <- get_token(conn), {:ok, claims} <- Token.verify_and_validate(token) do conn |> assign(:claims, claims) else …

This kind of works until a simple message is first: defp handle_error_response(conn, error) do IO.inspect(error, label: "error") if List.keymember?(error, :message, 0) do Logger.info("Complex: " <> error[:message]) conn |> put_status(401) |> json(%{error: error[:mes…

Got it, but ugly: defp handle_error_response(conn, error) do if is_atom(error) do conn |> put_status(401) |> json(%{error: error}) |> halt() else conn |> put_status(401) |> json(%{error: error[:message], reason: error[:claim]}) |> halt() …

What’s consuming the result of handle_error_response? If you only need error for debugging purposes, this would avoid JSON-encoding headaches: defp handle_error_response(conn, error) do conn |> put_status(401) |> json(%{error: inspect(error)}) |> halt() end Then error in the J…

Just API clients trying to auth using a JWT received from a m2m client creds OAuth 2.0 Auth0 session like so: scope "/api", SentrypeerWeb do pipe_through [:api, :api_authorization] resources "/events", SentrypeerEventController, only: [:create] get "/phone-numbers/:phone_number", Se…

Handling different Joken error messages with json()

Questions & Help Questions

ghenry February 8, 2023, 10:14pm 6

Actually, inspect is a bit messy with the atoms showing etc.