---
title: "django.contrib.auth"
version: 1.9
locale: id
source: https://docs.djangoproject.com/id/1.9/ref/contrib/auth/
canonical: https://djangodocs.dev/id/1.9/ref/contrib/auth/
---
# `django.contrib.auth`

This document provides API reference material for the components of Django's
authentication system. For more details on the usage of these components or
how to customize authentication and authorization see the [authentication
topic guide](/id/1.9/topics/auth/).

## Model `User`

### Bidang

#### `class models.User`

Obyek [`User`](#id0) mempunyai bidang berikut:

#### `username`

Wajib. 30 karakter atau sedikit. Nama pengguna mungkin mengandung alfanumerik, `_`, `@`, `+`, `.` dan `-` karakter.

#### `first_name`

Pilihan. 30 karakter atau sedikit.

#### `last_name`

Pilihan. 30 karakter atau sedikit.

#### `email`

Pilihan. Alamat email.

#### `password`

Required. A hash of, and metadata about, the password. (Django doesn't
store the raw password.) Raw passwords can be arbitrarily long and can
contain any character. See the [password documentation](/id/1.9/topics/auth/passwords/).

#### `groups`

Hubungan banyak-ke-banyak ke [`Group`](#id5)

#### `user_permissions`

Hubungan banyak-ke-banyak ke [`Permission`](#id2)

#### `is_staff`

Boolean. Designates whether this user can access the admin site.

#### `is_active`

Boolean. Designates whether this user account should be considered
active. We recommend that you set this flag to `False` instead of
deleting accounts; that way, if your applications have any foreign keys
to users, the foreign keys won't break.

This doesn't necessarily control whether or not the user can log in.
Authentication backends aren't required to check for the `is_active`
flag, and the default backends do not. If you want to reject a login
based on `is_active` being `False`, it's up to you to check that in
your own login view or a custom authentication backend. However, the
[`AuthenticationForm`](/id/1.9/topics/auth/default/#django.contrib.auth.forms.AuthenticationForm) used by the
[`login()`](/id/1.9/topics/auth/default/#django.contrib.auth.views.login) view (which is the default)
*does* perform this check, as do the permission-checking methods such
as [`has_perm()`](#django.contrib.auth.models.User.has_perm) and the
authentication in the Django admin. All of those functions/methods will
return `False` for inactive users.

#### `is_superuser`

Boolean. Designates that this user has all permissions without
explicitly assigning them.

#### `last_login`

Tanggalwaktu dari masuk terakhir pengguna.

> **Changed in Django 1.8**
>
> This field will be `null` if the user has never logged in.
> Previously it was set to the current date/time by default.

#### `date_joined`

A datetime designating when the account was created. Is set to the
current date/time by default when the account is created.

### Cara

#### `class models.User`

#### `get_username()`

Returns the username for the user. Since the User model can be swapped
out, you should use  this method instead of referencing the username
attribute directly.

#### `is_anonymous()`

Always returns `False`. This is a way of differentiating
[`User`](#id0) and
[`AnonymousUser`](#django.contrib.auth.models.AnonymousUser) objects.
Generally, you should prefer using
[`is_authenticated()`](#django.contrib.auth.models.User.is_authenticated) to this
method.

#### `is_authenticated()`

Always returns `True` (as opposed to
`AnonymousUser.is_authenticated()` which always returns `False`).
This is a way to tell if the user has been authenticated. This does not
imply any permissions, and doesn't check if the user is active or has
a valid session. Even though normally you will call this method on
`request.user` to find out whether it has been populated by the
[`AuthenticationMiddleware`](/id/1.9/ref/middleware/#django.contrib.auth.middleware.AuthenticationMiddleware)
(representing the currently logged-in user), you should know this method
returns `True` for any [`User`](#id0)
instance.

#### `get_full_name()`

Mengembalikan [`first_name`](#django.contrib.auth.models.User.first_name) ditambah [`last_name`](#django.contrib.auth.models.User.last_name), dengan spasi diantaranya.

#### `get_short_name()`

Mengembalikan [`first_name`](#django.contrib.auth.models.User.first_name).

#### `set_password(raw_password)`

Sets the user's password to the given raw string, taking care of the
password hashing. Doesn't save the
[`User`](#id0) object.

When the `raw_password` is `None`, the password will be set to an
unusable password, as if
[`set_unusable_password()`](#django.contrib.auth.models.User.set_unusable_password)
were used.

#### `check_password(raw_password)`

Returns `True` if the given raw string is the correct password for
the user. (This takes care of the password hashing in making the
comparison.)

#### `set_unusable_password()`

Marks the user as having no password set.  This isn't the same as
having a blank string for a password.
[`check_password()`](#django.contrib.auth.models.User.check_password) for this user
will never return `True`. Doesn't save the
[`User`](#id0) object.

You may need this if authentication for your application takes place
against an existing external source such as an LDAP directory.

#### `has_usable_password()`

Returns `False` if
[`set_unusable_password()`](#django.contrib.auth.models.User.set_unusable_password) has
been called for this user.

#### `get_group_permissions(obj=None)`

Returns a set of permission strings that the user has, through their
groups.

If `obj` is passed in, only returns the group permissions for
this specific object.

#### `get_all_permissions(obj=None)`

Returns a set of permission strings that the user has, both through
group and user permissions.

If `obj` is passed in, only returns the permissions for this
specific object.

#### `has_perm(perm, obj=None)`

Returns `True` if the user has the specified permission, where perm
is in the format `"<app label>.<permission codename>"`. (see
documentation on [permissions](/id/1.9/topics/auth/default/#topic-authorization)). If the user is
inactive, this method will always return `False`.

If `obj` is passed in, this method won't check for a permission for
the model, but for this specific object.

#### `has_perms(perm_list, obj=None)`

Returns `True` if the user has each of the specified permissions,
where each perm is in the format
`"<app label>.<permission codename>"`. If the user is inactive,
this method will always return `False`.

If `obj` is passed in, this method won't check for permissions for
the model, but for the specific object.

#### `has_module_perms(package_name)`

Returns `True` if the user has any permissions in the given package
(the Django app label). If the user is inactive, this method will
always return `False`.

#### `email_user(subject, message, from_email=None, **kwargs)`

Sends an email to the user. If `from_email` is `None`, Django uses
the [`DEFAULT_FROM_EMAIL`](/id/1.9/ref/settings/#std-setting-DEFAULT_FROM_EMAIL). Any `**kwargs` are passed to the
underlying [`send_mail()`](/id/1.9/topics/email/#django.core.mail.send_mail) call.

### Manager methods

#### `class models.UserManager`

The [`User`](#id0) model has a custom manager
that has the following helper methods (in addition to the methods provided
by [`BaseUserManager`](/id/1.9/topics/auth/customizing/#django.contrib.auth.models.BaseUserManager)):

#### `create_user(username, email=None, password=None, **extra_fields)`

Buat, simpan dan mengembalikan [`User`](#id0).

[`username`](#django.contrib.auth.models.User.username) dan [`password`](#django.contrib.auth.models.User.password) disetel sesuai yang diberikan. Bagian ranah dari [`email`](#django.contrib.auth.models.User.email) adalah otomatis mengubah ke huruf kecil, dan mengembalikan obyek [`User`](#id0) akan menyetel [`is_active`](#django.contrib.auth.models.User.is_active) ke `True`.

Jika tidak ada sandi disediakan, [`set_unusable_password()`](#django.contrib.auth.models.User.set_unusable_password) akan dipanggil.

The `extra_fields` keyword arguments are passed through to the
[`User`](#id0)’s `__init__` method to
allow setting arbitrary fields on a [custom User model](/id/1.9/topics/auth/customizing/#auth-custom-user).

Lihat [Membuat pengguna](/id/1.9/topics/auth/default/#topics-auth-creating-users) sebagai contoh penggunaan.

#### `create_superuser(username, email, password, **extra_fields)`

Same as [`create_user()`](#django.contrib.auth.models.UserManager.create_user), but sets [`is_staff`](#django.contrib.auth.models.User.is_staff) and
[`is_superuser`](#django.contrib.auth.models.User.is_superuser) to `True`.

## Obyek `AnonymousUser`

#### `class models.AnonymousUser`

[`django.contrib.auth.models.AnonymousUser`](#django.contrib.auth.models.AnonymousUser) is a class that
implements the [`django.contrib.auth.models.User`](#id0) interface, with
these differences:

- [id](/id/1.9/topics/db/models/#automatic-primary-key-fields) selalu `None`.
- [`username`](#django.contrib.auth.models.User.username) is always the empty
  string.
- [`get_username()`](#django.contrib.auth.models.User.get_username) selalu mengembalikan deretan kalimat kosong.
- [`is_staff`](#django.contrib.auth.models.User.is_staff) dan [`is_superuser`](#django.contrib.auth.models.User.is_superuser) adalah selalu `False`.
- [`is_active`](#django.contrib.auth.models.User.is_active) adalah selalu `False`.
- [`groups`](#django.contrib.auth.models.User.groups) dan [`user_permissions`](#django.contrib.auth.models.User.user_permissions) adalah selalu kosong.
- [`is_anonymous()`](#django.contrib.auth.models.User.is_anonymous) mengembalikan `True` daripada `False`.
- [`is_authenticated()`](#django.contrib.auth.models.User.is_authenticated) mengembalikan `False` daripada `True`.
- [`set_password()`](#django.contrib.auth.models.User.set_password), [`check_password()`](#django.contrib.auth.models.User.check_password), [`save()`](/id/1.9/ref/models/instances/#django.db.models.Model.save) dan [`delete()`](/id/1.9/ref/models/instances/#django.db.models.Model.delete) memunculkan [`NotImplementedError`](https://docs.python.org/3/library/exceptions.html#NotImplementedError).

> **New in Django 1.8**
>
> `AnonymousUser.get_username()` telah ditambahkan ke cermin [`django.contrib.auth.models.User`](#id0) lebih baik.

Dalam penerapannya, anda mungkin tidak butuh menggunakan obyek [`AnonymousUser`](#django.contrib.auth.models.AnonymousUser) anda sendiri, tetapi mereka digunakan oleh permintaan Jaringan, seperti yang dijelaskan di bagian selanjutnya.

## Model `Permission`

#### `class models.Permission`

### Bidang

Obyek [`Permission`](#id2) mempunyai bidang berikut:

#### `class models.Permission`

#### `name`

Dibutuhkan. 255 karakter atau sedikit. Contoh: `'Can vote'`.

> **Changed in Django 1.8**
>
> `max_length` meningkat dari 50 menjadi 255 karakter.

#### `content_type`

Dibutuhkan. Mengacu ke tabel basisdata `django_content_type`, yang mengandung sebuah rekaman untuk setiap model terpasang.

#### `codename`

Dibutuhkan. 100 karakter atau sedikit. Contoh: `'can_vote'`.

### Cara

Obyek [`Permission`](#id2) mempunyai standar cara akses-data seperti lainnya [Django model](/id/1.9/ref/models/instances/).

## Model `Group`

#### `class models.Group`

### Bidang

Obyek [`Group`](#id5) mempunyai bidang berikut:

#### `class models.Group`

#### `name`

Dibutuhkan. 80 karakter atau sedikit. Karakter apapun diizinkan. Contoh: `'Awesome Users'`.

#### `permissions`

Bidang banyak-ke-banyak ke [`Permission`](#id2):

```
group.permissions = [permission_list]
group.permissions.add(permission, permission, ...)
group.permissions.remove(permission, permission, ...)
group.permissions.clear()
```

## Sinyal masuk dan keluar

The auth framework uses the following [signals](/id/1.9/topics/signals/) that
can be used for notification when a user logs in or out.

#### `user_logged_in()`

Sent when a user logs in successfully.

Argumen dikirim dengan dinyal ini:

**`sender`**

  Kelas pengguna yang baru masuk.

**`request`**

  The current [`HttpRequest`](/id/1.9/ref/request-response/#django.http.HttpRequest) instance.

**`user`**

  The user instance that just logged in.

#### `user_logged_out()`

Sent when the logout method is called.

**`sender`**

  As above: the class of the user that just logged out or `None`
  if the user was not authenticated.

**`request`**

  The current [`HttpRequest`](/id/1.9/ref/request-response/#django.http.HttpRequest) instance.

**`user`**

  The user instance that just logged out or `None` if the
  user was not authenticated.

#### `user_login_failed()`

Terkirim ketika pengguna gagal berhasil masuk

**`sender`**

  Nama modul digunakan untuk pengecekan keaslian.

**`credentials`**

  A dictionary of keyword arguments containing the user credentials that were
  passed to [`authenticate()`](/id/1.9/topics/auth/default/#django.contrib.auth.authenticate) or your own custom
  authentication backend. Credentials matching a set of 'sensitive' patterns,
  (including password) will not be sent in the clear as part of the signal.

## Backend pembuktian keaslian

This section details the authentication backends that come with Django. For
information on how to use them and how to write your own authentication
backends, see the [Other authentication sources section](/id/1.9/topics/auth/customizing/#authentication-backends) of the [User authentication guide](/id/1.9/topics/auth/).

### Available authentication backends

The following backends are available in [`django.contrib.auth.backends`](#module-django.contrib.auth.backends):

#### `class ModelBackend`

This is the default authentication backend used by Django.  It
authenticates using credentials consisting of a user identifier and
password.  For Django's default user model, the user identifier is the
username, for custom user models it is the field specified by
USERNAME\_FIELD (see [Customizing Users and authentication](/id/1.9/topics/auth/customizing/)).

It also handles the default permissions model as defined for
[`User`](#id0) and
[`PermissionsMixin`](/id/1.9/topics/auth/customizing/#django.contrib.auth.models.PermissionsMixin).

[`has_perm()`](#django.contrib.auth.backends.ModelBackend.has_perm), [`get_all_permissions()`](#django.contrib.auth.backends.ModelBackend.get_all_permissions), [`get_user_permissions()`](#django.contrib.auth.backends.ModelBackend.get_user_permissions),
and [`get_group_permissions()`](#django.contrib.auth.backends.ModelBackend.get_group_permissions) allow an object to be passed as a
parameter for object-specific permissions, but this backend does not
implement them other than returning an empty set of permissions if
`obj is not None`.

#### `authenticate(username=None, password=None, **kwargs)`

Tries to authenticate `username` with `password` by calling
[`User.check_password`](#django.contrib.auth.models.User.check_password). If no `username`
is provided, it tries to fetch a username from `kwargs` using the
key [`CustomUser.USERNAME_FIELD`](/id/1.9/topics/auth/customizing/#django.contrib.auth.models.CustomUser.USERNAME_FIELD). Returns an
authenticated user or `None`.

#### `get_user_permissions(user_obj, obj=None)`

> **New in Django 1.8**

Returns the set of permission strings the `user_obj` has from their
own user permissions. Returns an empty set if
[`is_anonymous()`](/id/1.9/topics/auth/customizing/#django.contrib.auth.models.AbstractBaseUser.is_anonymous) or
[`is_active`](/id/1.9/topics/auth/customizing/#django.contrib.auth.models.CustomUser.is_active) is `False`.

#### `get_group_permissions(user_obj, obj=None)`

Returns the set of permission strings the `user_obj` has from the
permissions of the groups they belong. Returns an empty set if
[`is_anonymous()`](/id/1.9/topics/auth/customizing/#django.contrib.auth.models.AbstractBaseUser.is_anonymous) or
[`is_active`](/id/1.9/topics/auth/customizing/#django.contrib.auth.models.CustomUser.is_active)  is `False`.

#### `get_all_permissions(user_obj, obj=None)`

Returns the set of permission strings the `user_obj` has, including both
user permissions and group permissions. Returns an empty set if
[`is_anonymous()`](/id/1.9/topics/auth/customizing/#django.contrib.auth.models.AbstractBaseUser.is_anonymous) or
[`is_active`](/id/1.9/topics/auth/customizing/#django.contrib.auth.models.CustomUser.is_active) is `False`.

#### `has_perm(user_obj, perm, obj=None)`

Uses [`get_all_permissions()`](#django.contrib.auth.backends.ModelBackend.get_all_permissions) to check if `user_obj` has the
permission string `perm`. Returns `False` if the user is not
[`is_active`](/id/1.9/topics/auth/customizing/#django.contrib.auth.models.CustomUser.is_active).

#### `has_module_perms(self, user_obj, app_label)`

Returns whether the `user_obj` has any permissions on the app
`app_label`.

#### `class RemoteUserBackend`

Use this backend to take advantage of external-to-Django-handled
authentication.  It authenticates using usernames passed in
[`request.META['REMOTE_USER']`](/id/1.9/ref/request-response/#django.http.HttpRequest.META).  See
the [Authenticating against REMOTE\_USER](/id/1.9/howto/auth-remote-user/)
documentation.

If you need more control, you can create your own authentication backend
that inherits from this class and override these attributes or methods:

#### `RemoteUserBackend.create_unknown_user`

`True` or `False`.  Determines whether or not a
[`User`](#id0) object is created if not already
in the database.  Defaults to `True`.

#### `RemoteUserBackend.authenticate(remote_user)`

The username passed as `remote_user` is considered trusted. This method
simply returns the `User` object with the given username, creating a new
`User` object if [`create_unknown_user`](#django.contrib.auth.backends.RemoteUserBackend.create_unknown_user) is
`True`.

Mengembalikan `None` jika [`create_unknown_user`](#django.contrib.auth.backends.RemoteUserBackend.create_unknown_user) adalah `False` dan obyek `User` dengan nama pengguna yang diberikan tidak ditemukan dalam basisdata.

#### `RemoteUserBackend.clean_username(username)`

Performs any cleaning on the `username` (e.g. stripping LDAP DN
information) prior to using it to get or create a
[`User`](#id0) object.  Returns the cleaned
username.

#### `RemoteUserBackend.configure_user(user)`

Configures a newly created user.  This method is called immediately after a
new user is created, and can be used to perform custom setup actions, such
as setting the user's groups based on attributes in an LDAP directory.
Returns the user object.