🔐 Sid Gifari File Manager Pro
v8.0.5 | 2026-08-07 12:23:53 | PHP 8.2.32
📂
/ (Root)
/
usr
/
lib
/
python3.6
/
site-packages
/
oauthlib
/
oauth2
/
rfc6749
/
endpoints
/
__pycache__
📍 /usr/lib/python3.6/site-packages/oauthlib/oauth2/rfc6749/endpoints/__pycache__
🔄 Refresh
✏️
Editing: resource.cpython-36.pyc
Read Only
3 ,�[� � @ sV d Z ddlmZmZ ddlZddlmZ ddlmZm Z ej e �Z G dd� de�Z dS ) z� oauthlib.oauth2.rfc6749 ~~~~~~~~~~~~~~~~~~~~~~~ This module is an implementation of various logic needed for consuming and providing OAuth 2.0 RFC6749. � )�absolute_import�unicode_literalsN)�Request� )� BaseEndpoint� catch_errors_and_unavailabilityc @ sR e Zd ZdZdd� Zedd� �Zedd� �Zedd � �Ze dd d ��Z dd� Z d S )�ResourceEndpointa� Authorizes access to protected resources. The client accesses protected resources by presenting the access token to the resource server. The resource server MUST validate the access token and ensure that it has not expired and that its scope covers the requested resource. The methods used by the resource server to validate the access token (as well as any error responses) are beyond the scope of this specification but generally involve an interaction or coordination between the resource server and the authorization server:: # For most cases, returning a 403 should suffice. The method in which the client utilizes the access token to authenticate with the resource server depends on the type of access token issued by the authorization server. Typically, it involves using the HTTP "Authorization" request header field [RFC2617] with an authentication scheme defined by the specification of the access token type used, such as [RFC6750]:: # Access tokens may also be provided in query and body https://example.com/protected?access_token=kjfch2345sdf # Query access_token=sdf23409df # Body c C s t j| � || _|| _d S )N)r �__init__�_tokens�_default_token)�self� default_tokenZ token_types� r � /usr/lib/python3.6/resource.pyr / s zResourceEndpoint.__init__c C s | j S )N)r )r r r r r 4 s z ResourceEndpoint.default_tokenc C s | j j| j�S )N)�tokens�getr )r r r r �default_token_type_handler8 s z+ResourceEndpoint.default_token_type_handlerc C s | j S )N)r )r r r r r < s zResourceEndpoint.tokens�GETNc C sP t ||||�}| j|�|_||_| jj|j| j�}tjd|j|� |j |�|fS )z0Validate client, code etc, return body + headersz(Dispatching token_type %s request to %r.) r �find_token_type� token_type�scopesr r r �log�debugZvalidate_request)r ZuriZ http_methodZbodyZheadersr �requestZtoken_type_handlerr r r �verify_request@ s z ResourceEndpoint.verify_requestc s4 t � fdd�| jj� D ��}t|�r0|d d S dS )a> Token type identification. RFC 6749 does not provide a method for easily differentiating between different token types during protected resource access. We estimate the most likely token type (if any) by asking each known token type to give an estimation based on the request. c 3 s | ]\}}|j � �|fV qd S )N)Z estimate_type)�.0�n�t)r r r � <genexpr>U s z3ResourceEndpoint.find_token_type.<locals>.<genexpr>r r N)�sortedr �items�len)r r Z estimatesr )r r r M s z ResourceEndpoint.find_token_type)r NNN) �__name__� __module__� __qualname__�__doc__r �propertyr r r r r r r r r r r s r )r% Z __future__r r ZloggingZoauthlib.commonr �baser r Z getLoggerr" r r r r r r �<module> s
💾 Save Changes
❌ Cancel