Packages

arke_auth

0.4.5
0.6.0 0.5.0 0.4.5 0.4.4 0.4.3 0.4.2 0.4.1 0.4.0 0.4.0-bulk.1 0.4.0-bulk.0 0.3.5 0.3.4 0.3.3 0.3.2 0.3.1 0.3.0 0.1.18 0.1.17 0.1.16 0.1.15 0.1.14 0.1.13 0.1.12 0.1.11 0.1.10 0.1.9 0.1.8 0.1.7 0.1.6 0.1.5 0.1.4 0.1.3 0.1.2 0.1.1 0.1.0

Arke Auth

HexDocs

Current section

Files

Jump to
Readme
35 Versions
5 Dependencies
Dependants
Files
Activity
arke_auth usage-rules.md
Raw

usage-rules.md 

# Rules for working with ArkeAuth



## Understanding ArkeAuth



ArkeAuth is the identity and authorization layer of the Arke framework. It defines

no storage and no HTTP surface of its own: Users, Members, permissions, OTP codes

and tokens are all ordinary Arke Units and Links, persisted by the configured

persistence layer (usually `arke_postgres`) and exposed over HTTP by `arke_server`.

On top of the Arke data model it layers bcrypt password hashing, two independent

Guardian JWT modules (`ArkeAuth.Guardian` for project-scoped member tokens,

`ArkeAuth.SSOGuardian` for system-wide SSO tokens), a link-based permission model,

OTP codes, temporary tokens and reset-password tokens.



Read the topic rules in `usage-rules/` before using a feature. Do not assume the

API follows common Elixir auth-library conventions — most operations go through

`Arke.QueryManager` and Arke hooks, not through dedicated auth functions.