Local
Last updated
Last updated
local
is the default, general purpose authentication scheme, supporting Cookie
and JWT
login flows.
By default local
scheme is enabled and preconfigured. You can set strategies.local
to false
to disable it.
To do a password based login by sending credentials in request body as a JSON object:
Example for a token based flow:
Example for a cookie based flow:
endpoints
::: tip To disable each endpoint, simply set its value to false
. :::
propertyName
propertyName
can be used to specify which field of the response JSON to be used for value. It can be false
to directly use API response or being more complicated like auth.user
.
tokenRequired
This option can be used to disable all token handling. Useful for Cookie only flows. (Enabled by default)
tokenName
Default: Authorization
Authorization header name to be used in axios requests.
tokenType
Default: Bearer
Authorization header type to be used in axios requests.
autoFetchUser
Default: true
This option can be used to disable user fetch after login.
Each endpoint is used to make requests using axios. They are basically extending Axios .
TIP: It is useful when your login response already have the user. To manually set the user, use .