o Df"@sLddlZddlmZmZmZmZGdddeZGdddeZddZ dS) N)MissingClaimErrorInvalidClaimErrorExpiredTokenErrorInvalidTokenErrorcsFeZdZdZgZd fdd ZddZddZd d Zd d Z Z S) BaseClaimsaPayload claims for JWT, which contains a validate interface. :param payload: the payload dict of JWT :param header: the header dict of JWT :param options: validate options :param params: other params An example on ``options`` parameter, the format is inspired by `OpenID Connect Claims`_:: { "iss": { "essential": True, "values": ["https://example.com", "https://example.org"] }, "sub": { "essential": True "value": "248289761001" }, "jti": { "validate": validate_jti } } .. _`OpenID Connect Claims`: http://openid.net/specs/openid-connect-core-1_0.html#IndividualClaimsRequests Ncs*t|||_|p i|_|pi|_dSN)super__init__headeroptionsparams)selfpayloadr r r  __class__T/home/ubuntu/webapp/venv/lib/python3.10/site-packages/authlib/jose/rfc7519/claims.pyr (s  zBaseClaims.__init__c CsLzt||WSty%}z||jvr||WYd}~S|d}~wwr)object__getattribute__AttributeErrorREGISTERED_CLAIMSget)r keyerrorrrr __getattr__.s zBaseClaims.__getattr__cCsB|jD]}|j|dr||vrt|||st|qdS)N essential)r rrr)r krrr_validate_essential_claims6s  z%BaseClaims._validate_essential_claimscCs|j|}|s dS||}|d}|r||krt||d}|r-||vr-t||d}|r=|||s?t|dSdS)Nvaluevaluesvalidate)r rr)r claim_nameoptionr option_value option_valuesr rrr_validate_claim_value>s       z BaseClaims._validate_claim_valuecCs(i}|jD] }||vr||||<q|Sr)r)r rvrrrrget_registered_claimsPs   z BaseClaims.get_registered_claims)NN) __name__ __module__ __qualname____doc__rr rrr%r' __classcell__rrrrr src@sVeZdZgdZdddZddZdd Zd d Zd d ZddZ ddZ ddZ dS) JWTClaims)isssubaudexpnbfiatjtiNrcCs||durtt}||||||||||||| |j D] }||j vrA| |q5dS)z&Validate everything in claims payload.N)rinttime validate_iss validate_sub validate_aud validate_exp validate_nbf validate_iat validate_jtir keysrr%)r nowleewayrrrrr [s      zJWTClaims.validatecC|ddS)aThe "iss" (issuer) claim identifies the principal that issued the JWT. The processing of this claim is generally application specific. The "iss" value is a case-sensitive string containing a StringOrURI value. Use of this claim is OPTIONAL. r.Nr%r rrrr7oszJWTClaims.validate_isscCrA)aThe "sub" (subject) claim identifies the principal that is the subject of the JWT. The claims in a JWT are normally statements about the subject. The subject value MUST either be scoped to be locally unique in the context of the issuer or be globally unique. The processing of this claim is generally application specific. The "sub" value is a case-sensitive string containing a StringOrURI value. Use of this claim is OPTIONAL. r/NrBrCrrrr8ws zJWTClaims.validate_subcs|jd}|d}|r|sdS|d}|s"|d}|r"|g}|s&dSt|dtr2|dn|dgtfdd|DsFtddS)aThe "aud" (audience) claim identifies the recipients that the JWT is intended for. Each principal intended to process the JWT MUST identify itself with a value in the audience claim. If the principal processing the claim does not identify itself with a value in the "aud" claim when this claim is present, then the JWT MUST be rejected. In the general case, the "aud" value is an array of case- sensitive strings, each containing a StringOrURI value. In the special case when the JWT has one audience, the "aud" value MAY be a single case-sensitive string containing a StringOrURI value. The interpretation of audience values is generally application specific. Use of this claim is OPTIONAL. r0Nrrcsg|]}|vqSrr).0vaud_listrr sz*JWTClaims.validate_aud..)r r isinstancelistanyr)r aud_optionr0 aud_values aud_valuerrFrr9s"     zJWTClaims.validate_audcCs:d|vr|d}t|std|||krtdSdS)a The "exp" (expiration time) claim identifies the expiration time on or after which the JWT MUST NOT be accepted for processing. The processing of the "exp" claim requires that the current date/time MUST be before the expiration date/time listed in the "exp" claim. Implementers MAY provide for some small leeway, usually no more than a few minutes, to account for clock skew. Its value MUST be a number containing a NumericDate value. Use of this claim is OPTIONAL. r1N)_validate_numeric_timerr)r r?r@r1rrrr:  zJWTClaims.validate_expcCs:d|vr|d}t|std|||krtdSdS)aThe "nbf" (not before) claim identifies the time before which the JWT MUST NOT be accepted for processing. The processing of the "nbf" claim requires that the current date/time MUST be after or equal to the not-before date/time listed in the "nbf" claim. Implementers MAY provide for some small leeway, usually no more than a few minutes, to account for clock skew. Its value MUST be a number containing a NumericDate value. Use of this claim is OPTIONAL. r2NrOrr)r r?r@r2rrrr;rPzJWTClaims.validate_nbfcCs>d|vr|d}t|std|||krtdddSdS)axThe "iat" (issued at) claim identifies the time at which the JWT was issued. This claim can be used to determine the age of the JWT. Implementers MAY provide for some small leeway, usually no more than a few minutes, to account for clock skew. Its value MUST be a number containing a NumericDate value. Use of this claim is OPTIONAL. r3z5The token is not valid as it was issued in the future) descriptionNrQ)r r?r@r3rrrr<s zJWTClaims.validate_iatcCrA)aEThe "jti" (JWT ID) claim provides a unique identifier for the JWT. The identifier value MUST be assigned in a manner that ensures that there is a negligible probability that the same value will be accidentally assigned to a different data object; if the application uses multiple issuers, collisions MUST be prevented among values produced by different issuers as well. The "jti" claim can be used to prevent the JWT from being replayed. The "jti" value is a case- sensitive string. Use of this claim is OPTIONAL. r4NrBrCrrrr=s zJWTClaims.validate_jti)Nr) r(r)r*rr r7r8r9r:r;r<r=rrrrr-Xs  # r-cCst|ttfSr)rIr5float)srrrrOsrO) r6authlib.jose.errorsrrrrdictrr-rOrrrrs N