OwlCyberSecurity - MANAGER
Edit File: middleware.cpython-39.pyc
a iH�f7 � @ s� d dl mZ d dlmZ d dlmZ d dlmZ d dlm Z d dl m Z dd� Z G d d � d e �Z G d d � d e �ZG d d� de�ZdS )� )�auth)� load_backend)�RemoteUserBackend)�ImproperlyConfigured)�MiddlewareMixin)�SimpleLazyObjectc C s t | d�st�| �| _| jS )N� _cached_user)�hasattrr �get_userr ��request� r �`/home/gouroczh/virtualenv/test/3.9/lib/python3.9/site-packages/django/contrib/auth/middleware.pyr s r c @ s e Zd Zdd� ZdS )�AuthenticationMiddlewarec s( t � d�std��t� fdd��� _d S )N�sessionz�The Django authentication middleware requires session middleware to be installed. Edit your MIDDLEWARE setting to insert 'django.contrib.sessions.middleware.SessionMiddleware' before 'django.contrib.auth.middleware.AuthenticationMiddleware'.c s t � �S )N)r r r r r �<lambda> � z:AuthenticationMiddleware.process_request.<locals>.<lambda>)r r r �user)�selfr r r r �process_request s �z(AuthenticationMiddleware.process_requestN)�__name__� __module__� __qualname__r r r r r r s r c @ s0 e Zd ZdZdZdZdd� Zdd� Zdd � Zd S ) �RemoteUserMiddlewarea� Middleware for utilizing web-server-provided authentication. If request.user is not authenticated, then this middleware attempts to authenticate the username passed in the ``REMOTE_USER`` request header. If authentication is successful, the user is automatically logged in to persist the user in the session. The header used is configurable and defaults to ``REMOTE_USER``. Subclass this class and change the ``header`` attribute if you need to use a different header. Z REMOTE_USERTc C s� t |d�std��z|j| j }W n, tyN | jrH|jjrH| �|� Y d S 0 |jjr||j� � | � ||�krrd S | �|� t j ||d�}|r�||_t � ||� d S )Nr z�The Django remote user auth middleware requires the authentication middleware to be installed. Edit your MIDDLEWARE setting to insert 'django.contrib.auth.middleware.AuthenticationMiddleware' before the RemoteUserMiddleware class.)Z remote_user)r r ZMETA�header�KeyError�force_logout_if_no_headerr �is_authenticated�_remove_invalid_userZ get_username�clean_usernamer Z authenticate�login)r r �usernamer r r r r 0 s$ � z$RemoteUserMiddleware.process_requestc C s< |j tj }t�|�}z|�|�}W n ty6 Y n0 |S )zr Allow the backend to clean the username, if the backend defines a clean_username method. )r r �BACKEND_SESSION_KEYr r �AttributeError)r r! r Z backend_str�backendr r r r W s z#RemoteUserMiddleware.clean_usernamec C sN zt |j�tjd��}W n ty4 t�|� Y n0 t|t�rJt�|� dS )z� Remove the current authenticated user in the request which is invalid but only if the user is authenticated via the RemoteUserBackend. � N) r r �getr r" � ImportErrorZlogout� isinstancer )r r Zstored_backendr r r r d s � z)RemoteUserMiddleware._remove_invalid_userN) r r r �__doc__r r r r r r r r r r s ' r c @ s e Zd ZdZdZdS )� PersistentRemoteUserMiddlewarea� Middleware for web-server provided authentication on logon pages. Like RemoteUserMiddleware but keeps the user authenticated even if the header (``REMOTE_USER``) is not found in the request. Useful for setups when the external authentication via ``REMOTE_USER`` is only expected to happen on some "logon" URL and the rest of the application wants to use Django's authentication mechanism. FN)r r r r) r r r r r r* u s r* N)Zdjango.contribr Zdjango.contrib.authr Z django.contrib.auth.backendsr Zdjango.core.exceptionsr Zdjango.utils.deprecationr Zdjango.utils.functionalr r r r r* r r r r �<module> s Y