TњhI."SS5r\"S5rSrg)c\rSrSrSrSr\S5r\S5r\S5r Sr \S5r \S 5r \S 5r \S 5r\S 5r\S 5r\S5r\S5r\S5r\S5r\S5r\S5rSrg) AppSettingscXlgNprefix)selfrs ]D:\Anime\Ugyen\janka_web_project\venv\Lib\site-packages\allauth/socialaccount/app_settings.py__init__AppSettings.__init__s c:SSKJn U"URU-U5$)N) get_setting) allauth.utilsrr)r namedfltrs r _settingAppSettings._settings-4;;-t44r c:URSUR5$)zM Request email address from 3rd party account provider? E.g. using OpenID AX QUERY_EMAIL)rEMAIL_REQUIREDr s r rAppSettings.QUERY_EMAIL s }}]D,?,?@@r c&URSS5$)z Attempt to bypass the signup form by using fields (e.g. username, email) retrieved from the social account provider. If a conflict arises due to a duplicate email signup form will still kick in. AUTO_SIGNUPTrrs r rAppSettings.AUTO_SIGNUPs}}]D11r cURS05nURS5nU(aURU5US'U$)z Provider specific settings PROVIDERSopenid_connect)rget _migrate_oidc)r retoidcs r r AppSettings.PROVIDERSsA mmK,ww'( $($6$6t$sC E!// F*Nvg/B/B:/N}}-~>>r cSSKJn SSKJn UR(aURR OSnUR SU5$)z\ See email verification method. When `None`, the default `allauth.account` logic kicks in. rr<NEMAIL_VERIFICATION)allauthr9r?SOCIALACCOUNT_ONLYEmailVerificationMethodNONEr)r allauth_settingsrArs r rFAppSettings.EMAIL_VERIFICATIONIsB =D 22  4 4 9 9 }}1488r c&URSS5$)aConsider a scenario where a social login occurs, and the social account comes with a verified email address (verified by the account provider), but that email address is already taken by a local user account. Additionally, assume that the local user account does not have any social account connected. Now, if the provider can be fully trusted, you can argue that we should treat this scenario as a login to the existing local user account even if the local account does not already have the social account connected, because -- according to the provider -- the user logging in has ownership of the email address. This is how this scenario is handled when `EMAIL_AUTHENTICATION` is set to `True`. As this implies that an untrustworthy provider can login to any local account by fabricating social account data, this setting defaults to `False`. Only set it to `True` if you are using providers that can be fully trusted. EMAIL_AUTHENTICATIONFrrs r rN AppSettings.EMAIL_AUTHENTICATIONYs"}}3U;;r c&URSS5$)a)In case email authentication is applied, this setting controls whether or not the social account is automatically connected to the local account. In case of ``False`` (the default) the local account remains unchanged during the login. In case of ``True``, the social account for which the email matched, is automatically added to the list of social accounts connected to the local account. As a result, even if the user were to change the email address afterwards, social login would still be possible when using ``True``, but not in case of ``False``. !EMAIL_AUTHENTICATION_AUTO_CONNECTFrrs r rQ-AppSettings.EMAIL_AUTHENTICATION_AUTO_CONNECTls}}@%HHr c&URSS5$)NADAPTERz9allauth.socialaccount.adapter.DefaultSocialAccountAdapterrrs r rTAppSettings.ADAPTERzs}}  G  r c&URS05$)NFORMSrrs r rWAppSettings.FORMSs}}Wb))r c&URSS5$)N LOGIN_ON_GETFrrs r rZAppSettings.LOGIN_ON_GET}}^U33r c&URSS5$)N STORE_TOKENSFrrs r r^AppSettings.STORE_TOKENSr\r cg)Nr1rs r UID_MAX_LENGTHAppSettings.UID_MAX_LENGTHsr c&URSS5$)NSOCIALACCOUNT_STRrrs r reAppSettings.SOCIALACCOUNT_STRs}}0$77r c&URSS5$)NREQUESTS_TIMEOUTrrs r rhAppSettings.REQUESTS_TIMEOUTs}}/33r c&URSS5$)NOPENID_CONNECT_URL_PREFIXr%rrs r rl%AppSettings.OPENID_CONNECT_URL_PREFIXs}}8&AAr rN)__name__ __module__ __qualname____firstlineno__r rpropertyrrr r#rrFrNrQrTrWrZr^rbrerhrl__static_attributes__r1r r rrsC5 AA220?? 9 9<<$ I I  **44448844BBr rSOCIALACCOUNT_c"[[U5$r)getattr _app_settings)rs r __getattr__rxs =$ ''r N)rrwrxr1r r rys&ZBZBz,- (r