| Server IP : 138.197.107.151 / Your IP : 216.73.217.120 Web Server : Apache/2.4.58 (Ubuntu) System : Linux BloxBy-Builder 6.8.0-71-generic #71-Ubuntu SMP PREEMPT_DYNAMIC Tue Jul 22 16:52:38 UTC 2025 x86_64 User : wpbetasites_mrakzqskir ( 1022) PHP Version : 8.3.6 Disable Function : NONE MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : ON | Pkexec : OFF Directory : /lib/python3/dist-packages/oauthlib/oauth2/rfc6749/endpoints/__pycache__/ |
Upload File : |
�
�c\ � �r � d Z ddlZddlmZ ddlmZ ddlmZmZ ej e
� Z G d� d e� Z y)
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 �@ � e Zd ZdZdZdZ dd�Ze d d�� Zd� Z y)
�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)�POSTNc �t � t j | � || _ |xs | j | _ || _ y )N)r �__init__�request_validator�valid_token_types�supported_token_types� enable_jsonp)�selfr r r s �N/usr/lib/python3/dist-packages/oauthlib/oauth2/rfc6749/endpoints/revocation.pyr zRevocationEndpoint.__init__ s6 � �� � �d�#�!2�� � !� ;�T�%;�%;�
�"� (��� c �h � dddd�}t ||||�� } | j |� t j d|� | j j |j |j |� d
}| j r|j r|j d z }i |d fS # t $ r�}t j d||� |j
}| j r(|j r dj |j |� }|j |j � |||j fcY d }~S d }~ww xY w)
a� Revoke supplied access or refresh token.
The authorization server responds with HTTP status code 200 if the
token has been revoked successfully 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�headersz Token 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 �urir r r � resp_headers�request�e�
response_bodys r �create_revocation_responsez-RevocationEndpoint.create_revocation_response& s! � �, /� '� �
� �
� �[�t�W�F�� >� � ,� ,�W� 5� �I�I�6�� @�
� � �+�+�G�M�M�,3�,C�,C�W� N� �
� � � ��!1�!1� #� ,� ,�u� 4�M��=�#�%�%�� � >� �I�I�A�7�A� N� �F�F�M�� � �W�%5�%5� )� 0� 0��1A�1A�=� Q�
� � � �� � � *� � ��
�
�=� =��
>�s �'B � D1�&B D,�&D1�,D1c � � | j |� | j |� | j |� | j |� | j |� y)a Ensure 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 across 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)r r+ s r r z.RevocationEndpoint.validate_revocation_requestU sK � �J
�!�!�'�*� �'�'��0� �$�$�W�-� �%�%�g�.� �(�(��1r )NF)r
NN)
�__name__�
__module__� __qualname__�__doc__r �valid_request_methodsr r r. r � r r r
r
s@ � �� :�� %��@D� �)� %�GK�+/�,&� %�,&�\)2r r
)
r8 �logging�oauthlib.commonr �errorsr �baser r � getLoggerr5 r r
r: r r �<module>r@ s8 ��� � #� � ?��g����!��k2� � k2r