mirror of
https://github.com/fastapi-users/fastapi-users.git
synced 2025-08-17 04:26:47 +08:00

* Inject every model variations in router and DB model in DB adapters * Update documentation and import Tortoise in db module * Use path operation decorator dependencies for superuser routes
1.7 KiB
1.7 KiB
User model
FastAPI Users defines a minimal User model for authentication purposes. It is structured like this:
id
(str
) – Unique identifier of the user. Default to a UUID4.email
(str
) – Email of the user. Validated byemail-validator
.is_active
(bool
) – Whether or not the user is active. If not, login and forgot password requests will be denied. Default toTrue
.is_active
(bool
) – Whether or not the user is a superuser. Useful to implement administration logic. Default toFalse
.
Define your models
There are four Pydantic models variations provided as mixins:
BaseUser
, which provides the basic fields and validation ;BaseCreateUser
, dedicated to user registration, which makes theemail
compulsory and adds a compulsorypassword
field ;BaseUpdateUser
, dedicated to user profile update, which adds an optionalpassword
field ;BaseUserDB
, which is a representation of the user in database, adding ahashed_password
field.
You should define each of those variations, inheriting from each mixin:
from fastapi_users import models
class User(models.BaseUser):
pass
class UserCreate(User, models.BaseUserCreate):
pass
class UserUpdate(User, models.BaseUserUpdate):
pass
class UserDB(User, models.BaseUserDB):
pass
You can of course add you own properties there to fit to your needs!
Next steps
Depending on your database backend, database configuration will differ a bit.