REMOTE_USERLink to this heading#This document describes how to make use of external authentication sources in\nyour Django applications. This type of authentication solution is typically\nseen on intranet sites, with single sign-on solutions such as IIS and\nIntegrated Windows Authentication or Apache and mod_authnz_ldap, CAS,\nWebAuth, mod_auth_sspi, etc.
\nWhen the web server takes care of authentication it typically provides the\nauthenticated user as REMOTE_USER. In Django, this value is made available\nin request.META (as REMOTE_USER when\nsupplied as an environment variable, as in WSGI, or HTTP_REMOTE_USER when\nsupplied via an HTTP header, as in ASGI). Django can be configured to make use\nof the REMOTE_USER value using the RemoteUserMiddleware or\nPersistentRemoteUserMiddleware, and\nRemoteUserBackend classes found in\ndjango.contrib.auth.
Ar dtús, ní mór duit an:class: django.contrib.auth.middleware.remoteUserMiddleware a chur leis an socrú:setting: MIDDLEWARE **tar éis ** an:class: django.contrib.auth.middleware.AuthenticationMiddleware:
\nMIDDLEWARE = [\n "...",\n "django.contrib.auth.middleware.AuthenticationMiddleware",\n "django.contrib.auth.middleware.RemoteUserMiddleware",\n "...",\n]\nAnsin, ní mór duit:class: ~django.contrib.auth.backends.modelBackend a chur in ionad la:class: ~django.contrib.auth.backends.remoteUserBackend sa socrú: AUTHENTICATION_BACKENDS:
\nAUTHENTICATION_BACKENDS = [\n "django.contrib.auth.backends.RemoteUserBackend",\n]\nWith this setup, RemoteUserMiddleware will detect the username in\nrequest.META['REMOTE_USER'] (or request.META['HTTP_REMOTE_USER'] under\nASGI) and will authenticate and auto-login that user\nusing the RemoteUserBackend.
Bí ar an eolas go ndíchumasaíonn an socrú áirithe seo fíordheimhniú leis an réamhshocraithe ModelBackend. Ciallaíonn sé seo mura socraítear an luach REMOTE_USER` ansin níl an t-úsáideoir in ann logáil isteach, fiú ag baint úsáide as comhéadan riaracháin Django. Ag cur `Django.contrib.auth.backends.ModelBackend' leis an liosta AUTHENTICATION_BACKENDS, úsáidfear ModelBackend mar fhillback má tá REMOTE_USER as láthair, rud a réiteoidh na saincheisteanna seo.
Ní chomhtháthaíonn bainistíocht úsáideora Django, mar shampla na tuairimí i contrib.admin ``agus an t-ordú bainistíochta: djadmin: `createsuperuser, le húsáideoirí iargúlta. Oibríonn na comhéadain seo le húsáideoirí atá stóráilte sa bhunachar sonraí beag beann ar ``AUTHENTICATION_BACKENDS`.
\n\nIf your authentication mechanism uses a custom HTTP header and not\nREMOTE_USER, you can subclass RemoteUserMiddleware and set the\nheader attribute to the desired request.META key. For example:
mysite/middleware.py from django.contrib.auth.middleware import RemoteUserMiddleware\n\n\n class CustomHeaderRemoteUserMiddleware(RemoteUserMiddleware):\n header = "HTTP_AUTHUSER"\nThis custom middleware is then used in the MIDDLEWARE setting\ninstead of django.contrib.auth.middleware.RemoteUserMiddleware:
MIDDLEWARE = [\n "...",\n "django.contrib.auth.middleware.AuthenticationMiddleware",\n "mysite.middleware.CustomHeaderRemoteUserMiddleware",\n "...",\n]\nMá theastaíonn níos mó smachta uait, is féidir leat do chúltaca fíordheimhnithe féin a chruthú a fhaigheann oidhreacht ó:class: ~django.contrib.auth.backends.remoteUserBackend agus ceann amháin nó níos mó dá thréithe agus modhanna a shárú.
\nREMOTE_USER ar leathanaigh logála isteach amháinLink to this heading#Glacann an middleware fíordheimhnithe RemoteUserMiddleware go bhfuil an ceannteideal iarratais HTTP REMOTE_USER i láthair le gach iarratas fíordheimhnithe. D'fhéadfaí súil leis sin agus praiticiúil nuair a úsáidtear Basic HTTP Auth le htpasswd nó meicníochtaí den chineál céanna, ach le Negoate (GSSAPI/KerberOS) nó modhanna fíordheimhnithe dian-acmhainní eile, de ghnáth ní bhunaítear an fíordheimhniú sa bhfreastalaí HTTP tosaigh ach le haghaidh URL amháin nó cúpla URL, agus tar éis fíordheimhniú rathúil, ceaptar an feidhmchlár an seisiún fíordheimhnithe féin a choinneáil.
PersistentRemoteUserMiddleware\nprovides support for this use case. It will maintain the authenticated session\nuntil explicit logout by the user. The class can be used as a drop-in\nreplacement of RemoteUserMiddleware\nin the documentation above.