AnonSec Shell
Server IP : 209.38.156.173  /  Your IP : 216.73.216.122   [ Reverse IP ]
Web Server : Apache/2.4.52 (Ubuntu)
System : Linux lakekumayuhotel 5.15.0-136-generic #147-Ubuntu SMP Sat Mar 15 15:53:30 UTC 2025 x86_64
User : root ( 0)
PHP Version : 8.1.2-1ubuntu2.22
Disable Function : NONE
Domains : 2 Domains
MySQL : OFF  |  cURL : ON  |  WGET : ON  |  Perl : ON  |  Python : OFF  |  Sudo : ON  |  Pkexec : ON
Directory :  /lib/python3/dist-packages/oauthlib/oauth2/rfc6749/endpoints/__pycache__/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Command :

[ HOME ]     [ BACKUP SHELL ]     [ JUMPING ]     [ MASS DEFACE ]     [ SCAN ROOT ]     [ SYMLINK ]     

Current File : /lib/python3/dist-packages/oauthlib/oauth2/rfc6749/endpoints/__pycache__/revocation.cpython-310.pyc
o

���a\�@sRdZddlZddlmZddlmZddlmZmZe�	e
�ZGdd	�d	e�ZdS)
z�
oauthlib.oauth2.rfc6749.endpoint.revocation
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

An implementation of the OAuth 2 `Token Revocation`_ spec (draft 11).

.. _`Token Revocation`: https://tools.ietf.org/html/draft-ietf-oauth-revocation-11
�N)�Request�)�OAuth2Error�)�BaseEndpoint�catch_errors_and_unavailabilityc@s@eZdZdZdZdZ		d
dd�Ze		dd	d
��Zdd�Z	dS)�RevocationEndpointz�Token revocation endpoint.

    Endpoint used by authenticated clients to revoke access and refresh tokens.
    Commonly this will be part of the Authorization Endpoint.
    )�access_token�
refresh_token)�POSTNFcCs&t�|�||_|p|j|_||_dS)N)r�__init__�request_validator�valid_token_types�supported_token_types�enable_jsonp)�selfr
rr�r�N/usr/lib/python3/dist-packages/oauthlib/oauth2/rfc6749/endpoints/revocation.pyrs

�
zRevocationEndpoint.__init__rc	
Cs�dddd�}t||||d�}z
|�|�t�d|�Wn5tyP}z)t�d||�|j}|jr:|jr:d�|j|�}|�	|j
�|||jfWYd	}~Sd	}~ww|j�
|j|j|�d
}|jrh|jrh|jd}i|dfS)
a�Revoke supplied access or refresh token.


        The authorization server responds with HTTP status code 200 if the
        token has been revoked sucessfully or if the client submitted an
        invalid token.

        Note: invalid tokens do not cause an error response since the client
        cannot handle such an error in a reasonable way.  Moreover, the purpose
        of the revocation request, invalidating the particular token, is
        already achieved.

        The content of the response body is ignored by the client as all
        necessary information is conveyed in the response code.

        An invalid token type hint value is ignored by the authorization server
        and does not influence the revocation response.
        zapplication/jsonzno-storezno-cache)zContent-Typez
Cache-Control�Pragma)�http_method�body�headerszToken revocation valid for %r.z)Client error during validation of %r. %r.z{}({});N�z();��)r�validate_revocation_request�log�debugr�jsonr�callback�format�updater�status_coder
�revoke_token�token�token_type_hint)	r�urirrr�resp_headers�request�e�
response_bodyrrr�create_revocation_response&s4��
��
�

z-RevocationEndpoint.create_revocation_responsecCs6|�|�|�|�|�|�|�|�|�|�dS)aEnsure the request is valid.

        The client constructs the request by including the following parameters
        using the "application/x-www-form-urlencoded" format in the HTTP
        request entity-body:

        token (REQUIRED).  The token that the client wants to get revoked.

        token_type_hint (OPTIONAL).  A hint about the type of the token
        submitted for revocation.  Clients MAY pass this parameter in order to
        help the authorization server to optimize the token lookup.  If the
        server is unable to locate the token using the given hint, it MUST
        extend its search accross all of its supported token types.  An
        authorization server MAY ignore this parameter, particularly if it is
        able to detect the token type automatically.  This specification
        defines two such values:

                *  access_token: An Access Token as defined in [RFC6749],
                    `section 1.4`_

                *  refresh_token: A Refresh Token as defined in [RFC6749],
                    `section 1.5`_

                Specific implementations, profiles, and extensions of this
                specification MAY define other values for this parameter using
                the registry defined in `Section 4.1.2`_.

        The client also includes its authentication credentials as described in
        `Section 2.3`_. of [`RFC6749`_].

        .. _`section 1.4`: https://tools.ietf.org/html/rfc6749#section-1.4
        .. _`section 1.5`: https://tools.ietf.org/html/rfc6749#section-1.5
        .. _`section 2.3`: https://tools.ietf.org/html/rfc6749#section-2.3
        .. _`Section 4.1.2`: https://tools.ietf.org/html/draft-ietf-oauth-revocation-11#section-4.1.2
        .. _`RFC6749`: https://tools.ietf.org/html/rfc6749
        N)�_raise_on_bad_method�_raise_on_bad_post_request�_raise_on_missing_token�_raise_on_invalid_client�_raise_on_unsupported_token)rr'rrrrUs

%


z.RevocationEndpoint.validate_revocation_request)NF)rNN)
�__name__�
__module__�__qualname__�__doc__r�valid_request_methodsrrr*rrrrrrs
��.r)
r3�logging�oauthlib.commonr�errorsr�baserr�	getLoggerr0rrrrrr�<module>s


Anon7 - 2022
AnonSec Team