qh.BSSKJr SSKrSSKJr SSKJr SSKJrJ r J r SSK r SSK J r \R"\5rSr"S S \5r"S S \5r"S S\5r"SS\ R*5rg))urlparseN)add_params_to_uri) urldecode)SIGNATURE_HMAC SIGNATURE_RSASIGNATURE_TYPE_AUTH_HEADER)OAuth1cd[U5$![a SSKnURU5s$f=f)z(Parse query or json to python dictionaryrN) _urldecode Exceptionjsonloads)bodyrs R/var/www/html/env/lib/python3.13/site-packages/requests_oauthlib/oauth1_session.pyrrs3 $  zz$ s //c8^\rSrSrU4Sjr\S5rSrU=r$)TokenRequestDeniedc8>[[U] U5 X lgN)superr__init__responseselfmessager __class__s rrTokenRequestDenied.__init__s  $09 c.URR$)z$For backwards-compatibility purposes)r status_coders rr!TokenRequestDenied.status_codes}}(((rr) __name__ __module__ __qualname____firstlineno__rpropertyr!__static_attributes__ __classcell__rs@rrrs!))rrc(^\rSrSrU4SjrSrU=r$) TokenMissing%c8>[[U] U5 X lgr)rr.rrrs rrTokenMissing.__init__&s lD*73 rr$)r%r&r'r(rr*r+r,s@rr.r.%s !!rr.c\rSrSrSrg)VerifierMissing+N)r%r&r'r(r*r5rrr3r3+srr3c ^\rSrSrSrSSSS\\SSSS4 U4Sjjr\S5r \ RS5r \S5r SS jr SS jr SS jrS rS rSrSrSrU=r$) OAuth1Session/aRequest signing and convenience methods for the oauth dance. What is the difference between OAuth1Session and OAuth1? OAuth1Session actually uses OAuth1 internally and its purpose is to assist in the OAuth workflow through convenience methods to prepare authorization URLs and parse the various token and redirection responses. It also provide rudimentary validation of responses. An example of the OAuth workflow using a basic CLI app and Twitter. >>> # Credentials obtained during the registration. >>> client_key = 'client key' >>> client_secret = 'secret' >>> callback_uri = 'https://127.0.0.1/callback' >>> >>> # Endpoints found in the OAuth provider API documentation >>> request_token_url = 'https://api.twitter.com/oauth/request_token' >>> authorization_url = 'https://api.twitter.com/oauth/authorize' >>> access_token_url = 'https://api.twitter.com/oauth/access_token' >>> >>> oauth_session = OAuth1Session(client_key,client_secret=client_secret, callback_uri=callback_uri) >>> >>> # First step, fetch the request token. >>> oauth_session.fetch_request_token(request_token_url) { 'oauth_token': 'kjerht2309u', 'oauth_token_secret': 'lsdajfh923874', } >>> >>> # Second step. Follow this link and authorize >>> oauth_session.authorization_url(authorization_url) 'https://api.twitter.com/oauth/authorize?oauth_token=sdf0o9823sjdfsdf&oauth_callback=https%3A%2F%2F127.0.0.1%2Fcallback' >>> >>> # Third step. Fetch the access token >>> redirect_response = input('Paste the full redirect URL here.') >>> oauth_session.parse_authorization_response(redirect_response) { 'oauth_token: 'kjerht2309u', 'oauth_token_secret: 'lsdajfh923874', 'oauth_verifier: 'w34o8967345', } >>> oauth_session.fetch_access_token(access_token_url) { 'oauth_token': 'sdf0o9823sjdfsdf', 'oauth_token_secret': '2kjshdfp92i34asdasd', } >>> # Done. You can now make OAuth requests. >>> status_url = 'http://api.twitter.com/1/statuses/update.json' >>> new_status = {'status': 'hello world!'} >>> oauth_session.post(status_url, data=new_status) NFc  >[[U] 5 [U4UUUUUUUU U U S. U D6UlURUlg)aConstruct the OAuth 1 session. :param client_key: A client specific identifier. :param client_secret: A client specific secret used to create HMAC and plaintext signatures. :param resource_owner_key: A resource owner key, also referred to as request token or access token depending on when in the workflow it is used. :param resource_owner_secret: A resource owner secret obtained with either a request or access token. Often referred to as token secret. :param callback_uri: The URL the user is redirect back to after authorization. :param signature_method: Signature methods determine how the OAuth signature is created. The three options are oauthlib.oauth1.SIGNATURE_HMAC (default), oauthlib.oauth1.SIGNATURE_RSA and oauthlib.oauth1.SIGNATURE_PLAIN. :param signature_type: Signature type decides where the OAuth parameters are added. Either in the Authorization header (default) or to the URL query parameters or the request body. Defined as oauthlib.oauth1.SIGNATURE_TYPE_AUTH_HEADER, oauthlib.oauth1.SIGNATURE_TYPE_QUERY and oauthlib.oauth1.SIGNATURE_TYPE_BODY respectively. :param rsa_key: The private RSA key as a string. Can only be used with signature_method=oauthlib.oauth1.SIGNATURE_RSA. :param verifier: A verifier string to prove authorization was granted. :param client_class: A subclass of `oauthlib.oauth1.Client` to use with `requests_oauthlib.OAuth1` instead of the default :param force_include_body: Always include the request body in the signature creation. :param **kwargs: Additional keyword arguments passed to `OAuth1` ) client_secretresource_owner_keyresource_owner_secret callback_urisignature_methodsignature_typersa_keyverifier client_classforce_include_bodyN)rr7rr _clientauth)r client_keyr:r;r<r=r>r?r@rArBrCkwargsrs rrOAuth1Session.__init__fs\d mT+-   '1"7%-)%1     LL rc URRRnURRRnURRRn0nU(aXS'U(aX$S'U(aX4S'U$)N oauth_tokenoauth_token_secretoauth_verifier)rDclientr;r<rA)rrJrKrL token_dicts rtokenOAuth1Session.tokenspll))<< !\\00FF,,55 (3} % /A+ , +9' (rc&URU5 gr)_populate_attributes)rvalues rrOrPs !!%(rcURRR[:Xa)[ URRR 5$[ URRR 5=(aY [ URRR 5=(a) [ URRR5$)aPBoolean that indicates whether this session has an OAuth token or not. If `self.authorized` is True, you can reasonably expect OAuth-protected requests to the resource to succeed. If `self.authorized` is False, you need the user to go through the OAuth authentication dance before OAuth-protected requests to the resource will succeed. )rDrMr>rboolr;r:r<r"s r authorizedOAuth1Session.authorizeds <<   / /= @ ++>>? ?T\\((667D,,??@D,,BBC rc U=(d URRRUS'[R SX15 [ XR 55$)acCreate an authorization URL by appending request_token and optional kwargs to url. This is the second step in the OAuth 1 workflow. The user should be redirected to this authorization URL, grant access to you, and then be redirected back to you. The redirection back can either be specified during client registration or by supplying a callback URI per request. :param url: The authorization endpoint URL. :param request_token: The previously obtained request token. :param kwargs: Optional parameters to append to the URL. :returns: The authorization URL with new parameters embedded. An example using a registered default callback URI. >>> request_token_url = 'https://api.twitter.com/oauth/request_token' >>> authorization_url = 'https://api.twitter.com/oauth/authorize' >>> oauth_session = OAuth1Session('client-key', client_secret='secret') >>> oauth_session.fetch_request_token(request_token_url) { 'oauth_token': 'sdf0o9823sjdfsdf', 'oauth_token_secret': '2kjshdfp92i34asdasd', } >>> oauth_session.authorization_url(authorization_url) 'https://api.twitter.com/oauth/authorize?oauth_token=sdf0o9823sjdfsdf' >>> oauth_session.authorization_url(authorization_url, foo='bar') 'https://api.twitter.com/oauth/authorize?oauth_token=sdf0o9823sjdfsdf&foo=bar' An example using an explicit callback URI. >>> request_token_url = 'https://api.twitter.com/oauth/request_token' >>> authorization_url = 'https://api.twitter.com/oauth/authorize' >>> oauth_session = OAuth1Session('client-key', client_secret='secret', callback_uri='https://127.0.0.1/callback') >>> oauth_session.fetch_request_token(request_token_url) { 'oauth_token': 'sdf0o9823sjdfsdf', 'oauth_token_secret': '2kjshdfp92i34asdasd', } >>> oauth_session.authorization_url(authorization_url) 'https://api.twitter.com/oauth/authorize?oauth_token=sdf0o9823sjdfsdf&oauth_callback=https%3A%2F%2F127.0.0.1%2Fcallback' rJzAdding parameters %s to url %s)rDrMr;logdebugritems)rurl request_tokenrGs rauthorization_urlOAuth1Session.authorization_urlsDT!. W1D1D1W1W} 2F@ lln55rc (U(aSRU5OSURRlUR"U40UD6n[ R S5 SURRlSURRlU$)aFetch a request token. This is the first step in the OAuth 1 workflow. A request token is obtained by making a signed post request to url. The token is then parsed from the application/x-www-form-urlencoded response and ready to be used to construct an authorization url. :param url: The request token endpoint URL. :param realm: A list of realms to request access to. :param request_kwargs: Optional arguments passed to ''post'' function in ''requests.Session'' :returns: The response in dict format. Note that a previously set callback_uri will be reset for your convenience, or else signature creation will be incorrect on consecutive requests. >>> request_token_url = 'https://api.twitter.com/oauth/request_token' >>> oauth_session = OAuth1Session('client-key', client_secret='secret') >>> oauth_session.fetch_request_token(request_token_url) { 'oauth_token': 'sdf0o9823sjdfsdf', 'oauth_token_secret': '2kjshdfp92i34asdasd', }  Nz>> access_token_url = 'https://api.twitter.com/oauth/access_token' >>> redirect_response = 'https://127.0.0.1/callback?oauth_token=kjerht2309uf&oauth_token_secret=lsdajfh923874&oauth_verifier=w34o8967345' >>> oauth_session = OAuth1Session('client-key', client_secret='secret') >>> oauth_session.parse_authorization_response(redirect_response) { 'oauth_token: 'kjerht2309u', 'oauth_token_secret: 'lsdajfh923874', 'oauth_verifier: 'w34o8967345', } >>> oauth_session.fetch_access_token(access_token_url) { 'oauth_token': 'sdf0o9823sjdfsdf', 'oauth_token_secret': '2kjshdfp92i34asdasd', } rANz No client verifier has been set.z9Resetting verifier attribute, should not be used anymore.)rDrMrAgetattrr3rdrYrZ)rr\rArerOs rfetch_access_token OAuth1Session.fetch_access_token su4 +3LL   (t||**J==!"DE E!!#88 MN'+ $ rc[RSU5 [[[ U5R 55n[RS5 UR U5 X lU$)aExtract parameters from the post authorization redirect response URL. :param url: The full URL that resulted from the user being redirected back from the OAuth provider to you, the client. :returns: A dict of parameters extracted from the URL. >>> redirect_response = 'https://127.0.0.1/callback?oauth_token=kjerht2309uf&oauth_token_secret=lsdajfh923874&oauth_verifier=w34o8967345' >>> oauth_session = OAuth1Session('client-key', client_secret='secret') >>> oauth_session.parse_authorization_response(redirect_response) { 'oauth_token: 'kjerht2309u', 'oauth_token_secret: 'lsdajfh923874', 'oauth_verifier: 'w34o8967345', } z'Parsing token from query part of url %sz)Updating internal client token attribute.)rYrZdictrrqueryrRrO)rr\rOs rparse_authorization_response*OAuth1Session.parse_authorization_responseCsQ ;SAYx}2234 => !!%(  rcSU;aUSURRlO[SR US9U5eSU;aUSURRlSU;aUSURRlgg)NrJz)Response does not contain a token: {resp})resprKrL)rDrMr;r.formatr<rA)rrOs rrR"OAuth1Session._populate_attributesZs E !5:=5IDLL   2;BBBNPU  5 (8=>R8SDLL   5 u $+01A+BDLL   ( %rc N[RSXRR5 UR"U40UD6nUR S:a&Sn[ XCR UR4-U5e[RSUR5 [[URR555n[RSU5 [RS5 URU5 XPl U$![anSU-n[U5eSnAff=f)Nz&Fetching token from %s using client %siz5Token request failed with code %s, response was '%s'.z!Decoding token from response "%s"zUnable to decode token from token response. This is commonly caused by an unsuccessful request where a non urlencoded error message is returned. The decoding error was %szObtained token %sz4Updating internal client attributes from token data.)rYrZrDrMpostr!rtextrmrstrip ValueErrorrRrO)rr\rererrorrOes rrdOAuth1Session._fetch_tokenfs :CATATU IIc ,^ , ==C KE$UmmQVV-D%DaH H 5qvv> $166<<>23E %u- HI !!%(   $  U# # $s,D D$DD$cSUR;a7URRSS5 URUR5 g)zu When being redirected we should always strip Authorization header, since nonce may not be reused as per OAuth spec. AuthorizationTN)headerspop prepare_authrE)rprepared_requestrs r rebuild_authOAuth1Session.rebuild_auths@ .66 6  $ $ ( ($ ?  ) )$)) 4r)rDrErOr)r%r&r'r(__doc__rrrr)rOsetterrVr^rfrjrorRrdrr*r+r,s@rr7r7/s4r"'1 A!F   \\))&,6\B!F. C6  rr7) urllib.parserloggingoauthlib.commonrrr oauthlib.oauth1rrrrequestsr getLoggerr%rYryrr.r3Sessionr7r5rrrsl!-3UU! ))!:!  j \H$$\r