django.contrib.authLink to this heading#This document provides API reference material for the components of Django's\nauthentication system. For more details on the usage of these components or\nhow to customize authentication and authorization see the authentication\ntopic guide.
\nUserLink to this heading#Obyek User mempunyai bidang berikut:
Wajib. 30 karakter atau sedikit. Nama pengguna mungkin mengandung alfanumerik, _, @, +, . dan - karakter.
Pilihan. 30 karakter atau sedikit.
\nPilihan. 30 karakter atau sedikit.
\nPilihan. Alamat email.
\nRequired. A hash of, and metadata about, the password. (Django doesn't\nstore the raw password.) Raw passwords can be arbitrarily long and can\ncontain any character. See the password documentation.
\nHubungan banyak-ke-banyak ke Group
Hubungan banyak-ke-banyak ke Permission
Boolean. Designates whether this user can access the admin site.
\nBoolean. Designates whether this user account should be considered\nactive. We recommend that you set this flag to False instead of\ndeleting accounts; that way, if your applications have any foreign keys\nto users, the foreign keys won't break.
This doesn't necessarily control whether or not the user can log in.\nAuthentication backends aren't required to check for the is_active\nflag, and the default backends do not. If you want to reject a login\nbased on is_active being False, it's up to you to check that in\nyour own login view or a custom authentication backend. However, the\nAuthenticationForm used by the\nlogin() view (which is the default)\ndoes perform this check, as do the permission-checking methods such\nas has_perm() and the\nauthentication in the Django admin. All of those functions/methods will\nreturn False for inactive users.
Boolean. Designates that this user has all permissions without\nexplicitly assigning them.
\nTanggalwaktu dari masuk terakhir pengguna.
\n\nA datetime designating when the account was created. Is set to the\ncurrent date/time by default when the account is created.
\nReturns the username for the user. Since the User model can be swapped\nout, you should use this method instead of referencing the username\nattribute directly.
\nAlways returns False. This is a way of differentiating\nUser and\nAnonymousUser objects.\nGenerally, you should prefer using\nis_authenticated() to this\nmethod.
Always returns True (as opposed to\nAnonymousUser.is_authenticated() which always returns False).\nThis is a way to tell if the user has been authenticated. This does not\nimply any permissions, and doesn't check if the user is active or has\na valid session. Even though normally you will call this method on\nrequest.user to find out whether it has been populated by the\nAuthenticationMiddleware\n(representing the currently logged-in user), you should know this method\nreturns True for any User\ninstance.
Mengembalikan first_name ditambah last_name, dengan spasi diantaranya.
Mengembalikan first_name.
Sets the user's password to the given raw string, taking care of the\npassword hashing. Doesn't save the\nUser object.
When the raw_password is None, the password will be set to an\nunusable password, as if\nset_unusable_password()\nwere used.
Returns True if the given raw string is the correct password for\nthe user. (This takes care of the password hashing in making the\ncomparison.)
Marks the user as having no password set. This isn't the same as\nhaving a blank string for a password.\ncheck_password() for this user\nwill never return True. Doesn't save the\nUser object.
You may need this if authentication for your application takes place\nagainst an existing external source such as an LDAP directory.
\nReturns False if\nset_unusable_password() has\nbeen called for this user.
Returns a set of permission strings that the user has, through their\ngroups.
\nIf obj is passed in, only returns the group permissions for\nthis specific object.
Returns a set of permission strings that the user has, both through\ngroup and user permissions.
\nIf obj is passed in, only returns the permissions for this\nspecific object.
Returns True if the user has the specified permission, where perm\nis in the format "<app label>.<permission codename>". (see\ndocumentation on permissions). If the user is\ninactive, this method will always return False.
If obj is passed in, this method won't check for a permission for\nthe model, but for this specific object.
Returns True if the user has each of the specified permissions,\nwhere each perm is in the format\n"<app label>.<permission codename>". If the user is inactive,\nthis method will always return False.
If obj is passed in, this method won't check for permissions for\nthe model, but for the specific object.
Returns True if the user has any permissions in the given package\n(the Django app label). If the user is inactive, this method will\nalways return False.
Sends an email to the user. If from_email is None, Django uses\nthe DEFAULT_FROM_EMAIL. Any **kwargs are passed to the\nunderlying send_mail() call.
The User model has a custom manager\nthat has the following helper methods (in addition to the methods provided\nby BaseUserManager):
Buat, simpan dan mengembalikan User.
username dan password disetel sesuai yang diberikan. Bagian ranah dari email adalah otomatis mengubah ke huruf kecil, dan mengembalikan obyek User akan menyetel is_active ke True.
Jika tidak ada sandi disediakan, set_unusable_password() akan dipanggil.
The extra_fields keyword arguments are passed through to the\nUser’s __init__ method to\nallow setting arbitrary fields on a custom User model.
Lihat Membuat pengguna sebagai contoh penggunaan.
\nSame as create_user(), but sets is_staff and\nis_superuser to True.
AnonymousUserLink to this heading#django.contrib.auth.models.AnonymousUser is a class that\nimplements the django.contrib.auth.models.User interface, with\nthese differences:
id selalu None.
username is always the empty\nstring.
get_username() selalu mengembalikan deretan kalimat kosong.
is_staff dan is_superuser adalah selalu False.
is_active adalah selalu False.
groups dan user_permissions adalah selalu kosong.
is_anonymous() mengembalikan True daripada False.
is_authenticated() mengembalikan False daripada True.
set_password(), check_password(), save() dan delete() memunculkan NotImplementedError.
Dalam penerapannya, anda mungkin tidak butuh menggunakan obyek AnonymousUser anda sendiri, tetapi mereka digunakan oleh permintaan Jaringan, seperti yang dijelaskan di bagian selanjutnya.
PermissionLink to this heading#Obyek Permission mempunyai bidang berikut:
Dibutuhkan. 255 karakter atau sedikit. Contoh: 'Can vote'.
Dibutuhkan. Mengacu ke tabel basisdata django_content_type, yang mengandung sebuah rekaman untuk setiap model terpasang.
Dibutuhkan. 100 karakter atau sedikit. Contoh: 'can_vote'.
Obyek Permission mempunyai standar cara akses-data seperti lainnya Django model.
GroupLink to this heading#Obyek Group mempunyai bidang berikut:
Dibutuhkan. 80 karakter atau sedikit. Karakter apapun diizinkan. Contoh: 'Awesome Users'.
Bidang banyak-ke-banyak ke Permission:
group.permissions = [permission_list]\ngroup.permissions.add(permission, permission, ...)\ngroup.permissions.remove(permission, permission, ...)\ngroup.permissions.clear()\nThe auth framework uses the following signals that\ncan be used for notification when a user logs in or out.
\nSent when a user logs in successfully.
\nArgumen dikirim dengan dinyal ini:
\nsenderKelas pengguna yang baru masuk.
\nrequestThe current HttpRequest instance.
userThe user instance that just logged in.
\nSent when the logout method is called.
\nsenderAs above: the class of the user that just logged out or None\nif the user was not authenticated.
requestThe current HttpRequest instance.
userThe user instance that just logged out or None if the\nuser was not authenticated.
Terkirim ketika pengguna gagal berhasil masuk
\nsenderNama modul digunakan untuk pengecekan keaslian.
\ncredentialsA dictionary of keyword arguments containing the user credentials that were\npassed to authenticate() or your own custom\nauthentication backend. Credentials matching a set of 'sensitive' patterns,\n(including password) will not be sent in the clear as part of the signal.
This section details the authentication backends that come with Django. For\ninformation on how to use them and how to write your own authentication\nbackends, see the Other authentication sources section of the User authentication guide.
\nThe following backends are available in django.contrib.auth.backends:
This is the default authentication backend used by Django. It\nauthenticates using credentials consisting of a user identifier and\npassword. For Django's default user model, the user identifier is the\nusername, for custom user models it is the field specified by\nUSERNAME_FIELD (see Customizing Users and authentication).
\nIt also handles the default permissions model as defined for\nUser and\nPermissionsMixin.
has_perm(), get_all_permissions(), get_user_permissions(),\nand get_group_permissions() allow an object to be passed as a\nparameter for object-specific permissions, but this backend does not\nimplement them other than returning an empty set of permissions if\nobj is not None.
Tries to authenticate username with password by calling\nUser.check_password. If no username\nis provided, it tries to fetch a username from kwargs using the\nkey CustomUser.USERNAME_FIELD. Returns an\nauthenticated user or None.
Returns the set of permission strings the user_obj has from their\nown user permissions. Returns an empty set if\nis_anonymous() or\nis_active is False.
Returns the set of permission strings the user_obj has from the\npermissions of the groups they belong. Returns an empty set if\nis_anonymous() or\nis_active is False.
Returns the set of permission strings the user_obj has, including both\nuser permissions and group permissions. Returns an empty set if\nis_anonymous() or\nis_active is False.
Uses get_all_permissions() to check if user_obj has the\npermission string perm. Returns False if the user is not\nis_active.
Returns whether the user_obj has any permissions on the app\napp_label.
Use this backend to take advantage of external-to-Django-handled\nauthentication. It authenticates using usernames passed in\nrequest.META['REMOTE_USER']. See\nthe Authenticating against REMOTE_USER\ndocumentation.
If you need more control, you can create your own authentication backend\nthat inherits from this class and override these attributes or methods:
\nTrue or False. Determines whether or not a\nUser object is created if not already\nin the database. Defaults to True.
The username passed as remote_user is considered trusted. This method\nsimply returns the User object with the given username, creating a new\nUser object if create_unknown_user is\nTrue.
Mengembalikan None jika create_unknown_user adalah False dan obyek User dengan nama pengguna yang diberikan tidak ditemukan dalam basisdata.
Performs any cleaning on the username (e.g. stripping LDAP DN\ninformation) prior to using it to get or create a\nUser object. Returns the cleaned\nusername.
Configures a newly created user. This method is called immediately after a\nnew user is created, and can be used to perform custom setup actions, such\nas setting the user's groups based on attributes in an LDAP directory.\nReturns the user object.
\n