IiXSrSSKrSSKrSSKrSSKrSSKrSSKrSSKJr SSK J r J r JrJr SSKJr SSKJr SSKJrJrJr "SS \5r"S S \5r"S S \5rg!\ a SSK rNPf=f)zn Provides AWS4Auth class for handling Amazon Web Services version 4 authentication with the Requests module. N)urlparseparse_qsquoteunquote)AuthBase)AWS4SigningKey)DateMismatchErrorNoSecretKeyErrorDateFormatErrorc\rSrSrSr1SkrSrSSjrSrSr \ S 5r \ S 5r S r\ S 5rS r\ SSj5r\ S5rSr\ S5r\ S5rSrg)AWS4Autha Requests authentication class providing AWS version 4 authentication for HTTP requests. Implements header-based authentication only, GET URL parameter and POST parameter authentication are not supported. Provides authentication for regions and services listed at: http://docs.aws.amazon.com/general/latest/gr/rande.html The following services do not support AWS auth version 4 and are not usable with this package: * Simple Email Service (SES)' - AWS auth v3 only * Simple Workflow Service - AWS auth v3 only * Import/Export - AWS auth v2 only * SimpleDB - AWS auth V2 only * DevPay - AWS auth v1 only * Mechanical Turk - has own signing mechanism You can reuse AWS4Auth instances to sign as many requests as you need. Basic usage ----------- >>> import requests >>> from requests_aws4auth import AWS4Auth >>> auth = AWS4Auth('', '', 'eu-west-1', 's3') >>> endpoint = 'http://s3-eu-west-1.amazonaws.com' >>> response = requests.get(endpoint, auth=auth) >>> response.text bcaf1ffd86f461ca5fb16fd081034f webfile ... This example lists your buckets in the eu-west-1 region of the Amazon S3 service. STS Temporary Credentials ------------------------- >>> from requests_aws4auth import AWS4Auth >>> auth = AWS4Auth('', '', 'eu-west-1', 's3', session_token='') ... This example shows how to construct an AWS4Auth object for use with STS temporary credentials. The ``x-amz-security-token`` header is added with the session token. Temporary credential timeouts are not managed -- in case the temporary credentials expire, they need to be re-generated and the AWS4Auth object re-constructed with the new credentials. Dynamic STS Credentials using botocore RefreshableCredentials ------------------------------------------------------------- >>> from requests_aws4auth import AWS4Auth >>> from botocore.session import Session >>> credentials = Session().get_credentials() >>> auth = AWS4Auth(region='eu-west-1', service='es', refreshable_credentials=credentials) ... This example shows how to construct an AWS4Auth instance with automatically refreshing credentials, suitable for long-running applications using AWS IAM assume-role. The RefreshableCredentials instance is used to generate valid static credentials per-request, eliminating the need to recreate the AWS4Auth instance when temporary credentials expire. Date handling ------------- If an HTTP request to be authenticated contains a Date or X-Amz-Date header, AWS will only accept authorisation if the date in the header matches the scope date of the signing key (see http://docs.aws.amazon.com/general/latest/gr/sigv4-date-handling.html). From version 0.8 of requests-aws4auth, if the header date does not match the scope date, the AWS4Auth class will automatically regenerate its signing key, using the same scope parameters as the previous key except for the date, which will be changed to match the request date. (If a request does not include a date, the current date is added to the request in an X-Amz-Date header). The new behaviour from version 0.8 has implications for thread safety and secret key security, see the "Automatic key regeneration", "Secret key storage" and "Multithreading" sections below. This also means that AWS4Auth is now attempting to parse and extract dates from the values in X-Amz-Date and Date headers. Supported date formats are: * RFC 7231 (e.g. Mon, 09 Sep 2011 23:36:00 GMT) * RFC 850 (e.g. Sunday, 06-Nov-94 08:49:37 GMT) * C time (e.g. Wed Dec 4 00:00:00 2002) * Amz-Date format (e.g. 20090325T010101Z) * ISO 8601 / RFC 3339 (e.g. 2009-03-25T10:11:12.13-01:00) If either header is present but AWS4Auth cannot extract a date because all present date headers are in an unrecognisable format, AWS4Auth will delete any X-Amz-Date and Date headers present and replace with a single X-Amz-Date header containing the current date. This behaviour can be modified using the 'raise_invalid_date' keyword argument of the AWS4Auth constructor. Automatic key regeneration -------------------------- If you do not want the signing key to be automatically regenerated when a mismatch between the request date and the scope date is encountered, use the alternative StrictAWS4Auth class, which is identical to AWS4Auth except that upon encountering a date mismatch it just raises a DateMismatchError. You can also use the PassiveAWS4Auth class, which mimics the AWS4Auth behaviour prior to version 0.8 and just signs and sends the request, whether the date matches or not. In this case it is up to the calling code to handle an authentication failure response from AWS caused by a date mismatch. Secret key storage ------------------ To allow automatic key regeneration, the secret key is stored in the AWS4Auth instance, in the signing key object. If you do not want this to occur, instantiate the instance using an AWS4Signing key which was created with the store_secret_key parameter set to False: >>> sig_key = AWS4SigningKey(secret_key, region, service, date, False) >>> auth = StrictAWS4Auth(access_id, sig_key) The AWS4Auth class will then raise a NoSecretKeyError when it attempts to regenerate its key. A slightly more conceptually elegant way to handle this is to use the alternative StrictAWS4Auth class, again instantiating it with an AWS4SigningKey instance created with store_secret_key = False. Multithreading -------------- If you share AWS4Auth (or even StrictAWS4Auth) instances between threads you are likely to encounter problems. Because AWS4Auth instances may unpredictably regenerate their signing key as part of signing a request, threads using the same instance may find the key changed by another thread halfway through the signing process, which may result in undefined behaviour. It may be possible to rig up a workable instance sharing mechanism using locking primitives and the StrictAWS4Auth class, however this poor author can't think of a scenario which works safely yet doesn't suffer from at some point blocking all threads for at least the duration of an HTTP request, which could be several seconds. If several requests come in in close succession which all require key regenerations then the system could be forced into serial operation for quite a length of time. In short, it's best to create a thread-local instance of AWS4Auth for each thread that needs to do authentication. Class attributes ---------------- AWS4Auth.access_id -- the access ID supplied to the instance AWS4Auth.region -- the AWS region for the instance AWS4Auth.service -- the endpoint code for the service for this instance AWS4Auth.date -- the date the instance is valid for AWS4Auth.signing_key -- instance of AWS4SigningKey used for this instance, either generated from the supplied parameters or supplied directly on the command line >datehostx-amz-* content-typec<SUlURSS5UlUR(aURSS5UlUR(d [ S5eURSS5UlUR (d [ S5eURSS5UlURRS5 GO>[U5nUS ;aS RU5n[ U5eUS Ul [US [5(abUS :Xa\US UlURR UlURRUlURR UlOKUS;a;US nUS UlUSUlUS:XaUSOSUlURUS9 O [ 5eURS5UlUR(aURRS5 URSS5nUS;aX`lO [#S5e[%UR5UlSU;a5[US[(R*5(a[%US5Ul[,R."U5 g)a[ AWS4Auth instances can be created by supplying key scope parameters directly or by using an AWS4SigningKey instance: >>> auth = AWS4Auth(access_id, secret_key, region, service ... [, date][, raise_invalid_date=False][, session_token=None]) or >>> auth = AWS4Auth(access_id, signing_key[, raise_invalid_date=False]) or using auto-refreshed STS temporary creds via botocore RefreshableCredentials (useful for long-running processes): >>> auth = AWS4Auth(refreshable_credentials=botocore.session.Session().get_credentials(), ... region='eu-west-1', service='es') access_id -- This is your AWS access ID secret_key -- This is your AWS secret access key region -- The region you're connecting to, as per the list at http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region e.g. us-east-1. For services which don't require a region (e.g. IAM), use us-east-1. Must be supplied as a keyword argument iff refreshable_credentials is set. service -- The name of the service you're connecting to, as per endpoints at: http://docs.aws.amazon.com/general/latest/gr/rande.html e.g. elasticbeanstalk. Must be supplied as a keyword argument iff refreshable_credentials is set. date -- Date this instance is valid for. 8-digit date as str of the form YYYYMMDD. Key is only valid for requests with a Date or X-Amz-Date header matching this date. If date is not supplied the current date is used. signing_key -- An AWS4SigningKey instance. raise_invalid_date -- Must be supplied as keyword argument. AWS4Auth tries to parse a date from the X-Amz-Date and Date headers of the request, first trying X-Amz-Date, and then Date if X-Amz-Date is not present or is in an unrecognised format. If one or both of the two headers are present yet neither are in a format which AWS4Auth recognises then it will remove both headers and replace with a new X-Amz-Date header using the current date. If this behaviour is not wanted, set the raise_invalid_date keyword argument to True, and instead an InvalidDateError will be raised when neither date is recognised. If neither header is present at all then an X-Amz-Date header will still be added containing the current date. See the AWS4Auth class docstring for supported date formats. session_token -- Must be supplied as keyword argument. If session_token is set, then it is used for the x-amz-security-token header, for use with STS temporary credentials. refreshable_credentials -- A botocore.credentials.RefreshableCredentials instance. Must be supplied as keyword argument. This instance is used to generate valid per-request static credentials, without needing to re-generate the AWS4Auth instance. If refreshable_credentials is set, the following arguments are ignored: access_id, secret_key, signing_key, session_token. Nrefreshable_credentialsservicezOservice must be provided as keyword argument when using refreshable_credentialsregionzNregion must be provided as keyword argument when using refreshable_credentialsrx-amz-security-token)z.AWS4Auth() takes 2, 4 or 5 arguments, {} givenrrr)rrrr secret_key session_tokenraise_invalid_dateF)TFz?raise_invalid_date must be True or False in AWS4Auth.__init__() include_hdrs) signing_keygetrr TypeErrorrrdefault_include_headersaddlenformat access_id isinstancer regenerate_signing_keyrr ValueErrorsetr!abcIterabler__init__)selfargskwargslmsgrr s @/venv/lib/python3.13/site-packages/requests_aws4auth/aws4auth.pyr0AWS4Auth.__init__s,L '-zz2KT'R$  ' '!::i6DL<< qrr **Xt4DK;; pqq 640DI  ( ( , ,-C DD A !FMMaPn$!!WDN$q'>22qAv#'7 "..55 #//77  ,,11 f!!W "1g #Aw '(AvDG4 ++z+Bk!!'O!$: ;D $NcUc*URbURRc[eU=(d URRnU=(d URnU=(d URnU=(d UR nURcSnOURR n[XX4U5UlX lX0lURR Ulg)a Regenerate the signing key for this instance. Store the new key in signing_key property. Take scope elements of the new key from the equivalent properties (region, service, date) of the current AWS4Auth instance. Scope elements can be overridden for the new key by supplying arguments to this function. If overrides are supplied update the current AWS4Auth instance's equivalent properties to match the new values. If secret_key is not specified use the value of the secret_key property of the current AWS4Auth instance's signing key. If the existing signing key is not storing its secret key (i.e. store_secret_key was set to False at instantiation) then raise a NoSecretKeyError and do not regenerate the key. In order to regenerate a key which is not storing its secret key, secret_key must be supplied to this function. Use the value of the existing key's store_secret_key property when generating the new key. If there is no existing key, then default to setting store_secret_key to True for new key. NT)r"rr rrrstore_secret_keyr )r1rrrrr:s r6r+AWS4Auth.regenerate_signing_key8s0  4#3#3#;t?O?O?Z?Z?b" ">4#3#3#>#> &4;;)T\\ tyy    ## #//@@ )*g*:<  $$)) r8cdUR(aUR5 URU5nUcSUR;a URS SUR;a URS [RR 5nUR 5nURS5URS'URS5nX@R :waURU5 [US5(ayURbl[URS5(aURR5Ul URU5 [R"UR5nOU[US5(a.URb![R"UR5nO[R"S5nUR!5URS 'UR"(aUR"URS 'UR%XR&5nUupxUR)XU5n UR+XUR,R.5n U R1S 5n [2R4"UR,R6U [R5n U R!5n S n U S R9UR:UR,R.5- n U SR9U5- n U SR9U 5- n XRS'U$)a Interface used by Requests module to apply authentication to HTTP requests. Add x-amz-content-sha256 and Authorization headers to the request. Add x-amz-date header to request if not already present and req does not contain a Date header. Check request date matches date in the current signing key. If not, regenerate signing key to match request date. If request body is not already encoded to bytes, encode to charset specified in Content-Type header, or UTF-8 if not specified. req -- Requests PreparedRequest object r x-amz-datez%Y%m%dT%H%M%SZ%Y%m%dbodyreadcontentr8x-amz-content-sha256rutf-8zAWS4-HMAC-SHA256 zCredential={}/{}, zSignedHeaders={}, z Signature={} Authorization)rrefresh_credentialsget_request_dateheadersdatetimeutcnowrstrftimehandle_date_mismatchhasattrr?r@ encode_bodyhashlibsha256rA hexdigestrget_canonical_headersr!get_canonical_requestget_sig_stringr"scopeencodehmacnewkeyr(r))r1reqreq_datenowreq_scope_date content_hashresult cano_headerssigned_headerscano_req sig_stringhshsigauth_strs r6__call__AWS4Auth.__call__ds$  ' '  $ $ &((-  $#++f*=s{{* L0I##**,CxxzH(+ 5E(FCKK %!**84 YY &  % %c * 3  CHH$8sxx((88==?   S !">>#((3L S) $ $)@">>#++6L">>#.L.:.D.D.F *+   262D2DCKK. /++C1B1BC'-$ --c.<>((8H8H8N8NO &&w/ hht''++ZHmmo&(//040@0@0F0FH H(//??N))#..'/ O$ r8cURR5nURUlURUlUR URS9 g)Nr)rget_frozen_credentials access_keyr)tokenrr+r)r1temporary_credss r6rEAWS4Auth.refresh_credentialssH66MMO(33,22 ##/I/I#Jr8c SnSHcnX1R;aMURURU5n[RR US5R 5n U$ U$![a Mvf=f![ a Mf=f)a Try to pull a date from the request by looking first at the x-amz-date header, and if that's not present then the Date header. Return a datetime.date object, or None if neither date header is found or is in a recognisable format. req -- a requests PreparedRequest object N)r=rz%Y-%m-%d)rG parse_dater rHstrptimerr,)clsrYrheaderdate_strs r6rFAWS4Auth.get_request_dates,F[[( >>#++f*=> ((11(JGLLN - #    s"A..A?. A<;A<? B  B c^/SQmU4SjU4SjU4SjSSS.nSnUR5H,up4[R"X05nU(dM$U"U5n O Uc[eU$) a Check if date_str is in a recognised format and return an ISO yyyy-mm-dd format version if so. Raise DateFormatError if not. Recognised formats are: * RFC 7231 (e.g. Mon, 09 Sep 2011 23:36:00 GMT) * RFC 850 (e.g. Sunday, 06-Nov-94 08:49:37 GMT) * C time (e.g. Wed Dec 4 00:00:00 2002) * Amz-Date format (e.g. 20090325T010101Z) * ISO 8601 / RFC 3339 (e.g. 2009-03-25T10:11:12.13-01:00) date_str -- Str containing a date and optional time ) janfebmaraprmayjunjulaugsepoctnovdecc>SRURS5TRURS5R55S-URS55$)Nz {}-{:02d}-{}rrr)r(groupindexlowermmonthss r6%AWS4Auth.parse_date..sH.//GGAJLL!1!1!34q8GGAJ r8c *>SR[[RR 5R 5SSUR S5TRUR S5R55S-UR S55$)Nz{}{}-{:02d}-{}rrr) r(strrHrtodayyearrrrrs r6rrsk*11 ++-223BQ7GGAJLL!1!1!34q8GGAJ  r8c >SRURS5TRURS5R55S-[ URS555$)Nz{}-{:02d}-{:02d}rrr)r(rrrintrs r6rrsM,33GGAJLL!1!1!34q8 O%r8c<SR"UR56$)Nz{}-{}-{})r(groupsrs r6rrs*++QXXZ8r8c$URS5$)Nr)rrs r6rrs !''!*r8)z)^(?:\w{3}, )?(\d{2}) (\w{3}) (\d{4})\D.*$z%^\w+day, (\d{2})-(\w{3})-(\d{2})\D.*$z3^\w{3} (\w{3}) (\d{1,2}) \d{2}:\d{2}:\d{2} (\d{4})$z^(\d{4})(\d{2})(\d{2})T\d{6}Z$z ^(\d{4}-\d{2}-\d{2})(?:[Tt].*)?$N)itemsresearchr )rsformatsout_dateregexxformrrs @r6roAWS4Auth.parse_datesu .   % 9%5 :#MMOLE %*Aq 8 ,  ! !Or8cfURU5nURS5nURUS9 g)z Handle a request whose date doesn't match the signing key scope date. This AWS4Auth class implementation regenerates the signing key. See StrictAWS4Auth class if you would prefer an exception to be raised. req -- a requests prepared request object r>)rN)rFrJr+)r1rY req_datetime new_key_dates r6rKAWS4Auth.handle_date_mismatchs5,,S1 #,,X6  ###6r8c[UR[5(aURR SS5R S5n[ U5S:Xa9Uup#UR S5SnURRU5Ulg USnUS:XdS U;a URR5Ulg URRS 5UlUS -URS'g g ) a Encode body of request to bytes and update content-type if required. If the body of req is Unicode then encode to the charset found in content-type header if present, otherwise UTF-8, or ASCII if content-type is application/x-www-form-urlencoded. If encoding to UTF-8 then add charset to content-type. Modifies req directly, does not return a modified copy. req -- Requests PreparedRequest object rz text/plain;r=rrz!application/x-www-form-urlencodedx-amz-rCz; charset=utf-8N)r*r?rrGr#splitr'rU)rYrctcss r6rMAWS4Auth.encode_bodys chh $ $KKOONLAGGLE5zQXXc]1%88??2.1X==R"xx0CH"xxw7CH247H2HCKK/ %r8cj[UR5n[U5nURUR5nUR SS5n[ U5S:XaUSOSnURU5nURSn URR5XhUX9/n SRU 5n U $)a Create the AWS authentication Canonical Request string. req -- Requests/Httpx PreparedRequest object. Should already include an x-amz-content-sha256 header cano_headers -- Canonical Headers section of Canonical Request, as returned by get_canonical_headers() signed_headers -- Signed Headers, as returned by get_canonical_headers() ?rrrB ) rurlr amz_cano_pathpathrr'amz_cano_querystringrGmethodupperjoin) r1rYr_r`raw_urlrrrqs payload_hash req_partsras r6rRAWS4Auth.get_canonical_request-scgg,w!!#((+ c1%UqU1Xb  & &r *{{#9: ZZ%%'<#3 99Y'r8cXUc URnUVs/sHo3R5PM nnURR5nSU;a=[ [ UR 55RRS5SUS'0nUR5HupgUR5R5nURU5R5nXb;d.SU;d(SU;dMUURS5(dMmUS:XaMuURU/5nURU5 M Sn /n [U5HFnXVnS R![U55nU S R#Xg5- n U RU5 MH S R!U 5n X4$s snf) a Generate the Canonical Headers section of the Canonical Request. Return the Canonical Headers and the Signed Headers strs as a tuple (canonical_headers, signed_headers). req -- Requests PreparedRequest object include -- List of headers to include in the canonical and signed headers. It's primarily included to allow testing against specific examples from Amazon. If omitted or None it includes host, content-type and any header starting 'x-amz-' except for x-amz-client context, which appears to break mobile analytics auth if included. Except for the x-amz-client-context exclusion these defaults are per the AWS documentation. r:r*rrzx-amz-client-contextr,z{}:{} r)r%rrGcopyrrrnetlocrrstripamz_norm_whitespace startswith setdefaultappendsortedrr() rqrYincludexrGcano_headers_dicthdrvalvalsr_signed_headers_listr`s r6rQAWS4Auth.get_canonical_headersGs|& ?11G&-.g779g.++""$  &s377|4;;AA#FqIGFO  HC))+##%C))#.446C#.(S^^H-E-E#99(33C< C (  +,C$)D((6$<(C I,,S6 6L  & &s + - "56--=/sF'cURSn[R"UR55nSX2UR 5/nSR U5nU$)z Generate the AWS4 auth string to sign for the request. req -- Requests PreparedRequest object. This should already include an x-amz-date header. cano_req -- The Canonical Request, as returned by get_canonical_request() r=zAWS4-HMAC-SHA256r)rGrNrOrUrPr)rYrarTamz_daterc sig_itemsrbs r6rSAWS4Auth.get_sig_string|sM;;|,nnX__./'#--/J YYy) r8cSnSnUnSU;aURSS5upC[R"U5n[R"SSU5nUR S5(aUR S5(dUS- nUnUR S;a [U5n[XRS9nU(aSRXS45nU$) z Generate the canonical path as per AWS4 auth requirements. Not documented anywhere, determined from aws4_testsuite examples, problem reports and testing against the live services. path -- request path z/~rrrz/+/)s3rsafe) r posixpathnormpathrsubendswithrrrr)r1r safe_charsr fixed_path full_paths r6rAWS4Auth.amz_cano_paths  * '--c15NJ'' 3 VVD#z2 ==  j&9&9#&>&> # J  <<> ) *I)5 )1Ir8c SnURS5SnURSS5n0n[USS9R5H+up4[ X1S9nUVs/sH n[ XQS9PM nnXBU'M- /n[ U5H:nX#n[ U5H$nUR S RX5/55 M& M< S RU5nU$s snf) zu Parse and format querystring as per AWS4 auth requirements. Perform percent quoting as needed. qs -- querystring z-_.~ rrz%3BT)keep_blank_valuesrr&)rreplacerrrrrr)rsafe_qs_unresvdqs_itemsnamerr qs_stringss r6rAWS4Auth.amz_cano_querystrings! XXc]1  ZZU #"2>DDFJD4D@DEE#4DE!TNG 8$D>Dd|!!#((D;"78$%XXj ! FsCc[R"SU5(a$SR[R"USS95$U$)zS Replace runs of whitespace with a single space. Ignore text enclosed in quotes. z\srF)posix)rrrshlexr)texts r6rAWS4Auth.amz_norm_whitespaces4 99UD ! !88EKKE:; ; r8) r)rr!r rrrrr")NNNNN)__name__ __module__ __qualname____firstlineno____doc__r%r0r+rfrE classmethodrF staticmethodrorKrMrRrQrSrrr__static_attributes__r8r6rrs]|Jx t>B26**X@DK 877r 7II642.2.h :4  r8rc\rSrSrSrSrSrg)StrictAWS4Authia Instances of this subclass will not automatically regenerate their signing keys when asked to sign a request whose date does not match the scope date of the signing key. Instances will instead raise a DateMismatchError. Keys of StrictAWSAuth instances can be regenerated manually by calling the regenerate_signing_key() method. Keys will still store the secret key by default. If this is not desired then create the instance by passing an AWS4SigningKey created with store_secret_key set to False to the StrictAWS4AUth constructor: >>> sig_key = AWS4SigningKey(secret_key, region, service, date, False) >>> auth = StrictAWS4Auth(access_id, sig_key) c[e)a8 Handle a request whose date doesn't match the signing key process, by raising a DateMismatchError. Overrides the default behaviour of AWS4Auth where the signing key is automatically regenerated to match the request date To update the signing key if this is hit, call StrictAWS4Auth.regenerate_signing_key(). )r r1rYs r6rK#StrictAWS4Auth.handle_date_mismatchs  r8rNrrrrrrKrrr8r6rrs "  r8rc\rSrSrSrSrSrg)PassiveAWS4Authia4 This subclass does not perform any special handling of a mismatched request and scope date, it signs the request and allows Requests to send it. It is up to the calling code to handle a failed authentication response from AWS. This behaviour mimics the behaviour of AWS4Auth for versions 0.7 and earlier. cgrrrs r6rK$PassiveAWS4Auth.handle_date_mismatchs r8rNrrr8r6rrs  r8r)rrVrNrrrrHcollections.abcr. ImportError collections urllib.parserrrr requests.authraws4signingkeyr exceptionsr r r rrrrr8r6rsw  !<;"*LLr xr j X B  h  AsA&& A32A3