mirror of
https://github.com/team-alembic/ash_authentication.git
synced 2024-09-19 21:03:23 +12:00
chore(docs): small documentation improvements.
This commit is contained in:
parent
fd54efe85d
commit
2c1802dd69
2 changed files with 2 additions and 2 deletions
|
@ -61,7 +61,7 @@ callbacks for you to manipulate the conn after success or failure.
|
|||
|
||||
If you're using AshAuthentication with Phoenix, then check out
|
||||
[`ash_authentication_phoenix`](https://github.com/team-alembic/ash_authentication_phoenix)
|
||||
which provides route helpers, a controller abstraction and live-view components
|
||||
which provides route helpers, a controller abstraction and LiveView components
|
||||
for easy set up.
|
||||
|
||||
## Authentication Providers
|
||||
|
|
|
@ -24,7 +24,7 @@ defmodule AshAuthentication.TokenRevocation do
|
|||
|
||||
Token revocations are ephemeral, but their lifetime directly correlates to the
|
||||
lifetime of your tokens - ie if you have a long expiry time on your tokens you
|
||||
have to keep the revation records for longer. Therefore we suggest a (semi)
|
||||
have to keep the revocation records for longer. Therefore we suggest a (semi)
|
||||
permanent data layer, such as Postgres.
|
||||
|
||||
## Usage
|
||||
|
|
Loading…
Reference in a new issue