Defines the processor behavior for handling authentication business logic.

Processors are the business logic hub in KeenAuth's pipeline architecture. They receive normalized user data from mappers and can implement custom validation, user creation, role assignment, auditing, and other business-specific logic.

Pipeline Stage

The processor sits between the mapper and storage in the authentication flow:

Strategy → Mapper → **Processor** → Storage

Flexibility

Processors can be as simple or sophisticated as needed:

• Simple: Pass data through unchanged
• Advanced: Database lookups, validation, user creation, role assignment, auditing

Example Implementation

defmodule MyApp.Auth.Processor do
  @behaviour KeenAuth.Processor

  def process(conn, provider, mapped_user, oauth_response) do
    with {:ok, user} <- find_or_create_user(mapped_user),
         :ok <- validate_permissions(user),
         {:ok, user} <- assign_roles(user, oauth_response) do
      {:ok, conn, user, oauth_response}
    else
      {:error, reason} ->
        conn
        |> put_flash(:error, "Authentication failed")
        |> redirect(to: "/login")
    end
  end

  def sign_out(conn, provider, params) do
    conn
    |> KeenAuth.Storage.delete()
    |> redirect(to: "/")
  end
end

Configuration

Specify your processor in the strategy configuration:

config :keen_auth,
  strategies: [
    azure_ad: [
      processor: MyApp.Auth.Processor,
      # ... other config
    ]
  ]