Drop-in authentication support for Phoenix apps using AshAuthentication.
Find a file
2022-12-08 16:02:51 +13:00
.devcontainer chore: set up devcontainer env. 2022-10-25 10:44:50 +13:00
.github chore: add publishing of releases to hex. (#29) 2022-12-08 16:02:51 +13:00
config improvement!: Update to support AshAuthentication 3.x (#27) 2022-12-08 14:32:26 +13:00
dev improvement!: Update to support AshAuthentication 3.x (#27) 2022-12-08 14:32:26 +13:00
lib improvement!: Update to support AshAuthentication 3.x (#27) 2022-12-08 14:32:26 +13:00
test improvement!: Update to support AshAuthentication 3.x (#27) 2022-12-08 14:32:26 +13:00
.doctor.exs feat(PasswordReset): Add password reset support to the UI. (#10) 2022-11-03 16:07:25 +13:00
.formatter.exs feat: UI refresh. (#3) 2022-10-28 20:13:48 +13:00
.gitignore chore: set up dev Phoenix server. 2022-10-25 11:23:05 +13:00
.tool-versions chore: set up devcontainer env. 2022-10-25 10:44:50 +13:00
CHANGELOG.md chore: release version v0.5.0 2022-11-14 23:05:30 +00:00
LICENSE chore: add publishing of releases to hex. (#29) 2022-12-08 16:02:51 +13:00
mix.exs chore: add publishing of releases to hex. (#29) 2022-12-08 16:02:51 +13:00
mix.lock chore: add publishing of releases to hex. (#29) 2022-12-08 16:02:51 +13:00
README.md chore: add publishing of releases to hex. (#29) 2022-12-08 16:02:51 +13:00

AshAuthentication.Phoenix

The ash_authentication_phoenix package extends ash_authentication by adding router helpers, plugs and behaviours that makes adding authentication to an existing Ash-based Phoenix application dead easy.

Installation

The package can be installed by adding ash_authentication_phoenix to your list of dependencies in mix.exs:

def deps do
  [
    {:ash_authentication_phoenix, "~> 0.5.0"}
  ]
end

Usage

This package assumes that you have Phoenix, Ash and AshAuthentication installed and configured. See their individual documentation for details.

This package is designed so that you can choose the level of customisation required. At the easiest level of configuration, you can just add the routes into your router:

defmodule MyAppWeb.Router do
  use MyAppWeb, :router
  use AshAuthentication.Phoenix.Router

  pipeline :browser do
    # ...
    plug(:load_from_session)
  end

  scope "/" do
    pipe_through :browser
    sign_in_route
    sign_out_route MyAppWeb.AuthController
    auth_routes_for MyApp.Accounts.User, to: MyAppWeb.AuthController
  end
end

This will give you a generic sign-in/registration page and store the authenticated user in the Phoenix session.

Customisation

There are several methods of customisation available depending on the level of control you would like:

  1. Use the generic sign-in liveview.
  2. Apply overrides to set your own CSS classes for all components.
  3. Build your own sign-in pages using the pre-defined components.
  4. Build your own sign-in pages using the generated auth routes.

Documentation

Documentation for the latest release will be available on hexdocs and for the main branch.

Contributing

  • To contribute updates, fixes or new features please fork and open a pull-request against main.
  • Please use conventional commits - this allows us to dynamically generate the changelog.
  • Feel free to ask any questions on out GitHub discussions page.

Licence

MIT