diff options
| author | Preston Holmes <preston@ptone.com> | 2012-10-04 10:14:50 -0700 |
|---|---|---|
| committer | Preston Holmes <preston@ptone.com> | 2012-10-28 23:04:03 -0700 |
| commit | 4ea8105120121c7ef0d3dd6eb23f2bf5f55b496a (patch) | |
| tree | ae9eccc35bd05c18b1deb44534528e0148a8e0da /docs/topics/auth.txt | |
| parent | f1cc2be0c53858b673afc3b26347d3bb25e424f6 (diff) | |
Fixed #19061 -- added is_active attribute to AbstractBaseUser
Diffstat (limited to 'docs/topics/auth.txt')
| -rw-r--r-- | docs/topics/auth.txt | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/docs/topics/auth.txt b/docs/topics/auth.txt index d261a3c90b..f7a9084008 100644 --- a/docs/topics/auth.txt +++ b/docs/topics/auth.txt @@ -1911,6 +1911,15 @@ password resets. You must then provide some key implementation details: ``REQUIRED_FIELDS`` must contain all required fields on your User model, but should *not* contain the ``USERNAME_FIELD``. + .. attribute:: User.is_active + + A boolean attribute that indicates whether the user is considered + "active". This attribute is provided as an attribute on + ``AbstractBaseUser`` defaulting to ``True``. How you choose to + implement it will depend on the details of your chosen auth backends. + See the documentation of the :attr:`attribute on the builtin user model + <django.contrib.auth.models.User.is_active>` for details. + .. method:: User.get_full_name(): A longer formal identifier for the user. A common interpretation |