Ë ÞªgtãóL—ddlmZmZmZmZmZmZmZmZm Z m Z m Z Gd„d«Z y)é) ÚAuthMFAChallengeResponseÚAuthMFAEnrollResponseÚ-AuthMFAGetAuthenticatorAssuranceLevelResponseÚAuthMFAListFactorsResponseÚAuthMFAUnenrollResponseÚAuthMFAVerifyResponseÚMFAChallengeAndVerifyParamsÚMFAChallengeParamsÚMFAEnrollParamsÚMFAUnenrollParamsÚMFAVerifyParamscóx—eZdZdZdedefd„Zdedefd„Z de de fd„Z de de fd„Zdedefd„Zdefd „Zdefd „Zy ) ÚAsyncGoTrueMFAAPIz< Contains the full multi-factor authentication API. ÚparamsÚreturncƒóK—t«‚­w)aS Starts the enrollment process for a new Multi-Factor Authentication factor. This method creates a new factor in the 'unverified' state. Present the QR code or secret to the user and ask them to add it to their authenticator app. Ask the user to provide you with an authenticator code from their app and verify it by calling challenge and then verify. The first successful verification of an unverified factor activates the factor. All other sessions are logged out and the current one gets an `aal2` authenticator level. ©ÚNotImplementedError©Úselfrs úQ/var/www/openai/venv/lib/python3.12/site-packages/gotrue/_async/gotrue_mfa_api.pyÚenrollzAsyncGoTrueMFAAPI.enrollsèø€ô"Ó#Ð#ùó‚ cƒóK—t«‚­w)z© Prepares a challenge used to verify that a user has access to a MFA factor. Provide the challenge ID and verification code by calling `verify`. rrs rÚ challengezAsyncGoTrueMFAAPI.challenge#óèø€ô "Ó#Ð#ùrcƒóK—t«‚­w)zð Helper method which creates a challenge and immediately uses the given code to verify against it thereafter. The verification code is provided by the user by entering a code seen in their authenticator app. rrs rÚchallenge_and_verifyz&AsyncGoTrueMFAAPI.challenge_and_verify*sèø€ô"Ó#Ð#ùrcƒóK—t«‚­w)z­ Verifies a verification code against a challenge. The verification code is provided by the user by entering a code seen in their authenticator app. rrs rÚverifyzAsyncGoTrueMFAAPI.verify5rrcƒóK—t«‚­w)zö Unenroll removes a MFA factor. Unverified factors can safely be ignored and it's not necessary to unenroll them. Unenrolling a verified MFA factor cannot be done from a session with an `aal1` authenticator level. rrs rÚunenrollzAsyncGoTrueMFAAPI.unenroll<sèø€ô "Ó#Ð#ùrcƒóK—t«‚­w)a: Returns the list of MFA factors enabled for this user. For most use cases you should consider using `get_authenticator_assurance_level`. This uses a cached version of the factors and avoids incurring a network call. If you need to update this list, call `get_user` first. r©rs rÚ list_factorszAsyncGoTrueMFAAPI.list_factorsDsèø€ô"Ó#Ð#ùrcƒóK—t«‚­w)a~ Returns the Authenticator Assurance Level (AAL) for the active session. - `aal1` (or `null`) means that the user's identity has been verified only with a conventional login (email+password, OTP, magic link, social login, etc.). - `aal2` means that the user's identity has been verified both with a conventional login and at least one MFA factor. Although this method returns a promise, it's fairly quick (microseconds) and rarely uses the network. You can use this to check whether the current user needs to be shown a screen to verify their MFA factors. rr$s rÚ!get_authenticator_assurance_levelz3AsyncGoTrueMFAAPI.get_authenticator_assurance_levelNsèø€ô "Ó#Ð#ùrN)Ú__name__Ú __module__Ú __qualname__Ú__doc__r rrr rrr rrr r r rr"rr%rr'©órrrsŠ„ñð $ ?ð $Ð7Ló $ð$Ð&8ð$Ð=Uó$ð $à+ð $ð ó $ð$ ?ð$Ð7Ló$ð$Ð%6ð$Ð;Ró$ð$Ð$>ó$ð$à 6ô$r-rN) Útypesrrrrrrr r r r r rr,r-rÚr/s%ð÷ ÷ ÷ ñ ÷N$òN$r-